Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #240735 > unrolled thread

What do we have that will save a manpage as we see it on-screen

Back to article view | Back to linux.debian.user

Contents

  What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-01 18:30 +0200
    Re: What do we have that will save a manpage as we see it on-screen Larry Martell <larry.martell@gmail.com> - 2021-10-01 18:40 +0200
      Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-01 23:00 +0200
        Re: What do we have that will save a manpage as we see it on-screen Greg Wooledge <greg@wooledge.org> - 2021-10-01 23:10 +0200
          Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-01 23:30 +0200
            Re: What do we have that will save a manpage as we see it on-screen Greg Wooledge <greg@wooledge.org> - 2021-10-01 23:40 +0200
        Re: What do we have that will save a manpage as we see it on-screen Fred <fred@blakemfg.com> - 2021-10-02 02:50 +0200
          Re: What do we have that will save a manpage as we see it on-screen Greg Wooledge <greg@wooledge.org> - 2021-10-02 03:00 +0200
            Re: What do we have that will save a manpage as we see it on-screen David Wright <deblis@lionunicorn.co.uk> - 2021-10-02 05:00 +0200
              Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-02 13:30 +0200
                Re: What do we have that will save a manpage as we see it on-screen Greg Wooledge <greg@wooledge.org> - 2021-10-02 15:00 +0200
            Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-02 13:20 +0200
          Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-02 11:40 +0200
    Re: What do we have that will save a manpage as we see it on-screen Cindy Sue Causey <butterflybytes@gmail.com> - 2021-10-01 18:50 +0200
      Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-01 23:10 +0200
    Re: What do we have that will save a manpage as we see it on-screen Lee <ler762@gmail.com> - 2021-10-01 20:00 +0200
      Re: What do we have that will save a manpage as we see it  on-screen Jude DaShiell <jdashiel@panix.com> - 2021-10-01 20:10 +0200
      Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-01 23:10 +0200
        Re: What do we have that will save a manpage as we see it on-screen Greg Wooledge <greg@wooledge.org> - 2021-10-01 23:20 +0200
          Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-01 23:40 +0200
            Re: What do we have that will save a manpage as we see it on-screen Brian <ad44@cityscape.co.uk> - 2021-10-02 17:20 +0200
              Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-02 21:50 +0200
                Re: What do we have that will save a manpage as we see it on-screen Brian <ad44@cityscape.co.uk> - 2021-10-02 22:10 +0200
                  Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-02 23:40 +0200
                Re: What do we have that will save a manpage as we see it  on-screen Jude DaShiell <jdashiel@panix.com> - 2021-10-02 23:10 +0200
    Re: What do we have that will save a manpage as we see it on-screen Greg Wooledge <greg@wooledge.org> - 2021-10-01 21:50 +0200
      Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-01 23:20 +0200
    Re: What do we have that will save a manpage as we see it on-screen Eric S Fraga <e.fraga@ucl.ac.uk> - 2021-10-02 13:50 +0200
      Re: What do we have that will save a manpage as we see it on-screen Gene Heskett <gheskett@shentel.net> - 2021-10-02 14:50 +0200
      Re: What do we have that will save a manpage as we see it on-screen Greg Wooledge <greg@wooledge.org> - 2021-10-02 15:10 +0200
        Re: What do we have that will save a manpage as we see it on-screen Brian <ad44@cityscape.co.uk> - 2021-10-02 16:40 +0200
          Re: What do we have that will save a manpage as we see it on-screen Eric S Fraga <e.fraga@ucl.ac.uk> - 2021-10-02 18:00 +0200
            Re: What do we have that will save a manpage as we see it on-screen Brian <ad44@cityscape.co.uk> - 2021-10-02 19:40 +0200
        Re: What do we have that will save a manpage as we see it on-screen Eric S Fraga <e.fraga@ucl.ac.uk> - 2021-10-02 18:00 +0200

Page 1 of 2  [1] 2  Next page →

#240735 — What do we have that will save a manpage as we see it on-screen

Greetings all;

With the man markup subtracted, so what we save is exactly what we see.

Thanks.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [next] | [standalone]

#240736

