Re: Possible new feature: use 'openfile' to open new buffer

[Marco Diego Aurélio Mesquita]

On 5/19/20, Benno Schulenberg <address@hidden> wrote:
> No, what I meant is: when --multibuffer and 'set multibuffer' are not
> used, then every invocation of ^R ('insert') will insert the read file
> into the current buffer, *even* when on the previous invocation M-F was
> toggled on.  And inversely, when --multibuffer or 'set multibuffer' ARE
> used, then every invocation of ^R will read a file into a new buffer,
> even when on the previous invocation M-F was toggled OFF.  This would
> achieve what you want (a predictable state of the multibuffer flag)
> while one still can choose what ^R should do by default, AND without
> requiring a new bindable function.
>

Sounds like a much simpler approach. Indeed, this would achieve what I
need without a new bindable function. Please consider the attached
patch.

0001-tweaks-make-insert-into-current-new-buffer-flag-non-.patch
Description: Text Data