[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: another bug of find-file-noselect?

From: Kenichi Handa
Subject: Re: another bug of find-file-noselect?
Date: Wed, 25 Oct 2000 09:42:57 +0900 (JST)

Gerd Moellmann <address@hidden> writes:
> Kenichi Handa <address@hidden> writes:
>>  Even if there are files temp.1, temp.2, temp.3, 
>>  (find-file-noselect "temp.*" t t t) returns the buffer for
>>  temp.1 only against this docstring:
> [...]
>>  It seems that we can fix this bug just by removing the last
>>  `car' call in this code of find-file-noselect.
> I agree, that `car' looks bogus.

>>  But, it seems that the existence of `car' call is
>>  intentional.  In that case, docstring should be fixed.

> I don't know why that `car' is there.  Maybe returning a list caused
> some problem and a quick ``fix'' was to return a single buffer?

I found that this part was changed by Andre on 2000.10.4 by
the revision 1.505 (though there's no entry for that in
ChangeLog).  The change seems to be for fixing something
related to vc.   Andre, if we remove `car', does it cause
problem to vc?

>>  Could someone tell which is wrong, the code or the
>>  docstring?  I myselft want to fix the code because otherwise
>>  we don't know which buffers are created by this function.

> I also think the code is in error.

>>  By the way, Emacs Lisp Reference Manual says nothing special
>>  for the case that WILDCARDS is non-nil.   It just says:
>>       The `find-file-noselect' function returns the buffer that is
>>       visiting the file FILENAME.

> Could you please add the missing bits?

I've changed the last paragraph as this:

The @code{find-file-noselect} function usually returns the buffer that
is visiting the file @var{filename}.  But, if wildcards are actually
used and expanded, it returns a list of buffer tha are visiting the
various files.

Ken'ichi HANDA

reply via email to

[Prev in Thread] Current Thread [Next in Thread]