bogus extra RET required when entering filenames (etc)?

bogus extra RET required when entering filenames (etc)?

[Miles Bader]

There's a file in /tmp called "/tmp/x.c".  I type:

   C-x C-f /tmp/x.c RET

However, instead of visiting the file (which incidentally is already in
a buffer), emacs prints " [confirm]" at the end of the prompt, and I
have to hit RET again.

This didn't happen with an emacs from ~2 days ago, so it seems to be a
new problem.

Thanks,

-Miles

-- 
The car has become... an article of dress without which we feel uncertain,
unclad, and incomplete.  [Marshall McLuhan, Understanding Media, 1964]

Re: bogus extra RET required when entering filenames (etc)?

[Chong Yidong]

Miles Bader <miles.bader@necel.com> writes:

> There's a file in /tmp called "/tmp/x.c".  I type:
>
>    C-x C-f /tmp/x.c RET
>
> However, instead of visiting the file (which incidentally is already in
> a buffer), emacs prints " [confirm]" at the end of the prompt, and I
> have to hit RET again.
>
> This didn't happen with an emacs from ~2 days ago, so it seems to be a
> new problem.

This was from the recent introduction of the variable
confirm-nonexistent-file-or-buffer---previously
find-file-confirm-nonexistent-file---which had its default set as t.
I've checked in a fix to switch the default to nil.

Re: bogus extra RET required when entering filenames (etc)?

[Tassilo Horn]

Chong Yidong <cyd@stupidchicken.com> writes:

Hi!

>> There's a file in /tmp called "/tmp/x.c".  I type:
>>
>>    C-x C-f /tmp/x.c RET
>>
>> However, instead of visiting the file (which incidentally is already
>> in a buffer), emacs prints " [confirm]" at the end of the prompt, and
>> I have to hit RET again.
>
> This was from the recent introduction of the variable
> confirm-nonexistent-file-or-buffer---previously
> find-file-confirm-nonexistent-file---which had its default set as t.
> I've checked in a fix to switch the default to nil.

But Miles said the file already existed.  Why was he asked for
confirmation then?

Bye,
Tassilo

Re: bogus extra RET required when entering filenames (etc)?

[Miles Bader]

Tassilo Horn <tassilo@member.fsf.org> writes:
>> This was from the recent introduction of the variable
>> confirm-nonexistent-file-or-buffer---previously
>> find-file-confirm-nonexistent-file---which had its default set as t.
>> I've checked in a fix to switch the default to nil.
>
> But Miles said the file already existed.  Why was he asked for
> confirmation then?

Actually I went back and redid my test, and realized that although I had
already visited that file and added some contents, so the buffer
existed, I had never _saved_ the file, so there wasn't yet anything on
disk.

I suppose one could make an argument that find-file should consider that
state as "existing" and not require confirmation, but one could also
argue that the current behavior is correct...

-Miles

-- 
Rational, adj. Devoid of all delusions save those of observation, experience
and reflection.

Re: bogus extra RET required when entering filenames (etc)?

[Stefan Monnier]

>> There's a file in /tmp called "/tmp/x.c".  I type:
>> 
>> C-x C-f /tmp/x.c RET
>> 
>> However, instead of visiting the file (which incidentally is already in
>> a buffer), emacs prints " [confirm]" at the end of the prompt, and I
>> have to hit RET again.
>> 
>> This didn't happen with an emacs from ~2 days ago, so it seems to be a
>> new problem.

> This was from the recent introduction of the variable
> confirm-nonexistent-file-or-buffer---previously
> find-file-confirm-nonexistent-file---which had its default set as t.
> I've checked in a fix to switch the default to nil.

The change of default was no accident, it was done on purpose.
Please set it back to t.


        Stefan

Re: bogus extra RET required when entering filenames (etc)?

[mail]

Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The change of default was no accident, it was done on purpose.
> Please set it back to t.
>

Could you point me to the discussion about this change of default? It
seems like it makes the user experience worse.