On Fri, Oct 1, 2021 at 12:25 PM Gene Heskett <gheskett@shentel.net> wrote:
>
> Greetings all;
>
> With the man markup subtracted, so what we save is exactly what we see.

Maybe one of these man option will work for you:

       -t, --troff
              Use groff -mandoc to format the manual page to stdout.
This option is not required in conjunction with -H, -T, or -Z.

       -T[device], --troff-device[=device]
              This  option is used to change groff (or possibly
troff's) output to be suitable for a device other than the default.
It implies -t.  Examples (provided with Groff-1.17)
              include dvi, latin1, ps, utf8, X75 and X100.

       -H[browser], --html[=browser]
              This option will cause groff to produce HTML output, and
will display that output in a web browser.  The choice of browser is
determined by the optional browser  argument
              if  one  is provided, by the $BROWSER environment
variable, or by a compile-time default if that is unset (usually
lynx).  This option implies -t, and will only work with
              GNU troff.

       -X[dpi], --gxditview[=dpi]
              This option displays the output of groff in a graphical
window using the gxditview program.  The dpi (dots per inch) may be
75, 75-12, 100, or 100-12, defaulting  to  75;
              the -12 variants use a 12-point base font.  This option
implies -T with the X75, X75-12, X100, or X100-12 device respectively.

       -Z, --ditroff
              groff  will  run  troff  and then use an appropriate
post-processor to produce output suitable for the chosen device.  If
groff -mandoc is groff, this option is passed to
              groff and will suppress the use of a post-processor.  It
implies -t.

man -Tpdf will get you a PDF.

[toc] | [prev] | [next] | [standalone]

#240753

On Friday 01 October 2021 12:34:16 Larry Martell wrote:

man -t /path/to/man/file >file.txt
groff -mandoc /path/to/man/file > file.txt, both quadrupled the size with 
lots more markup.

Not what I want obviously.

Thanks Larry.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#240755

On Fri, Oct 01, 2021 at 04:59:25PM -0400, Gene Heskett wrote:
> On Friday 01 October 2021 12:34:16 Larry Martell wrote:
> 
> man -t /path/to/man/file >file.txt
> groff -mandoc /path/to/man/file > file.txt, both quadrupled the size with 
> lots more markup.
> 
> Not what I want obviously.

There is nothing obvious here.  What do you want?  Why?  What are you
going to do with the resulting file(s)?

[toc] | [prev] | [next] | [standalone]

#240759

On Friday 01 October 2021 17:01:56 Greg Wooledge wrote:

> On Fri, Oct 01, 2021 at 04:59:25PM -0400, Gene Heskett wrote:
> > On Friday 01 October 2021 12:34:16 Larry Martell wrote:
> >
> > man -t /path/to/man/file >file.txt
> > groff -mandoc /path/to/man/file > file.txt, both quadrupled the size
> > with lots more markup.
> >
> > Not what I want obviously.
>
> There is nothing obvious here.  What do you want?  Why?  What are you
> going to do with the resulting file(s)?

What I wanted on dead tree, was exactly what I see on screen.
With the manpage markup gobbled up, leaving only the text I see on screen 
when I type man 9 filename.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#240760

On Fri, Oct 01, 2021 at 05:21:54PM -0400, Gene Heskett wrote:
> What I wanted on dead tree, was exactly what I see on screen.
> With the manpage markup gobbled up, leaving only the text I see on screen 
> when I type man 9 filename.

So you wanted to print a man page on paper, but you wanted it *NOT* to
look exactly like it does on the screen.  You wanted the text only,
without the boldface and other markup.  Which is, again, *NOT* what you
see normally.  (What you see normally includes boldface and other markup.)

man ls | lp

should have done this for you.  There's no need for an intermediate file.
When the output of man isn't a terminal (e.g. when it's a pipe to lp),
man produces only the ASCII text, without any markup.

At least, that's how the man command works on Debian.  This is not the
case on proprietary Unixes.  There, the man command often includes the
markup when writing to non-terminals.  And if you look at the byte stream,
you see things like

_^Hu_^Hn_^Hd_^He_^Hr_^Hl_^Hi_^Hn_^He

because that's how you get underlining on a line or dot matrix printer.

