Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.apps > #19681 > unrolled thread

Terminal instructions

Back to article view | Back to comp.sys.mac.apps

Contents

  Terminal instructions  Butkus <ax64@mailinator.com> - 2013-11-28 07:24 +0000
    Re: Terminal instructions android <here@there.was> - 2013-11-28 08:35 +0100
      Re: Terminal instructions Butkus <ax64@mailinator.com> - 2013-11-29 13:49 +0000
        Re: Terminal instructions briang@panix.com (Brian Gordon) - 2013-11-29 15:59 +0000
          Re: Terminal instructions Butkus <ax64@mailinator.com> - 2013-11-30 12:37 +0000
            Re: Terminal instructions briang@panix.com (Brian Gordon) - 2013-11-30 16:07 +0000
              Re: Terminal instructions Alan Browne <alan.browne@FreelunchVideotron.ca> - 2013-11-30 11:39 -0500
                Re: Terminal instructions Butkus <ax64@mailinator.com> - 2013-12-01 17:46 +0000
                  Re: Terminal instructions android <here@there.was> - 2013-12-01 18:52 +0100
                    Re: Terminal instructions android <here@there.was> - 2013-12-01 19:09 +0100
                      Re: Terminal instructions "John Varela" <newlamps@verizon.net> - 2013-12-01 18:47 +0000
              Re: Terminal instructions dorayme <dorayme@optusnet.com.au> - 2013-12-01 08:42 +1100
    Re: Terminal instructions nospam <nospam@nospam.invalid> - 2013-11-28 03:01 -0500
    Re: Terminal instructions Michael Vilain <vilain@NOspamcop.net> - 2013-11-28 00:10 -0800
      Re: Terminal instructions nospam <nospam@nospam.invalid> - 2013-11-28 03:12 -0500
      Re: Terminal instructions android <here@there.was> - 2013-11-28 09:18 +0100
      Re: Terminal instructions Tim Streater <timstreater@greenbee.net> - 2013-11-28 08:21 +0000
        Re: Terminal instructions Barry Margolin <barmar@alum.mit.edu> - 2013-11-28 05:37 -0500
          Re: Terminal instructions briang@panix.com (Brian Gordon) - 2013-11-28 16:36 +0000
            Re: Terminal instructions Jolly Roger <jollyroger@pobox.com> - 2013-11-28 16:39 +0000
              Re: Terminal instructions briang@panix.com (Brian Gordon) - 2013-11-28 23:32 +0000
            Re: Terminal instructions gtr <xxx@yyy.zzz> - 2013-11-28 12:17 -0800
              Re: Terminal instructions Barry Margolin <barmar@alum.mit.edu> - 2013-11-29 00:32 -0500
                Re: Terminal instructions Paul Sture <nospam@sture.ch> - 2013-11-30 18:39 +0100
                  Re: Terminal instructions "John Varela" <newlamps@verizon.net> - 2013-12-01 01:32 +0000
                Re: Terminal instructions Wes Groleau <Groleau+news@FreeShell.org> - 2013-12-10 00:06 -0500
          Re: Terminal instructions "John Varela" <newlamps@verizon.net> - 2013-11-29 21:11 +0000
            Re: Terminal instructions Tim Streater <timstreater@greenbee.net> - 2013-11-29 23:11 +0000
    Re: Terminal instructions Lewis <g.kreme@gmail.com.dontsendmecopies> - 2013-11-28 13:57 +0000
      Re: Terminal instructions gtr <xxx@yyy.zzz> - 2013-11-28 07:52 -0800
        Re: Terminal instructions Alan Browne <alan.browne@FreelunchVideotron.ca> - 2013-11-30 10:43 -0500
          Re: Terminal instructions Lewis <g.kreme@gmail.com.dontsendmecopies> - 2013-12-01 04:15 +0000
            Re: Terminal instructions Alan Browne <alan.browne@FreelunchVideotron.ca> - 2013-12-01 10:07 -0500
    Re: Terminal instructions billy@MIX.COM - 2013-11-28 15:20 +0000
    Re: Terminal instructions jamiekg@wizardling.geek.nz (Jamie Kahn Genet) - 2013-11-29 11:58 +1300
    Re: Terminal instructions Wes Groleau <Groleau+news@FreeShell.org> - 2013-12-10 00:29 -0500
      Re: Terminal instructions Butkus <ax64@mailinator.com> - 2013-12-11 07:24 +0000
      Re: Terminal instructions Wes Groleau <Groleau+news@FreeShell.org> - 2013-12-12 02:38 -0500

