RE: [Structuredtext-develop] Some problems with option lists

[Tony J I. (Tibs) <to...@ls...>]

David Goodger wrote
> Besides, this is consistent with how bullet lists and enumerated lists
> are put together. We store the bullet character or enumeration details
> once, at the beginning of the list.

Hmm. I'm not entirely sure that we should be aiming to support every
weird and wonderful command line that someone can come up with, but I do
*actually* have a case (that I use) that mixes the slash and dash forms.

Specifically, I do a lot of work on Windows/NT, and tend thus to have
batch files that encapsulate common commands. These are done "properly",
with /help switches, and so on.

The specific example I am thinking of is a small batch file that runs
the javac, javah or javadoc tools for me. Its command line is of the
form:

	jmake /javac -verbose

where the /javac is telling it which tool to choose (and there are other
options, like /debug and so on), whilst the rest of the command line is
being passed down to the particular tool. Being Unix originated, despite
being on NT the Java tools expect dash-style switches (and, as you can
see, they don't follow the Gnu conventions).

Of course, strictly speaking the dash switches *are* just the "rest of
line", and I don't really expect to process them myself, so it perhaps
isn't strict doc-tools territory - except that it can be useful to
describe the more common switches for each tool.

Thinking-out-loud-again,
	Tibs

--
Tony J Ibbs (Tibs)      http://www.tibsnjoan.co.uk/
"How fleeting are all human passions compared with the massive
continuity of ducks." - Dorothy L. Sayers, "Gaudy Night"
My views! Mine! Mine! (Unless Laser-Scan ask nicely to borrow them.)