GNU bug report logs -
#20489
25.0.50; next-error-find-buffer chooses non-current buffer without good reason
Previous Next
Reported by: Dmitry Gutov <dgutov <at> yandex.ru>
Date: Sat, 2 May 2015 23:19:01 UTC
Severity: normal
Found in version 25.0.50
Done: Juri Linkov <juri <at> linkov.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> Ah, before arriving to the function without body I mistakenly tried #'identity
> (that didn't work) whereas I actually intended to try #'ignore.
Should we provide the K combinator?
> But the question that I really don't understand is what to do with the
> function next-error-buffer-on-selected-frame that now will have no
> reference in code, no use by default. How the users are supposed to
> know that it's possible to put add-function with this function in the
> init file?
Ah, so that's why you had a defcustom? Then maybe having it be
a defcustom is a good idea.
Stefan "to tell you the truth, I haven't bothered to look at the
code to try to understand what these things are doing,
so I have no opinion on whether it should be a defcustom
or not, or if should be a function defcustom rather
than, say, a boolean defcustom"
This bug report was last modified 7 years and 72 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.