|
From: | Dmitry Gutov |
Subject: | Re: next-error use cases |
Date: | Thu, 21 May 2020 04:57:46 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 |
On 20.05.2020 01:12, Juri Linkov wrote:
Some rough idea: pick some similar keybinding in flymake-supported buffers ('C-c C-c'? wouldn't it be too presumptuous to take over?)... and make it,And bind it to next-error-select-buffer.I don't know, echo the error text? Or (!) show the diagnostics buffer, for which there's no default key binding still. And in the end, call next-error-found.Indeed, using the diagnostics buffer is a good idea (even without showing it).
We could use the diagnostics in a similar fashion to compilation, xref, occur, etc, buffers to detect that the user definitely wants next-error-last-buffer changed.
And either set that variable when the user displays the diagnostics buffer, or when they use one of the "buttons" inside (but IME it's a very rare even, I never use them, unlike Compilation or Grep "buttons").
That would require showing it, however. But otherwise could enable a streamlined approach to all next-error-function enabled buffers, where the behavior of Flymake based ones doesn't much differ from others.
In all this, I'm most concerned about the keybinding: 'C-c C-c' would follow an existing example, but it's seems too valuable to take over in all programming major modes.
It calls comment-region in c-mode (and a few others), but that duplicates an existing binding.
In prolog-mode, ps-mode, sql-mode it invokes some unique commands, however.
[Prev in Thread] | Current Thread | [Next in Thread] |