* On 2002.09.11, in <[EMAIL PROTECTED]>, * "Sven Dogbert Guckes" <[EMAIL PROTECTED]> wrote: > > "filename" stands for the name of a file. no more - no less.
Wrong, Sven. > > Sometimes even reading the manual is not sufficient. > > yep - understanding it is required, too. *ehem* Indeed. So why are you talking? > > The admirable terseness of UNIX/Linux documentation sometimes > > cause gaps in understanding which are not apparent to those > > who are already familiar with the topics being examined. > > I believe this is one of those times. > > au contraire. Ryan probably expected that he can use > any kind of commmand with parameters in this value. > and that's where he would be wrong because the > parameter is explicitly described as a *filename*. > or does it say "put parameters here" anywhere? > exactly. Wrong, Sven. Ryan probably did not expect that he can use any kind of command here, but we'd have to ask him, and it's not worth speculating about. The fact is that a "filename" argument, in mutt, is allowed to be either a filename, or an "abbreviation" for a filename (!, =foo, ~/foo, etc.), or a pipe. Yes, a pipe, Sven. Try it before spouting sometime. > and well, if this is not clear now > then, um, get the windows version. Do you take your own advice, Sven? Ryan: The pipe symbol needs to be inside the quotation marks, but it's not allowed to take arguments. source "~/.mutt/hooks/folder.recip.lists.sh |" source "~/.mutt/hooks/folder.recip.people.sh |" These could theoretically be symlinked to the same script, and figure out what to do by examining $0. -- -D. We establised a fine coffee. What everybody can say Sun Project, APC/UCCO TASTY! It's fresh, so-mild, with some special coffee's University of Chicago bitter and sourtaste. "LET'S HAVE SUCH A COFFEE! NOW!" [EMAIL PROTECTED] Please love CAFE MIAMI. Many thanks.
