From: "Štěpán Němec" <stepnem@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40695@debbugs.gnu.org
Subject: bug#40695: [PATCH] ; Fix some typos and doc issues
Date: Sat, 18 Apr 2020 18:04:22 +0200 [thread overview]
Message-ID: <87a7387pbt.fsf@gmail.com> (raw)
In-Reply-To: <83pnc4kdmb.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 18 Apr 2020 18:38:52 +0300")
On Sat, 18 Apr 2020 18:38:52 +0300
Eli Zaretskii wrote:
>> From: Štěpán Němec <stepnem@gmail.com>
>> Cc: 40695-done@debbugs.gnu.org
>> Date: Sat, 18 Apr 2020 17:31:18 +0200
>>
>> > Either the split already occurs or is close (i.e. the offending text
>> > is close to the edge of a line. Otherwise we will have to put all of
>> > them in @w{..}, and that seems too much.
>>
>> I rechecked the occurences and tried to remove some of the added @w{}s,
>> and notably failed with ispell-kill-ispell and ispell-change-dictionary,
>> both of which are as far from the edges as one can get (the case of
>> ispell-message was already mentioned in the bug#6411 message)
>
> Sorry, I don't understand what failed here.
Even though all three of them are in the middle of the line (in
Texinfo), they end up split in Info, unless wrapped in @w{}.
> Maybe I wasn't clear enough: by "close to the edge" I meant in the
> produced Info file, not in Texinfo. If that's not the issue, please
> point out what am I missing.
Yes, that's the issue: the Texinfo source doesn't seem to be useful in
determining which occurences are safe from splitting (which seemed to be
what you were saying in
https://lists.gnu.org/archive/html/bug-gnu-emacs/2020-04/msg00245.html
835ze8o53t.fsf@gnu.org
)
The only way to know is checking the Info output, barred maybe some
exceptional cases like single-line paragraphs.
--
Štěpán
next prev parent reply other threads:[~2020-04-18 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 11:37 bug#40695: [PATCH] ; Fix some typos and doc issues Štěpán Němec
2020-04-18 12:28 ` Eli Zaretskii
2020-04-18 13:13 ` Štěpán Němec
2020-04-18 13:47 ` Eli Zaretskii
2020-04-18 15:31 ` Štěpán Němec
2020-04-18 15:38 ` Eli Zaretskii
2020-04-18 16:04 ` Štěpán Němec [this message]
2020-04-18 16:17 ` Eli Zaretskii
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=87a7387pbt.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=40695@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).