zsh-users
 help / color / mirror / code / Atom feed
From: Roman Neuhauser <neuhauser@sigpipe.cz>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@zsh.org
Subject: Re: setopt interactivecomments
Date: Fri, 18 Apr 2014 13:59:12 +0200	[thread overview]
Message-ID: <20140418115912.GC2388@isis.sigpipe.cz> (raw)
In-Reply-To: <140417154117.ZM22891@torch.brasslantern.com>

# schaefer@brasslantern.com / 2014-04-17 15:41:17 -0700:
> } What would break if interactive comments was on by default?
> 
> I don't know how prevalent this still is, but a number of programs used
> file names with # in them for backups.  It becomes one more thing you
> have to quote.

i'm *very* happy with zsh's conservatism: with one or two exceptions,
my 14yr old .zshrc has worked the same for me the whole time.

that said, i rely on filename completion to quote metacharacters for me.
it's possible to screw it up when i *do* input crazy filenames w/o
autocompletion (most probably copy/paste), so far i had no horrible
things happen in result (knock on wood).  IOW i have a slight preference
for interactive comments to be enabled by default, if completion
compensates for it.

-- 
roman


  parent reply	other threads:[~2014-04-18 12:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 14:35 shawn wilson
2014-04-16 17:27 ` Bart Schaefer
2014-04-16 17:37   ` shawn wilson
2014-04-17 14:37     ` Ray Andrews
2014-04-17 19:37       ` Bart Schaefer
2014-04-17 21:36         ` Ray Andrews
2014-04-17 22:07           ` shawn wilson
2014-04-17 22:48             ` Bart Schaefer
2014-04-17 23:51               ` shawn wilson
2014-04-17 22:41           ` Bart Schaefer
2014-04-18  3:10             ` Ray Andrews
2014-04-18 11:59             ` Roman Neuhauser [this message]
2014-04-23 15:50         ` zsh-newuser-install Peter Stephenson
2014-04-23 20:31           ` zsh-newuser-install Yuri D'Elia
2014-04-23 23:53             ` zsh-newuser-install Mikael Magnusson
2014-04-24  6:23               ` zsh-newuser-install Yuri D'Elia
2014-04-24 14:34                 ` zsh-newuser-install Ray Andrews
2014-04-24 16:02                   ` zsh-newuser-install Yuri D'Elia
2014-04-25  1:38                     ` zsh-newuser-install Ray Andrews
2014-04-24 16:04                   ` zsh-newuser-install Axel Beckert
2014-04-25 15:43               ` zsh-newuser-install Martin Vaeth
2014-04-25 16:21                 ` zsh-newuser-install Peter Stephenson
2014-04-26 10:07                   ` zsh-newuser-install Martin Vaeth
2014-04-26 20:21                     ` zsh-newuser-install Peter Stephenson
2014-04-26 20:38                     ` zsh-newuser-install Bart Schaefer
2014-04-25 17:03                 ` zsh-newuser-install Bart Schaefer
2014-04-26 13:49                 ` zsh-newuser-install Yuri D'Elia
2014-04-26 21:10                   ` zsh-newuser-install Bart Schaefer
2014-04-28 17:35                     ` zsh-newuser-install Bart Schaefer
2014-04-24  1:05           ` zsh-newuser-install Ray Andrews
2014-04-17 19:04     ` setopt interactivecomments 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=20140418115912.GC2388@isis.sigpipe.cz \
    --to=neuhauser@sigpipe.cz \
    --cc=schaefer@brasslantern.com \
    --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).