From: Donald Allen <donald...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: More, manpages
Date: Wed, 16 Sep 2015 13:58:56 -0700 (PDT) [thread overview]
Message-ID: <ebc903cd-bb25-4547-83a0-1db932e5987d@googlegroups.com> (raw)
In-Reply-To: <464b2498-24e7-49aa-9df8-ff3eff1fba8f@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1402 bytes --]
On Wednesday, September 16, 2015 at 2:38:47 PM UTC-4, Duncaen wrote:
>
> About 'v', do you have setup $EDITOR or $VISUAL in your shell environment.
> On the problem with 'b' or '^b', the man page of more says it only works
> with files and not with pipes, is this the problem?
>
Sounds very plausible. I'm used to the man on Arch, which presents the man
pages in a vim-like environment (maybe it is vim?). The simple vi commands
work, and 'gg' gets you to the top, as in vim. The use of more,
particularly if you can't scroll back, is big step backwards (pun intended).
> For me it works as expected with st as terminal emulator.
>
That would not seem to be consistent with your pipe theory above. Why
should the terminal emulator matter if more won't scroll back when its
input is a pipe? Nonetheless, I tried installing st and its behavior is
bizarre. Every character displayed has a lot of whitespace after it,
including what you type. I could not get man to work and gave up. I am
running a newly installed Void on a PC with an AMD processor, ATI video
hardware and no desktop system, just a window manager (dwm).
>
> Am Mittwoch, 16. September 2015 20:29:25 UTC+2 schrieb Donald Allen:
>>
>> When displaying manpages with man, more is used. Typing '?' at more
>> claims that 'b' or 'ctrl-b' will scroll backwards. It does not work. The
>> 'v' command doesn't work either.
>>
>
[-- Attachment #1.2: Type: text/html, Size: 2105 bytes --]
next prev parent reply other threads:[~2015-09-16 20:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 18:29 Donald Allen
2015-09-16 18:38 ` Duncaen
2015-09-16 20:58 ` Donald Allen [this message]
2015-09-17 8:02 ` Duncaen
2015-09-17 7:01 ` Pierre Bourgin
2015-09-17 11:14 ` Donald Allen
2015-09-17 14:15 ` Juan RP
2015-09-17 14:32 ` Christian Neukirchen
2015-09-17 22:09 ` Donald Allen
2015-09-18 8:12 ` Seth Hover
2015-09-18 13:28 ` Donald Allen
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=ebc903cd-bb25-4547-83a0-1db932e5987d@googlegroups.com \
--to="donald..."@gmail.com \
--cc="void..."@googlegroups.com \
/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.
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).