[toc] | [prev] | [next] | [standalone]

#240768

On 10/1/21 1:59 PM, Gene Heskett wrote:
> On Friday 01 October 2021 12:34:16 Larry Martell wrote:
> 
> man -t /path/to/man/file >file.txt
> groff -mandoc /path/to/man/file > file.txt, both quadrupled the size with
> lots more markup.
> 
> Not what I want obviously.
> 
> Thanks Larry.
> 
> Cheers, Gene Heskett.
> 
man command | col -b > command.txt

Best regards,
Fred

[toc] | [prev] | [next] | [standalone]

#240769

On Fri, Oct 01, 2021 at 05:44:41PM -0700, Fred wrote:
> man command | col -b > command.txt

Curious.

unicorn:~$ man ls > ls1
unicorn:~$ man ls | col -b > ls2
unicorn:~$ ls -l ls1 ls2
-rw-r--r-- 1 greg greg 8299 Oct  1 20:49 ls1
-rw-r--r-- 1 greg greg 7745 Oct  1 20:49 ls2

Glancing at the diff -u between the two files, most of the changes
appear to be whitespace related.

Opening them both in vim, the second one has a bunch of literal tab
characters, whereas the first one has no tabs at all -- only spaces.

So I guess most (or all?) of the size reduction is groups of spaces
being replaced by tabs.

[toc] | [prev] | [next] | [standalone]

#240770

On Fri 01 Oct 2021 at 20:53:26 (-0400), Greg Wooledge wrote:
> On Fri, Oct 01, 2021 at 05:44:41PM -0700, Fred wrote:
> > man command | col -b > command.txt
> 
> Curious.
> 
> unicorn:~$ man ls > ls1
> unicorn:~$ man ls | col -b > ls2
> unicorn:~$ ls -l ls1 ls2
> -rw-r--r-- 1 greg greg 8299 Oct  1 20:49 ls1
> -rw-r--r-- 1 greg greg 7745 Oct  1 20:49 ls2
> 
> Glancing at the diff -u between the two files, most of the changes
> appear to be whitespace related.
> 
> Opening them both in vim, the second one has a bunch of literal tab
> characters, whereas the first one has no tabs at all -- only spaces.
> 
> So I guess most (or all?) of the size reduction is groups of spaces
> being replaced by tabs.

Yes, diff -ubw will confirm that whitespace is the only difference.
I'm too lazy to check that the /apparently/ significant differences
shown by diff and diff -u are merely caused by the left-margin offset,
which makes TABs skip to different columns from those intended.

