[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: |
Dmitry Gutov |
|
Subject: |
bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason |
|
Date: |
Tue, 1 Mar 2016 01:30:37 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 |
On 02/29/2016 06:23 PM, Eli Zaretskii wrote:
Really? Isn't that strange? Doesn't every user of next-error want
that?
Just yet another way next-error-function is broken, it seems.
Please uncomment those lines, if you didn't already.
Already did, in aae436e2d898a8c8cc243c73d6cec5a8c566a061.
- 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/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, 2016/02/27