From: Eli Zaretskii <eliz@gnu.org>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: stefan@marxist.se, lennart.borgman@gmail.com, 6411@debbugs.gnu.org
Subject: bug#6411: Ispell string or comment, bug#6411: Ispell string or comment
Date: Thu, 09 Apr 2020 22:01:58 +0300 [thread overview]
Message-ID: <835ze8o53t.fsf@gnu.org> (raw)
In-Reply-To: <87o8s0ebx0.fsf@gmail.com> (message from Štěpán Němec on Thu, 09 Apr 2020 20:44:59 +0200)
> From: Štěpán Němec <stepnem@gmail.com>
> Cc: stefan@marxist.se, lennart.borgman@gmail.com, 6411@debbugs.gnu.org
> Date: Thu, 09 Apr 2020 20:44:59 +0200
>
> > Please quote symbols in log messages 'like this'. Please also mention
> > the bug number there.
>
> Will fix, thank you. (Funnily enough I did double check this when making
> the patch, and found recent commit messages quite diverse in that
> regard.)
Yes, not everybody follows the policy (and I'm ashamed to sometimes
forget doing that as well...)
> >> +can use @kbd{M-x ispell-comments-and-strings} or @kbd{M-x
> >> +ispell-comment-or-string-at-point} to check only comments or string
> >
> > When a long "M-x SOMETHING" command is close to a line's end, please
> > enclose it in @w{..}, so that it doesn't get split between two lines.
>
> By "close to a line's end" I assume you mean to check the rendered info
> file, as IIUC there is no strict correspondence between the texi source
> and the final document WRT end of line?
The correspondence is quite close, even though not 100%, and there's
the Info output, where it's even closer. So you could just use
@w{@kbd{..}} when it's close in Texinfo, because @w{..} is harmless if
it isn't needed.
next prev parent reply other threads:[~2020-04-09 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 17:57 bug#6411: Ispell string or comment Lennart Borgman
2010-06-22 15:00 ` Agustin Martin
2019-08-21 14:07 ` Stefan Kangas
2019-08-21 17:08 ` Eli Zaretskii
2019-08-21 20:57 ` Stefan Kangas
2020-04-08 19:23 ` bug#6411: Ispell string or comment, " Štěpán Němec
2020-04-09 6:21 ` Eli Zaretskii
2020-04-09 14:48 ` Štěpán Němec
2020-04-09 17:06 ` Eli Zaretskii
2020-04-09 17:11 ` Eli Zaretskii
2020-04-09 18:44 ` Štěpán Němec
2020-04-09 19:01 ` Eli Zaretskii [this message]
2020-04-09 19:56 ` Štěpán Němec
2020-04-10 6:22 ` Eli Zaretskii
2020-08-26 11:27 ` Štěpán Němec
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=835ze8o53t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6411@debbugs.gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=stefan@marxist.se \
--cc=stepnem@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).