bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Specify completion without name


From: Linda Walsh
Subject: Re: Specify completion without name
Date: Wed, 11 Jan 2012 12:03:32 -0800
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.24) Gecko/20100228 Lightning/0.9 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666



Clark J. Wang wrote:
On Fri, Jan 6, 2012 at 00:33, Peng Yu <address@hidden> wrote:

But beware to clearly document these by giving working
EXAMPLE code which include these three commands (not just text
explanation without working code, by "working code" I mean code
snippet is discouraged, a complete completion function should be
provided).


The bash man page already has ~70 pages manual. I don't like it to grow to
~700 pages (like the ABS Guide) with all the working examples you expected.
:)
----
 Vs. having things undocumented, as is the case in the current bash man page.

 I think the bash doc maintainers would benefit greatly by looking at the
perl manpages, which generally do a good job of documenting a complex
product.

 Like... compat40 mentions it changes behavior, about interrupting a command
list, yet try to find out what that behavior is, or what compat40 would
change it 'to'?

Or how about, does compat 31 imply compat32 and compat40?  If not, does that
really mean compat31 is really 'compat31', or just "use <feature> 3.1" to
specify that a specific feature be used in it's 3.1 version vs. a newer version.

I agree insomuch as if every new incompatibility had to be thoroughly 
documented,
the impact of such incompatibilities might be more thoroughly thought out,
not to mention the benefit for users trying to read the man page to program
by...







reply via email to

[Prev in Thread] Current Thread [Next in Thread]