Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Manpage improvement
- X-seq: zsh-users 1828
- From: Johan Sundström <johsu650@xxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxxxxxxx
- Subject: Manpage improvement
- Date: Sun, 27 Sep 1998 17:47:48 +0200 (MET DST)
I often find myself using constructs like this one:
oldifs=$IFS;IFS="
";foo=($(locate Argentina|grep .mp3));IFS=$oldifs;x11amp "${(@)foo}"
to supply x11amp with a set of quoted filenames on the
commandline. I was just about to ask for a more convenient way of
doing this, when I suddenly understood a section of the manual, and
then had no less than three other synonymous ways of doing this:
x11amp "${(@s:
:)$(locate Argentina|grep .mp3)}"
x11amp "${(@ps:\n:)$(locate Argentina|grep .mp3)}"
x11amp "${(@f)$(locate Argentina|grep .mp3)}"
It really is sad that it is so difficult to parse the man pages. Why
is the documentation in this sad state? Is it because it's more fun
coding the features than it is documenting them?
I hope this might qualify as an example to spice up future zsh
manpages.
/Johan Sundström,
**************************************************************
* Alsättersgatan 5A/34 * Master of Science student in *
* S-584 35 LINKÖPING * Computer Science and Engineering *
* SWEDEN * at Linköping University *
**************************************************************
* johsu650@xxxxxxxxxxxxxx *
***************************
Messages sorted by:
Reverse Date,
Date,
Thread,
Author