Is it just me? Don't you find the syntax descriptions of Linux commands
hard to understand because they're not written with so-called "railroad
diagrams"? I don't know who invented the railroad scheme, but I
certainly credit IBM (and others) for adopting the layout. If I'm force
into early reti
Amen. I completely agree.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Scully, William P
Sent: January 31, 2007 11:01
To: LINUX-390@VM.MARIST.EDU
Subject: OT: Linux and Railroad Diagrams
Is it just me? Don't you find the syntax descriptions of
/me agrees. Take a look at the arguments for the GCC compiler .
Kevin
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Scully, William P
Sent: Wednesday, January 31, 2007 11:01 AM
To: LINUX-390@VM.MARIST.EDU
Subject: OT: Linux and Railroad Diagrams
Is
I agree!! Could you start tomorrow?
Lea Stahr
Linux/Unix Team
630-753-5445
[EMAIL PROTECTED]
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Scully, William P
Sent: Wednesday, January 31, 2007 10:01 AM
To: LINUX-390@VM.MARIST.EDU
Subject: OT: Linux and
Must be due to lack of training.
Jon
Is it just me? Don't you find the syntax descriptions of Linux commands
hard to understand because they're not written with so-called "railroad
diagrams"?
--
For LINUX-390 subscribe /
On Jan 31, 2007, at 10:04 AM, Peter Webb, Toronto Transit Commission
wrote:
Amen. I completely agree.
$ man foobar
The documentation for the command foobar has been moved into the GNU
info system. Please consult it instead.
$ info foobar
RTFM
$
Adam
---
/me feels like giving Adam some obscure mainframe problem to solve, in
that case.
LOL
K
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Adam Thornton
Sent: Wednesday, January 31, 2007 11:10 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux and Railroad
and "info", of "MY" system?
Tom Duerbusch
THD Consulting
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Adam Thornton
Sent: Wednesday, January 31, 2007 11:10 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux and Railroad Diagrams
I'm not sure I know what is a "railroad diagram" and don't have the
Pascal book handy (hey, I don't learn every new language which comes
along. :-)
Are there links to URLs which show/explain these things?
--
--henry schaffer
Henry,
If you have access to VM/CMS, you can see railroad track (RRT) diagrams
by typing e.g.
help cp ipl
which will display information about the CP IPL command.
Some reference information can be found at
http://publib.boulder.ibm.com/infocenter/printer/v1r1/index.jsp?topic=/com.ibm.printers.
> I'm not sure I know what is a "railroad diagram" and don't have the
> Pascal book handy (hey, I don't learn every new language which comes
> along. :-)
> Are there links to URLs which show/explain these things?
Have a look at http://publibz.boulder.ibm.com/epubs/pdf/hcsd8b10.pdf,
and look at
m: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Adam Thornton
Sent: Wednesday, January 31, 2007 11:10 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux and Railroad Diagrams
On Jan 31, 2007, at 10:04 AM, Peter Webb, Toronto Transit Commission
wrote:
> Amen. I completely agree.
$ man foo
On Wednesday, 01/31/2007 at 03:02 EST, David Boyes <[EMAIL PROTECTED]>
wrote:
> I remember the uproar when IBM first introduced them (I think late in
> SP5 or early VM/ESA; don't remember precise dates). I can use them, but
> they aren't as effective for me as a good description. Maybe my brain's
>
> The layout of railroad tracks is not a substitution for reading the
> manual, it's an aid in understanding. Good doc is crystal clear and
> unambiguous.
Exactly.
> More off-topic: It would be interesting to hear from IBM on how
> screen-readers (for the blind) cope with railroad tracks.
Ba
> Though as soon as z gets a 3d visor (3DV) and 'hand motion
interpreter'
> (HMI) we might be able to do FILEDEF by using some of the recent
> breakthroughs in multidimensional visualization. (Hey - if the
> motherboards can have a dozen layers, why not syntax diagrams?)
I can see it now: the VM
Jon Brock wrote:
> Must be due to lack of training.
Woot!
or should that be: Whoo! Whoo!
:)
>
> Jon
>
>
>
> Is it just me? Don't you find the syntax descriptions of Linux commands
> hard to understand because they're not written with so-called "railroad
> diagrams"?
>
>
> -
On Jan 31, 2007, at 3:19 PM, David Boyes wrote:
Though as soon as z gets a 3d visor (3DV) and 'hand motion
interpreter'
(HMI) we might be able to do FILEDEF by using some of the recent
breakthroughs in multidimensional visualization. (Hey - if the
motherboards can have a dozen layers, why not
Linux on 390 Port wrote on 01/31/2007 02:47:55
PM:
> Though as soon as z gets a 3d visor (3DV) and 'hand motion interpreter'
> (HMI) we might be able to do FILEDEF by using some of the recent
> breakthroughs in multidimensional visualization. (Hey - if the
> motherboards can have a dozen layers,
It won't be long. They're already available for the desktop. See
http://www.sharpsystems.com/products/lcd_monitors/15-17_inch/ll-151-3d/
J. Leslie Turriff
VM Systems Programmer
University of Central Missouri
Room 400
Ward Edwards Building
Warrensburg MO 64093
660-543-4285
660-580-0523
[EMAIL
Your Name wrote:
Note that the examples provided by IBM's online books use only -+|<>
characters, making the diagrams somewhat harder to read than if extended
box characters were used. The original diagrams in the Pascal book used
quarter- and semi-circular joins, making the diagrams more
"railr
Altmark
Sent: Wednesday, January 31, 2007 3:48 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux and Railroad Diagrams
-snip-
Though as soon as z gets a 3d visor (3DV) and 'hand motion interpreter'
(HMI) we might be able to do FILEDEF by using some of the recent
breakthroughs in multid
On Feb 3, 2007, at 4:59 PM, Mark Post wrote:
I would be concerned that if the machine were able to interpret
hand motions
from the systems programmers, it would find out just how, ummm,
vehement
their feelings are for the hardware.
As Err would say, "I hope you are seeing this, because I am do
The first place I ever saw railroad track diagrams was in the appendix
of Niklaus Wirth's book about Pascal.
As far as I can tell there is no consolidated "Linux Command Reference"
anywhere. You can find bits and pieces here and there, but there are
no
Messages and Codes
User Guide
Command Refer
> As far as I can tell there is no consolidated "Linux Command
Reference"
> anywhere.
/bin/csh
cd /usr/man (note, *not* /usr/man/catman!)
foreach i (`ls -R *`) ( note backticks -- I'm sure there's a better way,
but
what did you pay for this one? )
cat $i | troff
On Jan 31, 2007, at 1:19 PM, David Boyes wrote:
/bin/csh
cd /usr/man (note, *not* /usr/man/catman!)
foreach i (`ls -R *`) ( note backticks -- I'm sure there's a better
way,
but
what did you pay for this one? )
cat $i | troff -man | lpr -Pyourpsprinter
echo $i
e
: Wednesday, January 31, 2007 1:19 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: OT: Linux and Railroad Diagrams
> As far as I can tell there is no consolidated "Linux Command
Reference"
> anywhere.
/bin/csh
cd /usr/man (note, *not* /usr/man/catman!)
foreach i (`ls -R *`)
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
> Behalf Of Adam Thornton
> Sent: Wednesday, January 31, 2007 1:36 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: OT: Linux and Railroad Diagrams
>
>
> On Jan 31, 2007, at
I started to try this with a single command documentation, without
looping:
(This is SUSE 9 SP3 64 bit)
cd /usr/share/man
[EMAIL PROTECTED]:/usr/share/man/man1> cat znew.1.gz | troff -man | lpr
-Plpl031
:1: warning: can't find character with input code 2
:1: warning: can't find character with inp
Sent: Wednesday, January 31, 2007 2:25 PM
> To: McKown, John; LINUX-390@VM.MARIST.EDU
> Subject: Re: OT: Linux and Railroad Diagrams
>
>
> I started to try this with a single command documentation, without
> looping:
> (This is SUSE 9 SP3 64 bit)
>
> cd /usr/share/
On Jan 31, 2007, at 2:24 PM, Tom Duerbusch wrote:
I started to try this with a single command documentation, without
looping:
(This is SUSE 9 SP3 64 bit)
cd /usr/share/man
[EMAIL PROTECTED]:/usr/share/man/man1> cat znew.1.gz | troff -man | lpr
-Plpl031
Use zcat instead of cat: you're reading
> [EMAIL PROTECTED]:/usr/share/man/man1> cat znew.1.gz | troff -man | lpr
> -Plpl031
Note the .gz extension. Your system has compressed man page source.
Either replace cat with zcat or pipe it through gunzip as part of the
pipe.
> Is this saying I need a postscript printer? The printer is fine
When I'm in /usr/share/man, all the subdirectories listed only have
files that are compressed (.gz suffix). As the origional source code
discussed used the 'cat' command, it makes me wonder what is different.
Did everyone else expand their files? Or am I in the wrong directory?
Also, I now have
You might enjoy knowing about man -t. Instead of
cat $i | troff -man | lpr -Pprinter
you should be able to do
man -t $i | lpr -Pprinter
man man for the details.
Richard
David Boyes wrote:
As far as I can tell there is no consolidated "Linux Command
Reference"
anywhere.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Scully, William P wrote:
|
| Is it just me? Don't you find the syntax descriptions of Linux commands
| hard to understand because they're not written with so-called "railroad
| diagrams"? I don't know who invented the railroad scheme, but I
|
I think that I have adapted to the Unix-style documentation.
I wrote that sentence and then started thinking of the number of times
that I looked at the command syntax in a man page and have been totally
mystified. Man pages are for people who already know how it works, but
just need to refresh t
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Tom Shilson wrote:
| I think that I have adapted to the Unix-style documentation.
|
| I wrote that sentence and then started thinking of the number of times
| that I looked at the command syntax in a man page and have been totally
| mystified. M
> When I'm in /usr/share/man, all the subdirectories listed only have
> files that are compressed (.gz suffix). As the origional source code
> discussed used the 'cat' command, it makes me wonder what is
different.
> Did everyone else expand their files? Or am I in the wrong directory?
I always
January 31, 2007 4:42 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: OT: Linux and Railroad Diagrams
>
> You might enjoy knowing about man -t. Instead of
>
> cat $i | troff -man | lpr -Pprinter
>
> you should be able to do
>
> man -t $i | lpr
McKown, John wrote:
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Adam Thornton
Sent: Wednesday, January 31, 2007 1:36 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: OT: Linux and Railroad Diagrams
On Jan 31, 2007, at 1:19 PM, David Boyes wrote:
/bin
Tom Duerbusch wrote:
I started to try this with a single command documentation, without
looping:
(This is SUSE 9 SP3 64 bit)
cd /usr/share/man
[EMAIL PROTECTED]:/usr/share/man/man1> cat znew.1.gz | troff -man | lpr
-Plpl031
gunzip -c ... would be better than cat ...
:1: warning: can't find
40 matches
Mail list logo