Like others, I tried to guess what Gene really wanted (I can barely
believe the answer) and to come up with a suitable method. I also
tried out others' suggestions. We don't know what the mysterious
man 9 actually is (unless there's a well-known command named "9"),
so I used   man man   and   man bash¹.

$ man man > /tmp/man.txt
$ man --ascii man > /tmp/man.txt

If you use this, and then intend to print it, have a care what the
width of your window is set to. Too narrow and you get hyphena‐
tion hell; too wide and you have to shrink it down to fit the paper.

$ man -t man > /tmp/man.txt (wrong)
$ man -t man > /tmp/man.ps

Good for people who still have a PostScript workflow.
Myself, I prefer:

$ man -t man > /tmp/scratch.ps && ps2pdf /tmp/scratch.ps /tmp/man.pdf

And if you have a big screen, you can postprocess it with, say,

$ pdfjam --vanilla --nup '2x1' --noautoscale true --scale 1 --landscape --papersize '{11in,17in}' --outfile /tmp/man-2up.pdf /tmp/man.pdf

and have double spreads. US paper sizes. ☹

File sizes:

Not usually much of an issue nowadays. But let's see:

  66546  /tmp/man.pdf
  72147  /tmp/man.ps
  35932  /tmp/man.txt

and   col -b   can reduce the size of man.txt a little.
But moving on to bash:

 377528  /tmp/bash.pdf
 616850  /tmp/bash.ps
 345111  /tmp/bash.txt

Not such a big difference now between the text and PDF.
And I can easily close that gap by revealing what I haven't
earlier: /tmp/bash.txt was generated on a 121-wide xterm.
So, running  COLUMNS=NNN man --ascii bash > /tmp/bashNNN.txt
to simulate different widths, we get:

 377528  /tmp/bash.pdf

 381919  /tmp/bash072.txt
 371213  /tmp/bash080.txt
 355442  /tmp/bash100.txt
 345111  /tmp/bash121.txt

And I would finally add that reading through any of /tmp/bash*.txt is
/very/ heavy going, and difficult to absorb, because of the frequency
of special terms, which usually would be coloured or marked up.

¹ Decades ago, I used to print out big man pages, such as bash, fvwm
  and ffmpeg, so that I could read through them in an armchair (no
  laptop then). I still generate PDFs for those and others, as I find
  the result easiest on the eye. I also find them easiest to navigate
  (flicking back and forth) because the formatted pages have the most
  distinguishable individual appearance.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#240788

On Friday 01 October 2021 22:52:59 David Wright wrote:

> On Fri 01 Oct 2021 at 20:53:26 (-0400), Greg Wooledge wrote:
> > On Fri, Oct 01, 2021 at 05:44:41PM -0700, Fred wrote:
> > > man command | col -b > command.txt
> >
> > Curious.
> >
> > unicorn:~$ man ls > ls1
> > unicorn:~$ man ls | col -b > ls2
> > unicorn:~$ ls -l ls1 ls2
> > -rw-r--r-- 1 greg greg 8299 Oct  1 20:49 ls1
> > -rw-r--r-- 1 greg greg 7745 Oct  1 20:49 ls2
> >
> > Glancing at the diff -u between the two files, most of the changes
> > appear to be whitespace related.
> >
> > Opening them both in vim, the second one has a bunch of literal tab
> > characters, whereas the first one has no tabs at all -- only spaces.
> >
> > So I guess most (or all?) of the size reduction is groups of spaces
> > being replaced by tabs.
>
> Yes, diff -ubw will confirm that whitespace is the only difference.
> I'm too lazy to check that the /apparently/ significant differences
> shown by diff and diff -u are merely caused by the left-margin offset,
> which makes TABs skip to different columns from those intended.
>
> Like others, I tried to guess what Gene really wanted (I can barely
> believe the answer) and to come up with a suitable method. I also
> tried out others' suggestions. We don't know what the mysterious
> man 9 actually is (unless there's a well-known command named "9"),
> so I used   man man   and   man bash¹.

There is a well known man 9 command, it means to save man the trouble of 
searching the whole database, as there might be duplicate names to 
confuse the issue, but it this case look in man/man9 for the requested 
manpage. Sheesh, doesn't anyone read manpages anymore? :o)
[...]


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#240796

On Sat, Oct 02, 2021 at 07:23:45AM -0400, Gene Heskett wrote:
> On Friday 01 October 2021 22:52:59 David Wright wrote:
> > Like others, I tried to guess what Gene really wanted (I can barely
> > believe the answer) and to come up with a suitable method. I also
> > tried out others' suggestions. We don't know what the mysterious
> > man 9 actually is (unless there's a well-known command named "9"),
> > so I used   man man   and   man bash¹.
> 
> There is a well known man 9 command, it means to save man the trouble of 
> searching the whole database, as there might be duplicate names to 
> confuse the issue, but it this case look in man/man9 for the requested 
> manpage. Sheesh, doesn't anyone read manpages anymore? :o)
> [...]

In Debian's man command, if there are two arguments given, the first
argument is the section name, and the second argument is the page name.

E.g. if you run "man 8 intro", you will read the intro(8) page, which
is the introduction to section 8 of the manual.

Debian mostly ships pages in sections 1 through 8, but some packages or
applications may create other sections.  E.g. the manpages-posix package
in Debian creates a section called "1posix".  Perl puts some man pages
in section "3perl", Tcl puts its man pages in section "n", and so on.

Apparently Gene's application has some documentation in section "9".  This
is also not unheard of.  According to Google, at some point in the past,
the Linux kernel shipped some kernel-internal stuff in section 9, and
Solaris also has kernel stuff in sections 9e, 9f and 9s.

[toc] | [prev] | [next] | [standalone]

#240787

On Friday 01 October 2021 20:53:26 Greg Wooledge wrote:

> On Fri, Oct 01, 2021 at 05:44:41PM -0700, Fred wrote:
> > man command | col -b > command.txt
>
> Curious.
>
> unicorn:~$ man ls > ls1
> unicorn:~$ man ls | col -b > ls2
> unicorn:~$ ls -l ls1 ls2
> -rw-r--r-- 1 greg greg 8299 Oct  1 20:49 ls1
> -rw-r--r-- 1 greg greg 7745 Oct  1 20:49 ls2
>
> Glancing at the diff -u between the two files, most of the changes
> appear to be whitespace related.
>
> Opening them both in vim, the second one has a bunch of literal tab
> characters, whereas the first one has no tabs at all -- only spaces.
>
> So I guess most (or all?) of the size reduction is groups of spaces
> being replaced by tabs.
The manpage is jogaxisget.9. and they look very close to identical, but 
an ls -l shows:
-rw-r--r--  1 pi   pi        1321 Oct  2 05:38 jogaxisget.text
-rw-r--r--  1 pi   pi        1580 Oct  1 17:00 jogaxisget.txt
either one will do. even for copy/paste as hal treats tabs the same as 
spaces and reads of past looking for the text.

Thank you everybody, problem solved. Now to figure out what to hook it up 
to in a 700+ l.o.c. file containing at least 5000 signal names.

TL;DR unless interested in cnc machinery

The hookup syntax is :

net netname <input-signal >output-1 [output-2] etc etc

and there is not an example line to show how its hooked up to achieve the 
desired logic outputs in the manpage. Only the invocation lines are 
given.
This is what I wanted:

JOGAXISGET(9)								     HAL Component								  JOGAXISGET(9)

NAME
       jogaxisget - determines which axis jogging

SYNOPSIS
       loadrt jogaxisget [count=N|names=name1[,name2...]]

FUNCTIONS
       jogaxisget.N (requires a floating-point thread)

PINS
       jogaxisget.N.Xin0 bit in
	      axis.x.kb-jog-active <-- (edited in) example signal name

       jogaxisget.N.Xin1 bit in
       jogaxisget.N.Yin0 bit in
	      axis.y.kb-jog-active

       jogaxisget.N.Yin1 bit in
       jogaxisget.N.Zin0 bit in
	      axis.z.kb-jog-active

       jogaxisget.N.Zin1 bit in
       jogaxisget.N.Ain0 bit in
	      axis.a.kb-jog-active

       jogaxisget.N.Ain1 bit in
       jogaxisget.N.Xtrigger bit out
       jogaxisget.N.Ytrigger bit out
       jogaxisget.N.Ztrigger bit out
       jogaxisget.N.Atrigger bit out
       jogaxisget.N.activeX bit out
       jogaxisget.N.activeY bit out
       jogaxisget.N.activeZ bit out
       jogaxisget.N.activeA bit out
       jogaxisget.N.Xverify bit in (default: FALSE)
	      axisui.Xisactive

       jogaxisget.N.Yverify bit in (default: FALSE)
	      axisui.Yisactive

       jogaxisget.N.Zverify bit in (default: FALSE)
	      axisui.Zisactive

       jogaxisget.N.Averify bit in (default: FALSE)
	      axisui.Aisactive

LICENSE
       GPL

LinuxCNC Documentation							       2021-09-30								  JOGAXISGET(9)

The idea is to keep a gui's radio buttons up to date with what the 
machine is doing, when signals external to the gui ae used to move the 
machine, in this case a pair of encoder dials that function like the 
hand cranks on a manual machine when it has been converted to cnc 
control. With a per click distance ranging from .0001 inches to 20 
thousanths per click. All this extra is unique to my machine, I wrote 
it.

The dials I have added are very handy when one is finding the positions 
to start a machining operation from, but at present, applying a 
touch-off to establish that point does not update the gui's radio 
buttons, so you find a point, and blindly apply the touch-off, only to 
discover the touch-off has been applied to the wrong axis because the 
radio buttons have not been updated by moving the machine with the 
dials.  This logic module is designed to act the same as a keyboard jog, 
which does update the gui's radio buttons. But its up to me to find the 
right signals to tie together to adhieve that, as they are mutually 
exclusive, only one can be TRUE at a time, the most recent. For a lathe, 
which only has 2 axis's only X and Z pins will be used, but for a mill 
at least 3 need to be "hooked" up. But both of my mills have 4 asises, 
and could have as many as 9. And since this module was written 
the "axis" and "joints" have been divorced for increased versatility, so 
the the subnames on the 2nd line are now duff and the new names will 
have to be found by experimentation. And I'm the first to use this 
module, so I get to write the translation rules.

Since N=69! is the largest that a ti calculator can handle, fun it won't 
be, cuz N is well north of 1000 in this case.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#240784

On Friday 01 October 2021 20:44:41 Fred wrote:

> On 10/1/21 1:59 PM, Gene Heskett wrote:
> > On Friday 01 October 2021 12:34:16 Larry Martell wrote:
> >
> > man -t /path/to/man/file >file.txt
> > groff -mandoc /path/to/man/file > file.txt, both quadrupled the size
> > with lots more markup.
> >
> > Not what I want obviously.
> >
> > Thanks Larry.
> >
> > Cheers, Gene Heskett.
>
> man command | col -b > command.txt
>
> Best regards,
> Fred
works fine, thanks.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#240739

On 10/1/21, Gene Heskett <gheskett@shentel.net> wrote:
> Greetings all;
>
> With the man markup subtracted, so what we save is exactly what we see.
>
> Thanks.
>
> Cheers, Gene Heskett.


Hi, Gene. I'm not sure if I'm understanding correctly, but.. I do this
(am using the LILO package as an example):

man lilo > manLILO

I just tested it to make sure first. Mine here looks exactly like the
terminal version when that manLILO file is viewed in Mousepad (XFE4's
text editor). That still prints all the useful "SEE ALSO", last date
edited, and e.g. "LILO(8) leads that appear at the bottom, too.

Others here sometimes do something a little fancier than only that ">"
(greater than sign), but I can't remember what it is nor if it applies
to something as straight forward as this one.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

[toc] | [prev] | [next] | [standalone]

#240754

On Friday 01 October 2021 12:43:00 Cindy Sue Causey wrote:

> On 10/1/21, Gene Heskett <gheskett@shentel.net> wrote:
> > Greetings all;
> >
> > With the man markup subtracted, so what we save is exactly what we
> > see.
> >
> > Thanks.
> >
> > Cheers, Gene Heskett.
>
> Hi, Gene. I'm not sure if I'm understanding correctly, but.. I do this
> (am using the LILO package as an example):
>
> man lilo > manLILO
>
> I just tested it to make sure first. Mine here looks exactly like the
> terminal version when that manLILO file is viewed in Mousepad (XFE4's
> text editor). That still prints all the useful "SEE ALSO", last date
> edited, and e.g. "LILO(8) leads that appear at the bottom, too.
>
> Others here sometimes do something a little fancier than only that ">"
> (greater than sign), but I can't remember what it is nor if it applies
> to something as straight forward as this one.
>
> Cindy :)

did exactly what I wanted it to do.  Thank you Cindy. ;o)

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#240744

On 10/1/21, Gene Heskett <gheskett@shentel.net> wrote:
> Greetings all;
>
> With the man markup subtracted, so what we save is exactly what we see.

Try the "--ascii" option - eg
  man --ascii  man > /tmp/man.txt

Regards,
Lee

[toc] | [prev] | [next] | [standalone]

#240745 — Re: What do we have that will save a manpage as we see it on-screen

There's tee that can be used just pipe the man page through it and into a
text file.


On Fri, 1 Oct 2021, Lee wrote:

> On 10/1/21, Gene Heskett <gheskett@shentel.net> wrote:
> > Greetings all;
> >
> > With the man markup subtracted, so what we save is exactly what we see.
>
> Try the "--ascii" option - eg
>   man --ascii  man > /tmp/man.txt
>
> Regards,
> Lee
>
>

[toc] | [prev] | [next] | [standalone]

#240756

On Friday 01 October 2021 13:58:20 Lee wrote:

> On 10/1/21, Gene Heskett <gheskett@shentel.net> wrote:
> > Greetings all;
> >
> > With the man markup subtracted, so what we save is exactly what we
> > see.
>
> Try the "--ascii" option - eg
>   man --ascii  man > /tmp/man.txt
>
> Regards,
> Lee

Cindy's suggestion worked.  Thanks Lee.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#240758

On Fri, Oct 01, 2021 at 05:05:44PM -0400, Gene Heskett wrote:
> On Friday 01 October 2021 12:43:00 Cindy Sue Causey wrote:
> > man lilo > manLILO

> did exactly what I wanted it to do.  Thank you Cindy. ;o)


