GNU bug report logs - #70163
29.3; hexl-mode incorrect docstring

Previous Next

Package: emacs;

Reported by: Thierry Volpiatto <thievol <at> posteo.net>

Date: Wed, 3 Apr 2024 15:02:01 UTC

Severity: normal

Found in version 29.3

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: thievol <at> posteo.net, 70163 <at> debbugs.gnu.org, schwab <at> linux-m68k.org
Subject: bug#70163: 29.3; hexl-mode incorrect docstring
Date: Sun, 07 Apr 2024 19:11:59 +0300
> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: thievol <at> posteo.net,  schwab <at> linux-m68k.org,  70163 <at> 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?




This bug report was last modified 1 year and 43 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.