From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh workers <zsh-workers@sunsite.dk>
Subject: suffix aliases behaving weird?
Date: Mon, 25 Jun 2007 18:26:56 +0200 [thread overview]
Message-ID: <20070625162656.GA2730@fsst.voodoo.lan> (raw)
Hi list!
Consider the following:
[snip]
% alias -s ogg='ogg123'
% /mnt/audio/music/S/Slayer\ -\ South\ Of\ Heaven\ -\ 01\ -\ South\ Of\ Heaven.ogg
[plays fine]
% "/mnt/audio/music/S/Slayer - South Of Heaven - 01 - South Of Heaven.ogg"
zsh: permission denied: /mnt/audio/music/S/Slayer - South Of Heaven - 01 - South Of Heaven.ogg
[snap]
Bug or intended behaviour?
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
next reply other threads:[~2007-06-25 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 16:26 Frank Terbeck [this message]
2007-06-25 17:23 ` Peter Stephenson
2007-06-25 17:40 ` Frank Terbeck
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=20070625162656.GA2730@fsst.voodoo.lan \
--to=ft@bewatermyfriend.org \
--cc=zsh-workers@sunsite.dk \
/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).