From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: somehow offtopic: looping filenames
Date: Mon, 20 Feb 2012 11:05:30 -0800 [thread overview]
Message-ID: <120220110530.ZM450@torch.brasslantern.com> (raw)
In-Reply-To: <20120220181650.GA11514@solfire>
On Feb 20, 7:16pm, meino.cramer@gmx.de wrote:
}
} I habe a loop like this:
}
} for fn *
} do
} flac $fn
} done
}
} Unfortunately, some file have 'illegal' filenames
} which parts flac sees as unknown commmand options or as
} two file and the loop fails.
Try this:
for fn *
do
flac $fn:a
done
The :a modifier expands $fn into a full path including removing any
mentions of "./" and "../". Think of it as a clean "$PWD/$fn".
If you don't have a recent-enough zsh for :a to be supported or it is
for some reason important to avoid the full path, try
flac ${${fn:h}-.}/${fn:t}
If that's still confusing it because e.g. you have SH_WORD_SPLIT turned
on, wrap the expression in double quotes.
next prev parent reply other threads:[~2012-02-20 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 18:16 meino.cramer
2012-02-20 18:38 ` Frank Terbeck
2012-02-20 19:05 ` Bart Schaefer [this message]
2012-02-21 12:35 ` Stephen Blott
2012-02-21 13:35 ` Frank Terbeck
2012-02-22 23:41 ` Mark van Dijk
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=120220110530.ZM450@torch.brasslantern.com \
--to=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).