GNU bug report logs - #79325
30.1; Typo in doc/misc/flymake.texi

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#79325: closed (30.1; Typo in doc/misc/flymake.texi)
Date: Thu, 28 Aug 2025 06:00:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 28 Aug 2025 08:59:17 +0300
with message-id <861powt2a2.fsf <at> gnu.org>
and subject line Re: bug#79325: 30.1; Typo in doc/misc/flymake.texi
has caused the debbugs.gnu.org bug report #79325,
regarding 30.1; Typo in doc/misc/flymake.texi
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
79325: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=79325
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Tim Landscheidt <tim <at> tim-landscheidt.de>
To: bug-gnu-emacs <at> gnu.org
Subject: 30.1; Typo in doc/misc/flymake.texi
Date: Thu, 28 Aug 2025 00:18:08 +0000

doc/misc/flymake.texi reads:

| @cindex next and previous diagnostic
| If the diagnostics are outside the visible region of the buffer,
| @code{flymake-goto-next-error} and @code{flymake-goto-prev-error} are
                                                                    ^^^
| let you navigate to the next/previous erroneous regions,
| respectively.  It might be a good idea to map them to @kbd{M-n} and
| @kbd{M-p} in @code{flymake-mode}, by adding to your init file:

The "are" seems to be out of place.

[Message part 3 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Tim Landscheidt <tim <at> tim-landscheidt.de>
Cc: 79325-done <at> debbugs.gnu.org
Subject: Re: bug#79325: 30.1; Typo in doc/misc/flymake.texi
Date: Thu, 28 Aug 2025 08:59:17 +0300

> From: Tim Landscheidt <tim <at> tim-landscheidt.de>
> Date: Thu, 28 Aug 2025 00:18:08 +0000
> 
> doc/misc/flymake.texi reads:
> 
> | @cindex next and previous diagnostic
> | If the diagnostics are outside the visible region of the buffer,
> | @code{flymake-goto-next-error} and @code{flymake-goto-prev-error} are
>                                                                     ^^^
> | let you navigate to the next/previous erroneous regions,
> | respectively.  It might be a good idea to map them to @kbd{M-n} and
> | @kbd{M-p} in @code{flymake-mode}, by adding to your init file:
> 
> The "are" seems to be out of place.

Thanks, fixed on the emacs-30 release branch, and closing the bug.

Previous Next

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