From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: nslookup (function) problem
Date: Fri, 5 May 2000 12:23:59 +0400 [thread overview]
Message-ID: <000001bfb66b$437e74a0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200005041449.QAA11775@beta.informatik.hu-berlin.de>
>
> - Does it use other environment variables? If so, which. In which
> order? I.e. which one overrides all others?
> - If $PAGER is not set, does it use a default pager or does it just
> dump the help to the output? I.e. is it enough to locally unset
> PAGER in nslookup() or should we locally export PAGER=cat?
>
Unsetting PAGER runs it through `more' (obviously, default - but this
PAGER story is not documented anywhere). Setting PAGER=cat does the
trick ... almost. The problem is, now the ability to page output is
lost.
Hmm ... may be extend nslookup function in the same way (probably, using
style to turn it on/off)? If output has more lines than fit on screen,
run it through PAGER?
-andrej
next prev parent reply other threads:[~2000-05-05 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-04 14:49 Sven Wischnowsky
2000-05-05 8:23 ` Andrej Borsenkow [this message]
2000-05-05 8:27 ` zpty read hangs (RE: nslookup (function) problem) Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
2000-05-05 8:55 nslookup (function) problem Sven Wischnowsky
2000-05-05 10:01 ` Andrej Borsenkow
2000-05-05 8:47 Sven Wischnowsky
2000-05-05 8:55 ` Peter Stephenson
2000-05-05 14:53 ` Bart Schaefer
2000-05-04 13:33 PATCH: Re: zpty and controlling tty (and other fd's) Sven Wischnowsky
2000-05-04 13:48 ` nslookup (function) problem Andrej Borsenkow
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='000001bfb66b$437e74a0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).