all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Takesi Ayanokoji <ayanokoji.takesi@gmail.com>
Cc: 31550-done@debbugs.gnu.org
Subject: bug#31550: Inconsistent markup usage in custom.texi(emacs-26)
Date: Tue, 22 May 2018 20:08:26 +0300	[thread overview]
Message-ID: <838t8behyt.fsf@gnu.org> (raw)
In-Reply-To: <CAN7WbiaX_1_r3h5tbAh_NK+9EGXRN5NQmrvivBSN_F8h8oDT4g@mail.gmail.com> (message from Takesi Ayanokoji on Tue, 22 May 2018 21:08:40 +0900)

> 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.





      reply	other threads:[~2018-05-22 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22 12:08 bug#31550: Inconsistent markup usage in custom.texi(emacs-26) Takesi Ayanokoji
2018-05-22 17:08 ` Eli Zaretskii [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838t8behyt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31550-done@debbugs.gnu.org \
    --cc=ayanokoji.takesi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.