unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>, Tino Calancha <tino.calancha@gmail.com>
Cc: 28864@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#28864: 25.3.50; next-error-no-select does select
Date: Mon, 23 Oct 2017 01:29:09 +0300	[thread overview]
Message-ID: <7f67cb1c-062f-44fa-ba8e-9ac0cab220a3@yandex.ru> (raw)
In-Reply-To: <874lqreyj5.fsf@localhost>

On 10/22/17 11:32 PM, Juri Linkov wrote:

> Visiting a buffer should not set next-error-last-buffer,
> it should be set only by an explicit user request,
> like M-x compile/grep/rgrep/occur and other commands do.
 >
> So please just remove setting of next-error-last-buffer
> from change-log-mode.

Why not remove it from compilation-start as well? And 
xref--xref-buffer-mode.

After all, the user can visit the results buffer and press M-x 
next-error just as well.

> We also have other issues with next-error in bug#20489
> where I'm waiting when Dmitry will send a comprehensive list
> of possible scenarios, so we could find a solution that fits
> all of them.

I had no idea that someone is waiting for something like that. Is there 
a question in the bug discussion that I'd missed?

My scenario template is basically this:

1. Visit a buffer <A> in some major mode, press M-x next-error or M-x 
previous-error an arbitrary number of times, visiting the appropriate 
error locations, whether they are in the current buffer or in some other 
buffers or files that will have to be opened.

2. The above should happen fine irrespective of the current window 
configuration, and whether the buffer <A> gets hidden for some reason 
during this process (and we do know the possible reasons).

3. Being able to open a different buffer <B>, *somehow* switch to its 
error function, and have M-x next-error and M-x previous-error use it.

4. Being able to go to step 1 without much hassle.

Please ask any further questions.

> 4. When the user needs to switch to visiting ChangeLog entries
>     from the ChangeLog buffer, this can be achieved by typing
>     C-c C-c (change-log-goto-source) once, then all subsequent
>     M-g M-n will continue visiting next ChangeLog entries
>     in the source files.

As solutions go, it's a step forward.

But far from ideal: generally speaking, it requires a separate command 
and a binding in each suitable major mode that will switch to its 
next-error-function.





  reply	other threads:[~2017-10-22 22:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 13:07 bug#28864: 25.3.50; next-error-no-select does select Tino Calancha
2017-10-17 13:37 ` Dmitry Gutov
2017-10-17 14:17   ` Tino Calancha
2017-10-18  7:44     ` Dmitry Gutov
2017-10-20  7:21       ` Tino Calancha
2017-10-20 21:49         ` Dmitry Gutov
2017-10-21  3:52           ` Tino Calancha
2017-10-22 20:32             ` Juri Linkov
2017-10-22 22:29               ` Dmitry Gutov [this message]
2017-10-23 20:12                 ` Juri Linkov
2017-10-23 20:23                   ` Dmitry Gutov
2017-10-24 20:22                     ` Juri Linkov
2017-10-24 22:23                       ` Dmitry Gutov
2017-10-25 23:58                         ` Dmitry Gutov
2017-10-28 21:07                         ` Juri Linkov
2017-10-28 22:46                           ` Dmitry Gutov
2017-10-29 21:42                             ` Juri Linkov
2017-10-30 14:59                               ` Dmitry Gutov
2017-10-30 18:30                                 ` Eli Zaretskii
2017-10-30 21:13                                   ` Dmitry Gutov
2017-10-30 21:15                                   ` Juri Linkov
2017-10-30 21:14                                 ` Juri Linkov
2017-10-31  0:02                                   ` Dmitry Gutov
2017-10-31 21:56                                     ` Juri Linkov
2017-10-31 23:42                                       ` Dmitry Gutov
2017-11-02 22:00                                         ` Juri Linkov
2017-11-05 13:37                                           ` Dmitry Gutov
2017-11-06 21:41                                             ` Juri Linkov
2017-10-28 20:54             ` Juri Linkov
2017-10-28 22:42               ` Dmitry Gutov

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=7f67cb1c-062f-44fa-ba8e-9ac0cab220a3@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=28864@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=npostavs@gmail.com \
    --cc=tino.calancha@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).