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

Previous Next

Package: emacs;

Reported by: Takesi Ayanokoji <ayanokoji.takesi <at> gmail.com>

Date: Tue, 22 May 2018 12:10:02 UTC

Severity: normal

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 31550 in the body.
You can then email your comments to 31550 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#31550; Package emacs. (Tue, 22 May 2018 12:10:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Takesi Ayanokoji <ayanokoji.takesi <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Tue, 22 May 2018 12:10:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Takesi Ayanokoji <ayanokoji.takesi <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Inconsistent markup usage in custom.texi(emacs-26)
Date: Tue, 22 May 2018 21:08:40 +0900
[Message part 1 (text/plain, inline)]
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 <at> gmail.com>
[Message part 2 (text/html, inline)]

Reply sent to Eli Zaretskii <eliz <at> gnu.org>:
You have taken responsibility. (Tue, 22 May 2018 17:09:01 GMT) Full text and rfc822 format available.

Notification sent to Takesi Ayanokoji <ayanokoji.takesi <at> gmail.com>:
bug acknowledged by developer. (Tue, 22 May 2018 17:09:02 GMT) Full text and rfc822 format available.

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.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Wed, 20 Jun 2018 11:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 7 years and 59 days ago.

Previous Next


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