On Sun, Jan 04, 2004 at 02:51:34PM -0500, Bijan Soleymani wrote:
> On Sun, Jan 04, 2004 at 01:01:10PM -0500, Antonio Rodriguez wrote:
> > After trying different options, the nicest looking version is obtained
> > by processing the source texinfo file:
> > 1. get the source from http://ftp.gnu.org/p
On Sun, Jan 04, 2004 at 01:01:10PM -0500, Antonio Rodriguez wrote:
> After trying different options, the nicest looking version is obtained
> by processing the source texinfo file:
> 1. get the source from http://ftp.gnu.org/pub/gnu/coreutils/
> 2. unpack it, dive into doc directory
> 3. texi2dvi c
On Sun, Jan 04, 2004 at 03:02:04AM -0500, Antonio Rodriguez wrote:
> On Sun, Jan 04, 2004 at 02:40:49AM -0500, Bijan Soleymani wrote:
> > On Sun, Jan 04, 2004 at 02:05:26AM -0500, Antonio Rodriguez wrote:
> > > There was a thread a while ago about reformatting man pages for pretty
> > > viewing and
Antonio Rodriguez([EMAIL PROTECTED]) is reported to have said:
> On Sun, Jan 04, 2004 at 02:40:49AM -0500, Bijan Soleymani wrote:
> > On Sun, Jan 04, 2004 at 02:05:26AM -0500, Antonio Rodriguez wrote:
> > > There was a thread a while ago about reformatting man pages for pretty
> > > viewing and pri
On Sun, Jan 04, 2004 at 02:40:49AM -0500, Bijan Soleymani wrote:
> On Sun, Jan 04, 2004 at 02:05:26AM -0500, Antonio Rodriguez wrote:
> > There was a thread a while ago about reformatting man pages for pretty
> > viewing and printing. I wonder if there are any similar tricks or
> > ideas for the in
On Sun, Jan 04, 2004 at 02:05:26AM -0500, Antonio Rodriguez wrote:
> There was a thread a while ago about reformatting man pages for pretty
> viewing and printing. I wonder if there are any similar tricks or
> ideas for the info pages. I didn't want to awake that sleeping
> thread, so I started thi
There was a thread a while ago about reformatting man pages for pretty
viewing and printing. I wonder if there are any similar tricks or
ideas for the info pages. I didn't want to awake that sleeping
thread, so I started this with a similar name.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
On Thu, Dec 18, 2003 at 03:30:04PM +0100, Jan Minar wrote:
> On Thu, Dec 18, 2003 at 12:47:35PM +, Colin Watson wrote:
> > Make sure you have no saved cat pages and try again? (A different line
> > length *should* bypass cat pages, but ...)
>
> | $ ls /var/cache/man/cat1/
> | pon.1.gz
> | vloc
On Thu, Dec 18, 2003 at 12:47:35PM +, Colin Watson wrote:
> On Thu, Dec 18, 2003 at 02:14:48AM +0100, Jan Minar wrote:
> > On Thu, Dec 18, 2003 at 12:50:54AM +, Colin Watson wrote:
> > > On Thu, Dec 18, 2003 at 12:41:41AM +, Colin Watson wrote:
> > > > The '--pager cat' continues to be
On Thu, Dec 18, 2003 at 02:09:27AM +0100, Jan Minar wrote:
> On Thu, Dec 18, 2003 at 12:41:41AM +, Colin Watson wrote:
> > On Wed, Dec 17, 2003 at 10:14:54PM +0100, Jan Minar wrote:
> > > This actually should not work, you have to tell man(1) it should
> > > send the formatted manpage to stdout
On Thu, Dec 18, 2003 at 02:14:48AM +0100, Jan Minar wrote:
> On Thu, Dec 18, 2003 at 12:50:54AM +, Colin Watson wrote:
> > On Thu, Dec 18, 2003 at 12:41:41AM +, Colin Watson wrote:
> > > The '--pager cat' continues to be unnecessary here; $COLUMNS is still
> > > honoured. I prefer using the
On Wed, Dec 17, 2003 at 10:14:54PM +0100, Jan Minar wrote:
> On Wed, Dec 17, 2003 at 01:07:35PM -0500, Lou Losee wrote:
> > * Gruessle <[EMAIL PROTECTED]> [2003-12-17 12:21]:
> > >
> > > Is there a way I can open man files in a text editor.
> > > I like to print one but have not configured my prin
On Thu, Dec 18, 2003 at 12:50:54AM +, Colin Watson wrote:
> On Thu, Dec 18, 2003 at 12:41:41AM +, Colin Watson wrote:
> > On Wed, Dec 17, 2003 at 10:14:54PM +0100, Jan Minar wrote:
> > > Now we want the lines narrower than the default 80 characters (I guess
> > > this won't work if man(1) i
On Thu, Dec 18, 2003 at 12:41:41AM +, Colin Watson wrote:
> On Wed, Dec 17, 2003 at 10:14:54PM +0100, Jan Minar wrote:
> > > Try man xxx | col -b > text-filename
> >
> > This actually should not work, you have to tell man(1) it should send the
> > formatted manpage to stdout, instead of messin
On Thu, Dec 18, 2003 at 12:41:41AM +, Colin Watson wrote:
> On Wed, Dec 17, 2003 at 10:14:54PM +0100, Jan Minar wrote:
> > Now we want the lines narrower than the default 80 characters (I guess
> > this won't work if man(1) is connected to the terminal, so the pipe is
> > vital here (that's why
On Wed, Dec 17, 2003 at 11:14:09AM -0800, [EMAIL PROTECTED] wrote:
> That will work for small manpages. But you will not like
> what it does for big ones. Here is a better way.
>
> 1. Find the manpage source.
>
> $ whereis bash
> bash: /bin/bash /etc/bash.bashrc /usr/share/man/man1/bash.1.gz
>
On Wed, Dec 17, 2003 at 10:14:54PM +0100, Jan Minar wrote:
> On Wed, Dec 17, 2003 at 01:07:35PM -0500, Lou Losee wrote:
> > * Gruessle <[EMAIL PROTECTED]> [2003-12-17 12:21]:
> > > Is there a way I can open man files in a text editor.
> > > I like to print one but have not configured my printer jet
On Wed, Dec 17, 2003 at 11:26:27PM +0100, Jan Minar wrote:
> On Wed, Dec 17, 2003 at 04:55:29PM -0500, Lou Losee wrote:
> > > > Try man xxx | col -b > text-filename
> > >
> > > This actually should not work, you have to tell man(1) it should send the
> > > formatted manpage to stdout, instead of m
[This message has also been posted to linux.debian.user.]
In article <[EMAIL PROTECTED]>, Lou Losee wrote:
> * Gruessle <[EMAIL PROTECTED]> [2003-12-17 12:21]:
>>
>> Is there a way I can open man files in a text editor.
>> I like to print one but have not configured my printer jet.
>> So I will em
Lou Losee wrote:
* Gruessle <[EMAIL PROTECTED]> [2003-12-17 12:21]:
Is there a way I can open man files in a text editor.
I like to print one but have not configured my printer jet.
So I will email it to my other pc.
Try man xxx | col -b > text-filename
it will give you a text version of the man
On Wed, Dec 17, 2003 at 04:55:29PM -0500, Lou Losee wrote:
> > > Try man xxx | col -b > text-filename
> >
> > This actually should not work, you have to tell man(1) it should send the
> > formatted manpage to stdout, instead of messing with the pager.
> > Replace `foo' with the desired program nam
* Jan Minar <[EMAIL PROTECTED]> [2003-12-17 16:23]:
> On Wed, Dec 17, 2003 at 01:07:35PM -0500, Lou Losee wrote:
> > * Gruessle <[EMAIL PROTECTED]> [2003-12-17 12:21]:
> > >
> > > Is there a way I can open man files in a text editor.
> > > I like to print one but have not configured my printer jet
On Wed, Dec 17, 2003 at 01:07:35PM -0500, Lou Losee wrote:
> * Gruessle <[EMAIL PROTECTED]> [2003-12-17 12:21]:
> >
> > Is there a way I can open man files in a text editor.
> > I like to print one but have not configured my printer jet.
> > So I will email it to my other pc.
> >
> Try man xxx |
On Wed, 2003-12-17 at 18:22, Gruessle wrote:
> Is there a way I can open man files in a text editor.
> I like to print one but have not configured my printer jet.
> So I will email it to my other pc.
# man -T ps
will produce the manual page for in postcript format. Maybe
you prefer a plain text
"Gruessle" <[EMAIL PROTECTED]> writes:
> Is there a way I can open man files in a text editor.
Emacs has a major mode for editing 'roff files, like man pages, if
that's what you're looking for.
> I like to print one but have not configured my printer jet.
'man -t' will produce postscript from a
* Gruessle <[EMAIL PROTECTED]> [2003-12-17 12:21]:
>
> Is there a way I can open man files in a text editor.
> I like to print one but have not configured my printer jet.
> So I will email it to my other pc.
>
Try man xxx | col -b > text-filename
it will give you a text version of the man page.
Is there a way I can open man files in a text editor.
I like to print one but have not configured my printer jet.
So I will email it to my other pc.
--
Gruessle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
27 matches
Mail list logo
