unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 32322@debbugs.gnu.org, Terje Larsen <terlar@gmail.com>
Subject: bug#32322: 27.0.50; Connect flymake to next-error-function when enabled
Date: Wed, 18 May 2022 21:12:03 +0300	[thread overview]
Message-ID: <86zgjed94g.fsf@mail.linkov.net> (raw)
In-Reply-To: <87zgjfca17.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 18 May 2022 14:14:44 +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.
>
> 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.





      reply	other threads:[~2022-05-18 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 21:41 bug#32322: 27.0.50; Connect flymake to next-error-function when enabled Terje Larsen
2022-05-18 12:14 ` Lars Ingebrigtsen
2022-05-18 18:12   ` Juri Linkov [this message]

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=86zgjed94g.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=32322@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=terlar@gmail.com \
    /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).