Page 2 of 2 — ← Prev page 1 [2]

#19730

In article <bfp9tfFhljaU1@mid.individual.net>,
Jolly Roger  <jollyroger@pobox.com> wrote:
>On 2013-11-28, Brian Gordon <briang@panix.com> wrote:
>>	[...]
>> Really?  I'm one of the (many) authors of the original Netiquette manual, and
>> don't remember this being in there ...
>
>Are you referring to RFC 1855?:
>
><http://tools.ietf.org/html/rfc1855>
>

Nope -- the "original" manual was written in the 70s or 80s and was about 5-6
pages long :-) I only skimmed these 19 pages and didn't notice it there, but
maybe I just missed it :-)

-- 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
| Brian Gordon     -->briang@panix.com<--     brian dot gordon at cox dot net |
+ brianggordon@hotmail.com   Bass: Lexington "Main Street Harmonizers" chorus +
-------------------------------------------------------------------------------

[toc] | [prev] | [next] | [standalone]

#19712

On 2013-11-28 16:36:19 +0000, Brian Gordon said:

> In article <barmar-A4D4DC.05374728112013@news.eternal-september.org>,
> Barry Margolin  <barmar@alum.mit.edu> wrote:
>> In article <281120130821135194%timstreater@greenbee.net>,
>> Tim Streater <timstreater@greenbee.net> wrote:
>> 
>>> In article <vilain-3FA53C.00100828112013@news.individual.net>, Michael
>>> Vilain <vilain@NOspamcop.net> wrote:
>>> 
>>>> books.  Or find another vendor who's books you like.  I prefer
>>> 
>>> whose
>>> 
>>>> expect to loose stuff as you shoot yourself in the foot.
>>> 
>>> lose
>> 
>> Didn't anyone ever teach you that it's bad netiquette to reply only for
>> the purpose of correcting spelling/grammar?
>> 
> 
> Really?  I'm one of the (many) authors of the original Netiquette manual, and
> don't remember this being in there ...

Did you write this part (with my emphasis):

   - Messages and articles should be brief and to the point.  Don't
      wander off-topic, don't ramble and don't send mail or *post
      messages solely to point out other people's errors in typing
      or spelling*.  These, more than any other behavior, mark you
      as an immature beginner.

But I think a salient consideration of etiquette whether on the net or 
elsewhere is "don't be a prick". That's sound advice.

[toc] | [prev] | [next] | [standalone]

#19745

In article <2013112812172078109-xxx@yyyzzz>, gtr <xxx@yyy.zzz> wrote:

> On 2013-11-28 16:36:19 +0000, Brian Gordon said:
> 
> > In article <barmar-A4D4DC.05374728112013@news.eternal-september.org>,
> > Barry Margolin  <barmar@alum.mit.edu> wrote:
> >> In article <281120130821135194%timstreater@greenbee.net>,
> >> Tim Streater <timstreater@greenbee.net> wrote:
> >> 
> >>> In article <vilain-3FA53C.00100828112013@news.individual.net>, Michael
> >>> Vilain <vilain@NOspamcop.net> wrote:
> >>> 
> >>>> books.  Or find another vendor who's books you like.  I prefer
> >>> 
> >>> whose
> >>> 
> >>>> expect to loose stuff as you shoot yourself in the foot.
> >>> 
> >>> lose
> >> 
> >> Didn't anyone ever teach you that it's bad netiquette to reply only for
> >> the purpose of correcting spelling/grammar?
> >> 
> > 
> > Really?  I'm one of the (many) authors of the original Netiquette manual, 
> > and
> > don't remember this being in there ...
> 
> Did you write this part (with my emphasis):
> 
>    - Messages and articles should be brief and to the point.  Don't
>       wander off-topic, don't ramble and don't send mail or *post
>       messages solely to point out other people's errors in typing
>       or spelling*.  These, more than any other behavior, mark you
>       as an immature beginner.
> 
> But I think a salient consideration of etiquette whether on the net or 
> elsewhere is "don't be a prick". That's sound advice.

There's also Skitt's Law

http://rationalwiki.org/wiki/Internet_law#Skitt.27s_Law

"Any post correcting an error in another post will contain at least one 
error itself"

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[toc] | [prev] | [next] | [standalone]

