clone 363250 -1
reassign -1 general
retitle -1 PAGER as a pipeline
tags 363250 fixed-upstream
thanks
On Sun, Apr 23, 2006 at 09:52:34PM +0200, Loïc Minier wrote:
Yes, indeed, the root of the problem is the change of support for
pipelines. However, I'm not sure that pipelines worked in the
Processing commands for cont...@bugs.debian.org:
clone 363250 -1
Bug#363250: please clarify in the man manpage how $PAGER is invoked
Bug 363250 cloned as bug 538022.
reassign -1 general
Bug#538022: please clarify in the man manpage how $PAGER is invoked
Bug reassigned from package `man-db' to
On Sun, Apr 23, 2006, Manoj Srivastava wrote:
Historically, if my memory serves me correctly, one used PAGER
to specify the program, and the default arguments. PAGER essentially
worked as an shell alias:
PAGER= less -cim
And then you could either pipe thigs to ti, or call it on a
On 22 Apr 2006, Loïc Minier outgrape:
On Sat, Apr 22, 2006, Manoj Srivastava wrote:
There are two use cases that any pager directive must address:
1) The program is going to generate output which must be piped to
a pager
2) The program want to send a file to the user.
I agree that these
On Sun, Apr 23, 2006, Manoj Srivastava wrote:
Since allowing pipelines seems to be the motivating factor
here, we do need to solve that, I think.
Yes, indeed, the root of the problem is the change of support for
pipelines. However, I'm not sure that pipelines worked in the use case
Manoj Srivastava [EMAIL PROTECTED] writes:
I read it. I still think that my answer suffices: Put your
pipeline in a script, and set that to PAGER.
Your answer doesn't suffice, because it's not what people expect --
PAGER has historically (for a _long_ time) supported arguments being
On 23 Apr 2006, Loïc Minier verbalised:
On Sun, Apr 23, 2006, Manoj Srivastava wrote:
Since allowing pipelines seems to be the motivating factor
here, we do need to solve that, I think.
Yes, indeed, the root of the problem is the change of support for
pipelines. However, I'm not sure that
On 23 Apr 2006, Miles Bader spake thusly:
Manoj Srivastava [EMAIL PROTECTED] writes:
I read it. I still think that my answer suffices: Put your
pipeline in a script, and set that to PAGER.
Your answer doesn't suffice, because it's not what people expect
-- PAGER has historically (for a
On 21 Apr 2006, Loïc Minier spake thusly:
Hi,
On Fri, Apr 21, 2006, Manoj Srivastava wrote:
Here is my solution for using vim + script as a pager; similar
mechanisms can be used to use plain vim as PAGER as well.
Nice, I suggest filing a new bug against vim to propose this as a
contrib
On Sat, Apr 22, 2006, Manoj Srivastava wrote:
#363250 is more about documenting the semantics of $PAGER (whether
it can uses sh syntax, or whether it's a command with parameters
separated with spaces), to be documented in man man, and/or policy.
Err, we should define how it behaves,
On 22 Apr 2006, Loïc Minier spake thusly:
On Sat, Apr 22, 2006, Manoj Srivastava wrote:
363250 is more about documenting the semantics of $PAGER (whether
it can uses sh syntax, or whether it's a command with parameters
separated with spaces), to be documented in man man, and/or
policy.
Err,
Hi,
On Sat, Apr 22, 2006, Manoj Srivastava wrote:
Please read again the original report, the submitter wanted to have
a pipe of commands in $PAGER, he said this worked in the past, and
works on other distros. He did not want to simply be able to use
$PAGER on a file or to pipe
Hi,
Here is my solution for using vim + script as a pager; similar
mechanisms can be used to use plain vim as PAGER as well.
,
| #!/bin/bash
| # Shell script to start Vim with less.vim.
| # Read stdin if no arguments were given.
|
| #VRUNTIME=/usr/share/vim/vim64/
|
Hi,
On Fri, Apr 21, 2006, Manoj Srivastava wrote:
Here is my solution for using vim + script as a pager; similar
mechanisms can be used to use plain vim as PAGER as well.
Nice, I suggest filing a new bug against vim to propose this as a
contrib script, or to ship it as
On Fri, Apr 21, 2006 at 08:36:10AM -0500, Manoj Srivastava wrote:
Hi,
Here is my solution for using vim + script as a pager; similar
mechanisms can be used to use plain vim as PAGER as well.
[snip script]
There is already a less.sh that does this, which is in the same
directory
On Thu, Apr 20, 2006 at 12:05:16AM -0500, Manoj Srivastava wrote:
I expect to be able to pipe stuff to $PAGER, or invoke $PAGER
on a text file, like so:
% cat~/.bash_profile | $PAGER
% $PAGER ~/.bash_profile
That seems to be an awfully user-specific expectation, given that
you
On 20 Apr 2006, Steve Langasek spake thusly:
On Thu, Apr 20, 2006 at 12:05:16AM -0500, Manoj Srivastava wrote:
I expect to be able to pipe stuff to $PAGER, or invoke $PAGER
on a text file, like so:
% cat~/.bash_profile | $PAGER
% $PAGER ~/.bash_profile
That seems to be an awfully
Henning Makholm [EMAIL PROTECTED] writes:
Policy does not really specify how to handle $PAGER and its friends,
but I have always assumed that it was OK for a package to do things
like (error checking omitted for clarity):
...
In that case, PAGER has to be set to just the name of a program,
On Wed, Apr 19, 2006, Henning Makholm wrote:
Policy does not really specify how to handle $PAGER and its friends
Feel free to clone against policy, I agree that it would be cleaner to
define how it should be called in policy (but it would still be nice to
have man man document how $PAGER is
On 18 Apr 2006, Loïc Minier uttered the following:
reassign 363250 man retitle 363250 Please clarify how $PAGER is
invoked in the man manpage stop
Hi,
On Tue, Apr 18, 2006, Rohan Dhruva wrote:
export PAGER=col -b | view -c 'set ft=man nomod nolist
titlestring=MANPAGE' -
This $PAGER
On Wed, Apr 19, 2006 at 09:12:04AM -0500, Manoj Srivastava wrote:
which explicitely calls sh -c to handle pipes and quotes in the
expected way.
I expect to be able to pipe stuff to $PAGER, or invoke $PAGER
on a text file, like so:
% cat~/.bash_profile | $PAGER
% $PAGER
On 19 Apr 2006, Steve Langasek uttered the following:
On Wed, Apr 19, 2006 at 09:12:04AM -0500, Manoj Srivastava wrote:
which explicitely calls sh -c to handle pipes and quotes in the
expected way.
I expect to be able to pipe stuff to $PAGER, or invoke $PAGER
on a text file, like so:
%
Package: general
Severity: normal
I want to use vim as my man pager. On other distros, and on sarge, I use this
line
in my .bashrc
# Set vim as the man pager
export PAGER=col -b | view -c 'set ft=man nomod nolist titlestring=MANPAGE' -
In those systems, it displays the man page properly in
On 4/18/06, Rohan Dhruva [EMAIL PROTECTED] wrote:
Package: general
Severity: normal
I want to use vim as my man pager. On other distros, and on sarge, I use this
line
in my .bashrc
# Set vim as the man pager
export PAGER=col -b | view -c 'set ft=man nomod nolist titlestring=MANPAGE'
-
At 1145360089 past the epoch, Rohan Dhruva wrote:
# Set vim as the man pager
export PAGER=col -b | view -c 'set ft=man nomod nolist titlestring=MANPAGE'
-
In those systems, it displays the man page properly in vim with full
color. However, on using the same line on sid, the error given is
reassign 363250 man
retitle 363250 Please clarify how $PAGER is invoked in the man manpage
stop
Hi,
On Tue, Apr 18, 2006, Rohan Dhruva wrote:
export PAGER=col -b | view -c 'set ft=man nomod nolist titlestring=MANPAGE'
-
This $PAGER definition makes the assumption that it's passed to
Processing commands for [EMAIL PROTECTED]:
reassign 363250 man
Bug#363250: general: Custom PAGER gives error on sid, but works on sarge
Warning: Unknown package 'man'
Bug reassigned from package `general' to `man'.
retitle 363250 Please clarify how $PAGER is invoked in the man manpage
reassign 363250 man-db
retitle 363250 please clarify in the man manpage how $PAGER is invoked
stop
Hi,
On Tue, Apr 18, 2006, Rohan Dhruva wrote:
I suggest you use:
export PAGER=sh -c \col -b | view -c 'set ft=man nomod nolist
titlestring=MANPAGE' -\
That didnt work.
On 4/18/06, Loïc Minier [EMAIL PROTECTED] wrote:
reassign 363250 manretitle 363250 Please clarify how $PAGER is invoked in the man manpagestopHi,On Tue, Apr 18, 2006, Rohan Dhruva wrote: export PAGER=col -b | view -c 'set ft=man nomod nolist titlestring=MANPAGE' -
This $PAGER definition makes the
Also, IMHO, topic is a bit wrong .. this bug applies to all man pages, not only the man manpage. Regards,-- Rohan DhruvaProud GNU/Linux user.Windows: Where do you want to go today?
Linux: Where do you want to go tomorrow?FreeBSD: Are you guys coming or what?http://www.dhruva.be/
retitle 363250 Please clarify how $PAGER is invoked for any manpage.stopSorry for the spam, I did not know I can retitle bugs myself.-- Rohan DhruvaProud GNU/Linux user.Windows: Where do you want to go today?
Linux: Where do you want to go tomorrow?FreeBSD: Are you guys coming or
On 4/18/06, Loïc Minier [EMAIL PROTECTED] wrote:
reassign 363250 man-db
retitle 363250 please clarify in the man manpage how $PAGER is invoked
stop
Hi,
On Tue, Apr 18, 2006, Rohan Dhruva wrote:
I suggest you use:
export PAGER=sh -c \col -b | view -c 'set ft=man nomod
* Rohan Dhruva [Tue, 18 Apr 2006 22:30:29 +0530]:
view: -s option is only applicable to ex.
% /usr/sbin/update-alternatives --display view | grep current
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at
On Tue, Apr 18, 2006, Adeodato Simó wrote:
view: -s option is only applicable to ex.
% /usr/sbin/update-alternatives --display view | grep current
(I redirected the discussion to the bug report for the second time;
FYI, it was nview.)
--
Loïc Minier [EMAIL PROTECTED]
You can
Scripsit Loïc Minier [EMAIL PROTECTED]
I suggest you use:
export PAGER=sh -c \col -b | view -c 'set ft=man nomod nolist
titlestring=MANPAGE' -\
which explicitely calls sh -c to handle pipes and quotes in the
expected way.
Policy does not really specify how to handle $PAGER and its
35 matches
Mail list logo
