emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#16802: closed (@w for long option names)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#16802: closed (@w for long option names)
Date: Fri, 21 Feb 2014 02:27:02 +0000

Your message dated Thu, 20 Feb 2014 18:26:05 -0800
with message-id <address@hidden>
and subject line Re: bug#16802: @w for long option names
has caused the debbugs.gnu.org bug report #16802,
regarding @w for long option names
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
16802: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16802
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: @w for long option names Date: Tue, 18 Feb 2014 23:57:29 GMT
In a couple places, coreutils.texi uses @w around (bare) long option
names.  These are the ones I noticed:

621:@item @address@hidden
1268:The @address@hidden (@option{-t}) option allows the @command{cp},
1312:operating on it.  The @address@hidden option enables

I'm guess the point is to avoid line breaks at the internal hyphens
(there would/should never be line breaks at leading hyphens).  In which
case, a cleaner/more general approach would be

@allowcodebreaks false

Then there is no need for sprinkling @w throughout the source.
We added that in Texinfo 4.11, released 2007.

(It belatedly occurs to me that we should make @option, specifically,
always disallow line breaks at hyphens.)

karl



--- End Message ---
--- Begin Message --- Subject: Re: bug#16802: @w for long option names Date: Thu, 20 Feb 2014 18:26:05 -0800 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
OK, thanks, I installed it on savannah and am marking this as done.


--- End Message ---

reply via email to

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