On Fri, Oct 01, 2021 at 05:07:37PM -0400, Gene Heskett wrote:
> On Friday 01 October 2021 13:58:20 Lee wrote:
> >   man --ascii  man > /tmp/man.txt

> Cindy's suggestion worked.  Thanks Lee.


*sigh*

Do you know how frustrating this is?

"Hey guys, I want a thing.  I won't give any useful details, though.
Just make this thing for me.  I want you all to guess what I want, and
I'll look through the answers, and pick the one I like the most.  You're
all going to be my personal army of monkeys typing on the keyboards.
One of you will produce Shakespeare for me."


Even now, after you've declared a winner, we can still only *guess* what
the contest rules were.

And the decision is nonsensical, because you've declared one winner (Cindy)
when the second-place runner up (Lee) gave a command that gives *exactly*
the same result as Cindy's command.

unicorn:~$ man ls > manls
unicorn:~$ man --ascii ls > manls2
unicorn:~$ ls -l manls manls2
-rw-r--r-- 1 greg greg 8299 Oct  1 17:09 manls
-rw-r--r-- 1 greg greg 8299 Oct  1 17:10 manls2
unicorn:~$ cmp manls manls2
unicorn:~$ 


We still don't know why you want this.  I guess we'll never know.

[toc] | [prev] | [next] | [standalone]

