GNU bug report logs - #32322
27.0.50; Connect flymake to next-error-function when enabled

Previous Next

Package: emacs;

Reported by: Terje Larsen <terlar <at> gmail.com>

Date: Mon, 30 Jul 2018 21:42:01 UTC

Severity: wishlist

Found in version 27.0.50

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 32322 in the body.
You can then email your comments to 32322 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#32322; Package emacs. (Mon, 30 Jul 2018 21:42:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Terje Larsen <terlar <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Mon, 30 Jul 2018 21:42:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Terje Larsen <terlar <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 27.0.50; Connect flymake to next-error-function when enabled
Date: Mon, 30 Jul 2018 23:41:43 +0200
I know that some other packages utilize the 'next-error-function' to get
support for 'next-error' and 'previous-error'. I wonder if it would make
sense to set this up by default when the flymake mode is enabled. I have
currently enabled it by:

  (setq next-error-function 'flymake-goto-next-error)

And it seems to work flawlessly.

In GNU Emacs 27.0.50 (build 1, x86_64-apple-darwin13.4.0, NS
appkit-1265.21 Version 10.9.5 (Build 13F1911))
of 2018-05-07 built on builder10-9.local
Windowing system distributor 'Apple', version 10.3.1561
System Description:  Mac OS X 10.13.6

Configured using:
'configure --with-ns '--enable-locallisppath=/Library/Application
Support/Emacs/${version}/site-lisp:/Library/Application
Support/Emacs/site-lisp' --with-modules'

Configured features:
NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS

Important settings:
  value of $LANG: en_SE.UTF-8
  locale-coding-system: utf-8

Major mode: Emacs-Lisp

-- 
// Terje Larsen




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#32322; Package emacs. (Wed, 18 May 2022 12:15:02 GMT) Full text and rfc822 format available.

Message #8 received at 32322 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Terje Larsen <terlar <at> gmail.com>
Cc: 32322 <at> debbugs.gnu.org
Subject: Re: bug#32322: 27.0.50; Connect flymake to next-error-function when
 enabled
Date: Wed, 18 May 2022 14:14:44 +0200
Terje Larsen <terlar <at> gmail.com> writes:

> I know that some other packages utilize the 'next-error-function' to get
> support for 'next-error' and 'previous-error'. I wonder if it would make
> sense to set this up by default when the flymake mode is enabled. I have
> currently enabled it by:
>
>   (setq next-error-function 'flymake-goto-next-error)
>
> And it seems to work flawlessly.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

I don't think it would be appropriate for flymake-mode to set that
itself, since that variable is mostly just meant for other
compilation-line major modes to set buffer-locally.  But I can see how
it might be convenient for users that mainly just use flymake and not
the regular `M-x compile', so I've now mentioned this in the
flymake-mode doc string in Emacs 29.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




bug marked as fixed in version 29.1, send any further explanations to 32322 <at> debbugs.gnu.org and Terje Larsen <terlar <at> gmail.com> Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Wed, 18 May 2022 12:15:03 GMT) Full text and rfc822 format available.

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#32322; Package emacs. (Wed, 18 May 2022 18:23:01 GMT) Full text and rfc822 format available.

Message #13 received at 32322 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 32322 <at> debbugs.gnu.org, Terje Larsen <terlar <at> gmail.com>
Subject: Re: bug#32322: 27.0.50; Connect flymake to next-error-function when
 enabled
Date: Wed, 18 May 2022 21:12:03 +0300
>> I know that some other packages utilize the 'next-error-function' to get
>> support for 'next-error' and 'previous-error'. I wonder if it would make
>> sense to set this up by default when the flymake mode is enabled. I have
>> currently enabled it by:
>>
>>   (setq next-error-function 'flymake-goto-next-error)
>>
>> And it seems to work flawlessly.
>
> I don't think it would be appropriate for flymake-mode to set that
> itself, since that variable is mostly just meant for other
> compilation-line major modes to set buffer-locally.  But I can see how
> it might be convenient for users that mainly just use flymake and not
> the regular `M-x compile', so I've now mentioned this in the
> flymake-mode doc string in Emacs 29.

The problem with enabling next-error-function in buffers
where flymake-mode is activated is that there is no evident
visual indication that next-error is used to navigate errors
in the current buffer.  In other modes like compilation
the enabled next-error-function is usually indicated
by the presence of the compilation window with a list of errors
nearby.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Thu, 16 Jun 2022 11:24:05 GMT) Full text and rfc822 format available.

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

Previous Next


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