GNU bug report logs - #31550
Inconsistent markup usage in custom.texi(emacs-26)

Previous Next

Full log

Message #10 received at 31550-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Takesi Ayanokoji <ayanokoji.takesi <at> gmail.com>
Cc: 31550-done <at> debbugs.gnu.org
Subject: Re: bug#31550: Inconsistent markup usage in custom.texi(emacs-26)
Date: Tue, 22 May 2018 20:08:26 +0300

> From: Takesi Ayanokoji <ayanokoji.takesi <at> gmail.com>
> Date: Tue, 22 May 2018 21:08:40 +0900
> 
> In custom.texi:147..150,
> 
> >>> start here
> If you are interested in customizing a particular setting or customization group, you can go straight there with
> the commands @kbd{M-x customize-option}, @kbd{M-x customize-face}, or @w{@kbd{M-x
> customize-group}}.  @xref{Specific Customization}."
> <<< end here
> 
>  only '@kbd{M-x customize-group}' are marked-up by @w{...} (Prevent Line Breaks).
> 
> About this paragraph, only adding @w markup was changed in Emacs manual from emacs-25.2 to
> emacs-26.
> 
> Is there any reason?

The reason is to avoid breaking a long command between two lines.
Commands that are not in danger of being split between lines don't
need the @w{..} guard.  Having @w{} everywhere cannot do any harm, but
it makes reading the Texinfo source harder.

This is not a bug.

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.