#240761

On Friday 01 October 2021 17:17:53 Greg Wooledge wrote:

> On Fri, Oct 01, 2021 at 05:05:44PM -0400, Gene Heskett wrote:
> > On Friday 01 October 2021 12:43:00 Cindy Sue Causey wrote:
> > > man lilo > manLILO
> >
> > did exactly what I wanted it to do.  Thank you Cindy. ;o)
>
> On Fri, Oct 01, 2021 at 05:07:37PM -0400, Gene Heskett wrote:
> > On Friday 01 October 2021 13:58:20 Lee wrote:
> > >   man --ascii  man > /tmp/man.txt
> >
> > Cindy's suggestion worked.  Thanks Lee.
>
> *sigh*
>
> Do you know how frustrating this is?
>
> "Hey guys, I want a thing.  I won't give any useful details, though.
> Just make this thing for me.  I want you all to guess what I want, and
> I'll look through the answers, and pick the one I like the most. 
> You're all going to be my personal army of monkeys typing on the
> keyboards. One of you will produce Shakespeare for me."
>
>
> Even now, after you've declared a winner, we can still only *guess*
> what the contest rules were.
>
> And the decision is nonsensical, because you've declared one winner
> (Cindy) when the second-place runner up (Lee) gave a command that
> gives *exactly* the same result as Cindy's command.
>
> unicorn:~$ man ls > manls
> unicorn:~$ man --ascii ls > manls2
> unicorn:~$ ls -l manls manls2
> -rw-r--r-- 1 greg greg 8299 Oct  1 17:09 manls
> -rw-r--r-- 1 greg greg 8299 Oct  1 17:10 manls2
> unicorn:~$ cmp manls manls2
> unicorn:~$
>
>
> We still don't know why you want this.  I guess we'll never know.

We apparently don't speak the same dialect of english Greg. I wanted a 
dead tree (aka paper) copy of a manpage, with ALL the markup totally 
stripped. As for Lee's suggestion, I didn't try it since Cindy's example 
worked perfectly and by the time I read Lee's msg, I had what I needed 
on the output tray of my huge printer. No reflection on Lee was 
intended. Still isn't.

Thanks Greg.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web