#19766

Barry Margolin wrote:
>
> There's also Skitt's Law
>
> http://rationalwiki.org/wiki/Internet_law#Skitt.27s_Law
>
> "Any post correcting an error in another post will contain at least one 
> error itself"

Hiss boo hiss.

I wrote similar posts somewhere on CompuServe back in 1997.

I claim prior art.

Or would if an archive of those posts still existed :-)

-- 
Paul Sture

[toc] | [prev] | [next] | [standalone]

#19768

On Sat, 30 Nov 2013 17:39:43 UTC, Paul Sture <nospam@sture.ch> 
wrote:

> Barry Margolin wrote:
> >
> > There's also Skitt's Law
> >
> > http://rationalwiki.org/wiki/Internet_law#Skitt.27s_Law
> >
> > "Any post correcting an error in another post will contain at least one 
> > error itself"
> 
> Hiss boo hiss.
> 
> I wrote similar posts somewhere on CompuServe back in 1997.
> 
> I claim prior art.

You're not even close:

According to knowyourmeme.com/memes/skitts-law:

On May 15th, 1990, alt.sex[17] user Andrew Bell replied to a thread 
regarding grammar corrections that are incorrect with "Bell's First 
Law of Usenet":

    "Bell's First Law of USENET: Flames of spelling and/or grammar 
will
    have spelling and/or grammatical errors."

-- 
John Varela

[toc] | [prev] | [next] | [standalone]

#19850

On 11-29-2013, 00:32, Barry Margolin wrote:
> There's also Skitt's Law
>
> http://rationalwiki.org/wiki/Internet_law#Skitt.27s_Law
>
> "Any post correcting an error in another post will contain at least one
> error itself"

I think Tim Streater just proved that wrong.

-- 
Wes Groleau

   “But, Professor! I didn't plagiarize! I paid someone to
    write the essay for me, and that person plagiarized!"
               — from http://rateyourstudents.blogspot.com

[toc] | [prev] | [next] | [standalone]

#19754

On Thu, 28 Nov 2013 10:37:47 UTC, Barry Margolin 
<barmar@alum.mit.edu> wrote:

> In article <281120130821135194%timstreater@greenbee.net>,
>  Tim Streater <timstreater@greenbee.net> wrote:
> 
> > In article <vilain-3FA53C.00100828112013@news.individual.net>, Michael
> > Vilain <vilain@NOspamcop.net> wrote:
> > 
> > > books.  Or find another vendor who's books you like.  I prefer 
> > 
> > whose
> > 
> > > expect to loose stuff as you shoot yourself in the foot.
> > 
> > lose
> 
> Didn't anyone ever teach you that it's bad netiquette to reply only for 
> the purpose of correcting spelling/grammar?
 
Except in alt.usage.english.

-- 
John Varela

[toc] | [prev] | [next] | [standalone]

#19756

In article <51W5y0sPNk52-pn2-xYyJKdPkwPGb@localhost>, John Varela
<newlamps@verizon.net> wrote:

> On Thu, 28 Nov 2013 10:37:47 UTC, Barry Margolin 
> <barmar@alum.mit.edu> wrote:
> 
> > In article <281120130821135194%timstreater@greenbee.net>,
> >  Tim Streater <timstreater@greenbee.net> wrote:
> > 
> > > In article <vilain-3FA53C.00100828112013@news.individual.net>, Michael
> > > Vilain <vilain@NOspamcop.net> wrote:
> > > 
> > > > books.  Or find another vendor who's books you like.  I prefer 
> > > 
> > > whose
> > > 
> > > > expect to loose stuff as you shoot yourself in the foot.
> > > 
> > > lose
> > 
> > Didn't anyone ever teach you that it's bad netiquette to reply only for 
> > the purpose of correcting spelling/grammar?
>  
> Except in alt.usage.english.

That would be like saying that the only place where it's OK to arrest
bad guys is at police college.

-- 
Tim

"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted"  --  Bill of Rights 1689

[toc] | [prev] | [next] | [standalone]

#19694

In message <1936776914407271227.467156ax64-mailinator.com@news.tin.it> 
  Butkus <ax64@mailinator.com> wrote:
> Is there a book or something where you can learn how to use the Terminal
> and its instructions?

This was good, but was never updated:

<http://shop.oreilly.com/product/9780596009434.do>

Probably still has most everything you need in it.

