rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: James Matthew Farrow <matty@cs.su.OZ.AU>
To: rc@archone.tamu.edu
Subject: Re: comments, newlines
Date: Sun, 15 Mar 1992 17:31:07 -0600	[thread overview]
Message-ID: <19920315183107.28843.frobozz@karl.cs.su.OZ.AU> (raw)
In-Reply-To: <9203141939.AA22325@burn.Princeton.EDU>

I am in favour of John's view.  I always getting caught by special
characters ([=~#]) always being special and having to quote them which
makes commands look really ugly and less readable sometimes.  For
example, the 

    	What's wrong with
    		lpr -Gr2 -#3 foo.ps
    	? Why doesn't it print anything ? Do you really prefer
    		lpr -Gr2 -'#'3 foo.ps
    	? Is that better syntax ? Is it more readable ?
	
that Emin mentioned.

					Matty.


  reply	other threads:[~1992-03-15  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-03-14 19:39 Emin G. Sirer
1992-03-15 23:31 ` James Matthew Farrow [this message]
1992-03-15 17:54   ` schwartz
  -- strict thread matches above, loose matches on Subject: below --
1992-03-11 17:27 haahr
1992-03-12 22:05 ` David J. Fiander
1992-03-13 10:14   ` John Mackin
1992-03-13 22:44     ` Dave Mason
1992-03-11  7:19 schwartz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19920315183107.28843.frobozz@karl.cs.su.OZ.AU \
    --to=matty@cs.su.oz.au \
    --cc=rc@archone.tamu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).