From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: thievol@posteo.net, 70163@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#70163: 29.3; hexl-mode incorrect docstring
Date: Sun, 07 Apr 2024 19:11:59 +0300 [thread overview]
Message-ID: <86plv1ywxc.fsf@gnu.org> (raw)
In-Reply-To: <jwvsezxxj5j.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 07 Apr 2024 12:07:42 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: thievol@posteo.net, schwab@linux-m68k.org, 70163@debbugs.gnu.org
> Date: Sun, 07 Apr 2024 12:07:42 -0400
>
> >> >> > What is "the more appropriate place", and how will you find it, given
> >> >> > that some doc strings are auto-generated, either in part or in full?
> >> >> Right after the next \n ?
> >> > That could be in the middle of a sentence.
> >> Then insert at point if (and (bolp) (not (bobp)))?
> > But that again could be in the middle of a sentence.
>
> It could.
>
> > Shouldn't we look for the end of the sentence, and insert after that
> > instead? Or what am I missing?
>
> I don't believe in the ability of machines to find the end of
> a sentence. 🙂
Then maybe we shouldn't try to be too smart here? I already added to
Tips the recommendation to have this not in the middle of a sentence,
so maybe we should leave the rest to the programmer?
next prev parent reply other threads:[~2024-04-07 16:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 15:02 bug#70163: 29.3; hexl-mode incorrect docstring Thierry Volpiatto
2024-04-03 15:50 ` Eli Zaretskii
2024-04-03 16:37 ` Andreas Schwab
2024-04-03 17:04 ` Thierry Volpiatto
2024-04-03 18:14 ` Eli Zaretskii
2024-04-04 5:47 ` Thierry Volpiatto
2024-04-04 12:18 ` Eli Zaretskii
2024-04-04 12:45 ` Andreas Schwab
2024-04-04 13:07 ` Eli Zaretskii
2024-04-04 13:20 ` Andreas Schwab
2024-04-04 12:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 13:16 ` Andreas Schwab
2024-04-04 13:23 ` Eli Zaretskii
2024-04-04 13:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 18:41 ` Thierry Volpiatto
2024-04-05 5:46 ` Eli Zaretskii
2024-04-05 6:29 ` Thierry Volpiatto
2024-04-06 10:46 ` Eli Zaretskii
2024-04-06 11:27 ` Thierry Volpiatto
2024-04-06 12:52 ` Ihor Radchenko
2024-04-06 14:05 ` Andreas Schwab
2024-04-06 14:15 ` Eli Zaretskii
2024-04-06 15:05 ` Andreas Schwab
2024-04-06 15:27 ` Eli Zaretskii
2024-04-06 15:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 16:16 ` Eli Zaretskii
2024-04-06 20:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 20:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-07 5:29 ` Eli Zaretskii
2024-04-07 14:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-07 14:57 ` Eli Zaretskii
2024-04-07 16:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-07 16:11 ` Eli Zaretskii [this message]
2024-04-03 17:04 ` Thierry Volpiatto
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=86plv1ywxc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70163@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.org \
--cc=thievol@posteo.net \
/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).