-- 
"Anything that is in the world when you’re born is normal and ordinary
 and is just a natural part of the way the world works. Anything that’s
 invented between when you’re fifteen and thirty- five is new and exciting
 and revolutionary and you can probably get a career in it. Anything
 invented after you’re thirty-five is against the natural order of
 things."  -- Douglas Adams

[toc] | [prev] | [next] | [standalone]

#19701

On 2013-11-28 13:57:26 +0000, Lewis said:

> In message <1936776914407271227.467156ax64-mailinator.com@news.tin.it>
>   Butkus <ax64@mailinator.com> wrote:
>> Is there a book or something where you can learn how to use the Terminal
>> and its instructions?
> 
> This was good, but was never updated:
> 
> <http://shop.oreilly.com/product/9780596009434.do>
> 
> Probably still has most everything you need in it.

I've had that book since Tiger, and wondered if they would ever produce 
another more up-to-date edition. Oh, but I wisht they would!

[toc] | [prev] | [next] | [standalone]

#19763

On 2013.11.28, 10:52 , gtr wrote:
> On 2013-11-28 13:57:26 +0000, Lewis said:
>
>> In message <1936776914407271227.467156ax64-mailinator.com@news.tin.it>
>>   Butkus <ax64@mailinator.com> wrote:
>>> Is there a book or something where you can learn how to use the Terminal
>>> and its instructions?
>>
>> This was good, but was never updated:
>>
>> <http://shop.oreilly.com/product/9780596009434.do>
>>
>> Probably still has most everything you need in it.
>
> I've had that book since Tiger, and wondered if they would ever produce
> another more up-to-date edition. Oh, but I wisht they would!

Wrt unix and command line (thread topic) I don't think there have been 
any changes at all since then - at least for the casual user.

There is plenty online as well.
Here's a tutorial page that looks well structured:
http://www.tutorialspoint.com/unix/

For particular "fixes" using command line you can usually copy from the 
web, paste, edit if needed and execute.

-- 
"The radio was once expected to promote international understanding and 
co-operation;
it has turned out to be a means of insulating one nation from another."
                                                  -George Orwell, 1945

[toc] | [prev] | [next] | [standalone]

#19770

In message <hpednQoqA6I6mgfPnZ2dnUVZ_vqdnZ2d@giganews.com> 
  Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
> On 2013.11.28, 10:52 , gtr wrote:
>> On 2013-11-28 13:57:26 +0000, Lewis said:
>>
>>> In message <1936776914407271227.467156ax64-mailinator.com@news.tin.it>
>>>   Butkus <ax64@mailinator.com> wrote:
>>>> Is there a book or something where you can learn how to use the Terminal
>>>> and its instructions?
>>>
>>> This was good, but was never updated:
>>>
>>> <http://shop.oreilly.com/product/9780596009434.do>
>>>
>>> Probably still has most everything you need in it.
>>
>> I've had that book since Tiger, and wondered if they would ever produce
>> another more up-to-date edition. Oh, but I wisht they would!

> Wrt unix and command line (thread topic) I don't think there have been 
> any changes at all since then - at least for the casual user.

But it's more than jut "UNIX ina  Nutshell" (that's a different book.
There are things that are specific to OS X that are worth knowing about.
the `open` and `osascript` commands, just to name two. 

-- 
'Tell me, sir Samuel, do you know the phrase "Quis custodiet isos
custodes?"? (...) It means "Who guards the guards themselves?" (...) Who
watches the Watch?' --Feet of Clay

[toc] | [prev] | [next] | [standalone]

#19774

On 2013.11.30, 23:15 , Lewis wrote:
> In message <hpednQoqA6I6mgfPnZ2dnUVZ_vqdnZ2d@giganews.com>
>    Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>> On 2013.11.28, 10:52 , gtr wrote:
>>> On 2013-11-28 13:57:26 +0000, Lewis said:
>>>
>>>> In message <1936776914407271227.467156ax64-mailinator.com@news.tin.it>
>>>>    Butkus <ax64@mailinator.com> wrote:
>>>>> Is there a book or something where you can learn how to use the Terminal
>>>>> and its instructions?
>>>>
>>>> This was good, but was never updated:
>>>>
>>>> <http://shop.oreilly.com/product/9780596009434.do>
>>>>
>>>> Probably still has most everything you need in it.
>>>
>>> I've had that book since Tiger, and wondered if they would ever produce
>>> another more up-to-date edition. Oh, but I wisht they would!
>
>> Wrt unix and command line (thread topic) I don't think there have been
>> any changes at all since then - at least for the casual user.
>
> But it's more than jut "UNIX ina  Nutshell" (that's a different book.
> There are things that are specific to OS X that are worth knowing about.
> the `open` and `osascript` commands, just to name two.

