[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer wi
From: |
Eli Zaretskii |
Subject: |
bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason |
Date: |
Sat, 27 Feb 2016 12:14:07 +0200 |
> Cc: Eli Zaretskii <eliz@gnu.org>
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 22 Feb 2016 02:01:21 +0200
>
> Now that the xref window is more "persistent", could you try
> uncommenting the relevant lines in xref--xref-buffer-mode, and see if
> the situation has improved here?
It looks much better now, thanks. I think we can uncomment those
lines now.
A couple of minor nits:
. When one uses next-error to step through hits found by Dired's 'A'
command, point in the *xref* buffer doesn't move to the hit that is
visited in the window displayed above *xref*. Given how next-error
works in other cases, I think users will expect point to move
accordingly; at least I did.
. I see the places I visited marked by a special face in *xref*
(good!), but I don't quite understand when they get marked. They
certainly don't get marked as I move through hits with next-error
or with an explicit RET on a hit in the *xref* buffer. Perhaps we
should mark them in real time? That would also help in
understanding what that face means, I think.
- bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason, (continued)
- bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason, Dmitry Gutov, 2016/02/01
- bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason, Dmitry Gutov, 2016/02/21
- bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason, Eli Zaretskii, 2016/02/22
- bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason, Dmitry Gutov, 2016/02/22
- bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason, Eli Zaretskii, 2016/02/22
- bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason, Dmitry Gutov, 2016/02/22
- bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason, Dmitry Gutov, 2016/02/22
- bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason, Eli Zaretskii, 2016/02/22
bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason,
Eli Zaretskii <=