zsh-users
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-users@zsh.org
Subject: INTERACTIVE_COMMENTS - why?
Date: Wed, 24 Aug 2011 14:02:50 +0200	[thread overview]
Message-ID: <87y5yjf251.fsf@ft.bewatermyfriend.org> (raw)

Hey list!

I've been wondering why the option `interactive_comments' is there at
all. I thought, that maybe comments would clash with some corner cases
of `extended_glob', like when you have a file called "a  b" and try a
glob "a\ #b".  But that is not the case.

Since I couldn't find a technical reason for it, it might be there for
emulating the behaviour of another shell. My guess would be csh or tcsh,
which behave like that, too AFAIK.

Can someone confirm that suspicion or did I miss a technical issue that
can be avoided by having `interactive_comments' unset?

Regards, Frank

-- 
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
                                                  -- RFC 1925


             reply	other threads:[~2011-08-24 12:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 12:02 Frank Terbeck [this message]
2011-08-24 12:44 ` Mikael Magnusson
2011-08-24 13:17   ` Frank Terbeck
2011-08-24 15:00     ` Bart Schaefer
2011-08-24 17:05       ` Frank Terbeck
2011-08-29 15:17         ` Bart Schaefer

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=87y5yjf251.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --cc=zsh-users@zsh.org \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).