As I said, for the "casual user" of terminal who occasionally needs to 
do something in terminal, there haven't been changes worth a new book. 
Experts who use terminal a lot are probably happy with the man and don't 
need the book.

As to osascript, it's been there since 10.0 so it would be covered (I 
assume) in the referred Tiger manual.

-- 
"The radio was once expected to promote international understanding and 
co-operation;
it has turned out to be a means of insulating one nation from another."
                                                  -George Orwell, 1945

[toc] | [prev] | [next] | [standalone]

#19697

Butkus <ax64@mailinator.com> asked:

> > Is there a book or something where you can learn
> > how to use the Terminal and its instructions?

This is written for Linux...

http://linuxcommand.org/tlcl.php

...but, it's a good place to start, and it's available for free.

There is also a good GUI command line (terminal) interface -

http://rixstep.com/4/0/clix/

It's free, too.

Billy Y..
-- 
        sub     #'9+1   ,r0             ; convert ascii byte
	add     #9.+1   ,r0             ; to an integer
	bcc     20$                     ; not a number

[toc] | [prev] | [next] | [standalone]

#19728

Butkus <ax64@mailinator.com> wrote:

> Is there a book or something where you can learn how to use the Terminal
> and its instructions?

I used a couple O'Reily titles including 'Learning UNIX for Mac OS X'
and 'Mac OS X The Missing Manual' which has a UNIX section. Mac OS X
Hacks also had a bunch of UNIX stuff.
-- 
If you're not part of the solution, you're part of the precipitate.

[toc] | [prev] | [next] | [standalone]

#19851

On 11-28-2013, 02:24, Butkus wrote:
> Is there a book or something where you can learn how to use the Terminal
> and its instructions?

Are you in a hurry, or do you just want to explore?

If the latter, think of something that might be inthere.

Type "apropos" and the thing you thought of.  Like

apropos disk

You'll get two columns of stuff.  on the left is something that has a 
place in "the manual" with the section number in the manual in 
parentheses.  On the right is a brief description of the thing.

The items in section one are commands you can type in Terminal.
Pick a command that sounds interesting, and type

man (command)

substituting the command you chose, of course.

To get another screenful of text, hit the space bar.
To get another line of text, the return key.
To get out before the end, the letter 'q'

Happy Reading!

You can even do 'man apropos' or 'man man'

And if you want a REALLY long one, 'man bash'

Last but not least, to cure insomnia, paste the
following five lies into Terminal:

for CHAPTER in $(man perl                          | \
                  egrep " +perl[a-z]+ +Perl [a-z]+" | \
                  awk '{print $1}')                 ; do
     man $CHAPTER
done


-- 
Wes Groleau

   “But, Professor! I didn't plagiarize! I paid someone to
    write the essay for me, and that person plagiarized!"
               — from http://rateyourstudents.blogspot.com

[toc] | [prev] | [next] | [standalone]

#19874

Wes Groleau <Groleau+news@FreeShell.org> wrote:
> On 11-28-2013, 02:24, Butkus wrote:
>
[Cut]

> Happy Reading!
> 
> You can even do 'man apropos' or 'man man'
> 
> And if you want a REALLY long one, 'man bash'
> 
> Last but not least, to cure insomnia, paste the
> following five lies into Terminal:
> 
> for CHAPTER in $(man perl                          | \
>                  egrep " +perl[a-z]+ +Perl [a-z]+" | \
>                  awk '{print $1}')                 ; do
>     man $CHAPTER
> done
> 


Thank you, and about plagiarism I found somewhere this:
"Copying from one is plagiarism, copy fro many is research".

[toc] | [prev] | [next] | [standalone]

#19882

On 12-10-2013, 00:29, Wes Groleau wrote:
> Last but not least, to cure insomnia, paste the
> following five lies into Terminal:

_lines_  :-)

-- 
Wes Groleau

    Liar, Liar, Pants on Fire!
    http://www.politifact.com/truth-o-meter/rulings/pants-fire/

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.sys.mac.apps

csiph-web