[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: |
Mon, 22 Feb 2016 19:22:00 +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?
Will do. To make this more efficient, can you suggest what situations
to try?
Thanks.
- bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason, Juri Linkov, 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 <=
- 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, 2016/02/27