bug#31550: Inconsistent markup usage in custom.texi(emacs-26)

bug#31550: Inconsistent markup usage in custom.texi(emacs-26)

[Takesi Ayanokoji]

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

Hi emacs developers.

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?

It seems necessary for specific columns count environment for me.

Or original language environment, @kbd{M-x customize-group} will be put
line-break position, always?
(If so when it translated to other languages, translators should decide @w
markup target separately?)

Thanks.

ayatakesi <ayanokoji.takesi@gmail.com>

[-- Attachment #2: Type: text/html, Size: 1838 bytes --]

bug#31550: Inconsistent markup usage in custom.texi(emacs-26)

[Eli Zaretskii]

> From: Takesi Ayanokoji <ayanokoji.takesi@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.