ECB Asks to make buffer read-only when creating in non-existing directories

[metaturso]

Hello @ware,

After I activate ECB, when I open a new buffer in a non-existing directory, Emacs blocks me with the following prompt in the echo area:

File <the file name here> is read-only on disk.  Make buffer read-only, too? (y or n)

The problem manifests itself only when ECB is activated and I can also reproduce with Emacs -Q loaded with only ECB and none of my personal setup.

I have a feeling, but haven't been able to prove this myself, that this behaviour is controlled by some customisation option in Emacs, as opposed to ECB itself, as a quick grep shows that the message isn't defined in the ECB codebase.

I'd appreciate your help to disable this behaviour so that I can return to creating new directories and buffers anywhere on the filesystem without interruptions.

Are there any ECB or Emacs customisation options which can control this?

Thanks,
~ Andrea

[ware]

Hey @trashofmasters, I'm assuming that you saw this with 25.0.50.1?

[metaturso]

Yes @ware, this is still an issue on 2.5-dev (1d47484).

[aufflick]

Hi, I inadvertently cross-posted this on the old repo as https://github.com/alexott/ecb/issues/35 and it's related to SO http://emacs.stackexchange.com/questions/13935/ecb-never-ask-to-make-buffer-read-only

Note that now I've updated to HEAD of this repo, the behaviour has changed. I no longer get a prompt/dialog, instead the buffer is just set to be read only without prompting, so I need to toggle-read-only after creating the buffer.

Also on 2.5-dev. When the buffer is created, there is a minibuffer message "File not found and directory write-protected" which I can't trace in the ecb code, so I guess it's surfaced from some other dependency.