From: Hrvoje Niksic <hniksic@srce.hr>
To: vlefevre@ens-lyon.fr (Vincent Lefevre)
Cc: zsh-users@math.gatech.edu
Subject: Re: null commands...
Date: 26 Oct 1996 20:01:04 +0100 [thread overview]
Message-ID: <kigaft94kjz.fsf@jagor.srce.hr> (raw)
In-Reply-To: vlefevre@ens-lyon.fr's message of Sat, 26 Oct 1996 20:33:45 +0200
Vincent Lefevre (vlefevre@ens-lyon.fr) wrote:
> This wouldn't always work. $PAGER may have arguments, e.g. "less -is".
> But $READNULLCMD can't:
[...]
> Is it a bug?
No, it's another gripe for READNULLCMD (regardless of $PAGER): It
should be parsed as command-line string. So
< file
should be translated to
${=READNULLCMD} < file
instead of $READNULLCMD < file, which is currently the case.
With the $PAGER changes zsh would do the following:
If READNULLCMD is non-empty, `< file' means `${=READNULLCMD} < file',
else if PAGER is non-empty, `< file' means `${=PAGER} < file',
else `< file' means `more < file'.
I think this behaviour would be well-accepted by the users which
generally set PAGER to whatever they like (e.g. less or "less -i").
Would it be hard to code to exec.c?
--
} WWW: World-Wide-Waste. Waste management corporation, which
} handles the billions of tons of garbage generated by just
} about everybody these days.
} You owe the Oracle a good book. In HyperText, please.
next prev parent reply other threads:[~1996-10-26 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-25 22:33 Varadarajan
1996-10-26 7:51 ` Geoff Wing
1996-10-26 14:21 ` Hrvoje Niksic
1996-10-26 15:05 ` Zefram
1996-10-26 15:11 ` Hrvoje Niksic
1996-10-26 18:33 ` Vincent Lefevre
1996-10-26 19:01 ` Hrvoje Niksic [this message]
1996-10-26 19:18 ` Zefram
1996-10-28 11:53 ` Geoff Wing
1996-10-28 12:20 ` Hrvoje Niksic
1996-10-28 13:37 ` Zefram
1996-10-26 15:21 alain (a.) caron
[not found] <no.id>
1996-10-28 22:15 ` Geoff Wing
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=kigaft94kjz.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
--cc=vlefevre@ens-lyon.fr \
--cc=zsh-users@math.gatech.edu \
/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).