From: "Christoph (Stucki) von Stuckrad" <stucki@math.fu-berlin.de>
To: zsh-users@zsh.org
Subject: Re: Why is this happening in zsh?
Date: Fri, 16 Mar 2012 01:11:33 +0100 [thread overview]
Message-ID: <20120316001132.GB692@localhost.mi.fu-berlin.de> (raw)
In-Reply-To: <B80FC916-9DF0-47A7-AED2-6C307F389F88@gmail.com>
On Thu, 15 Mar 2012, Kyle Partridge wrote:
> So I alias these type of commands to use `noglob`.
> Does this solution make sense?
>
> Ex:
> alias find="noglob find"
This depends on what you really want to do and whether you alias
such command for a spcific case (good) or generally (bad).
Personally I prefer zsh's 'calling a missing * expansion an error',
because I normally tell the shell exactly what to do:
- eighter I write a simple * and 'globbing nothing' then IS an error
- or I use quoting, so I KNOW that the program called, will get the '*'
On the command line I mostly quote stars like: find ... -name \*foo\*
By doing this I keep the possibillity to do both in one comand,
like:
find some/tree/*/branches -name leaf\* -print
And the errormessage of the zsh keeps me from accidentally working
with real '*' in filenames or empty parameters, which can have VERY
strange results in daily work as a sysadmin :-)
Stucki
--
Christoph von Stuckrad * * |nickname |Mail <stucki@mi.fu-berlin.de> \
Freie Universitaet Berlin |/_*|'stucki' |Tel(Mo.,Mi.):+49 30 838-75 459|
Mathematik & Informatik EDV |\ *|if online| (Di,Do,Fr):+49 30 77 39 6600|
Takustr. 9 / 14195 Berlin * * |on IRCnet|Fax(home): +49 30 77 39 6601/
next prev parent reply other threads:[~2012-03-16 0:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 18:59 Anonymous
2012-03-14 19:29 ` Heorhi Valakhanovich
2012-03-14 23:19 ` Damien Thébault
2012-03-14 19:42 ` Stephane Chazelas
2012-03-14 19:49 ` Peter Stephenson
2012-03-15 10:13 ` Nomen Nescio
2012-03-15 18:00 ` Kyle Partridge
2012-03-16 0:11 ` Christoph (Stucki) von Stuckrad [this message]
2012-03-16 3:28 ` Benjamin R. Haskell
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=20120316001132.GB692@localhost.mi.fu-berlin.de \
--to=stucki@math.fu-berlin.de \
--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).