From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-users@zsh.org
Subject: Re: INTERACTIVE_COMMENTS - why?
Date: Wed, 24 Aug 2011 19:05:51 +0200 [thread overview]
Message-ID: <87pqjug2og.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <110824080039.ZM25273@torch.brasslantern.com> (Bart Schaefer's message of "Wed, 24 Aug 2011 08:00:39 -0700")
Bart Schaefer wrote:
> On Aug 24, 3:17pm, Frank Terbeck wrote:
> } Fair enough. But then again, who wouldn't set `extended_glob'? ;)
>
> I don't. I have a little "eglob" function that I use as a prefix to
> the command line when I want extended globbing. (Obviously I spend
> too much of my time cleaning out backup files that have "#" and "~"
> in their names.)
Hm. I wonder how you're doing that. I've ended up with the following:
alias eglob='noalias eglob'
function eglob() {
emulate -L zsh
setopt extended_glob
${~"${argv[@]}"};
}
Are you doing something similar or is there a neat trick to do that
differently?
> } Still: The choice of having it unset by default might still be for
> } emulating csh behaviour. Or maybe not. If someone can remember why
> } it's off by default, I'd be glad to hear about it.
>
> It's almost certainly related to csh. Zsh was first invented as a
> shell to bring Bourne shell parsing regularity and scripting features
> to users (university students in a BSD Unix environment) who had been
> introduced to Unix via csh. Anything that would overtly confuse a
> csh-er who was typing a simple one-liner at the prompt was avoided.
Okay. Thanks for clearing that up.
Regards, Frank
next prev parent reply other threads:[~2011-08-24 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 12:02 Frank Terbeck
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 [this message]
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=87pqjug2og.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).