From: Eli Zaretskii <eliz@gnu.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs-diffs Digest, Vol 130, Issue 82
Date: Fri, 27 Sep 2013 09:10:53 +0300 [thread overview]
Message-ID: <83fvsqg5g2.fsf@gnu.org> (raw)
In-Reply-To: <CAAF+z6Gx+Mc-fwgdtqHM1PXo1XqypQNndWk41WcDyLvfbbRynQ@mail.gmail.com>
> Date: Fri, 27 Sep 2013 06:49:45 +0800
> From: Xue Fuqiao <xfq.free@gmail.com>
> Cc: emacs-devel <emacs-devel@gnu.org>
>
> On Fri, Sep 27, 2013 at 12:06 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > 2013-09-26 Xue Fuqiao <xfq.free@gmail.com>
> >
> > + * dired.texi (Flagging Many Files): Use @emph instead of @strong.
> >
> > Why? What's wrong with @strong in this case?
>
> In (info "(texinfo) @emph @strong"):
>
> ---------------------------------------------------------------------
> *Caution*: 'rm * .[^.]*' removes _all_ normal files.
>
> The '@strong' command is seldom used except to mark what is, in
> effect, a typographical element, such as the word 'Caution' in the
> preceding example.
> ---------------------------------------------------------------------
>
> So I think @strong should be used to mark something like "Caution:",
> "Warning:", "Please notice:", "Please note:", "Reassurance:",
> "Important:", "Usage note:", etc.
This is a purely stylistic issue. The quoted passage from the Texinfo
manual just says that @strong is seldom used, it does not say "do not
use it except in the following situations". Please do not make any
changes that are stylistic in nature, because style preferences are
deeply personal, and we don't want to start arguments over personal
preferences.
next prev parent reply other threads:[~2013-09-27 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.24.1380211205.32681.emacs-diffs@gnu.org>
2013-09-26 16:06 ` Emacs-diffs Digest, Vol 130, Issue 82 Eli Zaretskii
2013-09-26 22:49 ` Xue Fuqiao
2013-09-27 6:10 ` Eli Zaretskii [this message]
2013-09-28 1:35 ` Xue Fuqiao
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fvsqg5g2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=xfq.free@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).