|
From: | Dmitry Gutov |
Subject: | bug#21175: 24.5; progmodes/etags.el: next-file does (find-file next novisit) |
Date: | Sat, 1 Aug 2015 14:45:06 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Thunderbird/40.0 |
Version: 25.1 On 08/01/2015 12:53 PM, phs wrote:
Passing novisit is dangerous since find-file takes this as the wildcards flag, nothing to do with the meaning of novisit. Actually, if the filename contains * or ? (and is currently visited, or "not new") tags may create many buffers visiting many files that match the filename interpreted as a pattern, not an actual file name. What buffer will be searched next is maybe not the one associated with filename.
Thanks, this is fixed now as well.
The comment too is incorrect.
I think the comment refers to the code below it.
[Prev in Thread] | Current Thread | [Next in Thread] |