bug#43503: Patch: Improvements regarding commands like find-file-other-tab.

[ej32u]

On 9/19/20 10:34 AM, Lars Ingebrigtsen wrote:
>> +(defun find-file-read-only-other-tab (filename &optional wildcards)
>> +  "Edit file FILENAME, in another tab, but don't allow changes.
>> +Like \\[find-file-other-frame] (which see), but creates a new tab.
>> +
>> +Like C-x t C-f, but marks buffer as read-only.
>> +Use C-x C-q to permit editing."
> This should probably refer to the functions, not the keystrokes?
You are right. I fixed that.
> But anyway -- I'm not really sure I understand the use case here -- is
> opening files in read-only mode a thing that people do a lot?  I mean,
> we have `C-x C-r', so adding tab-opening versions of that would be
> logical, but...
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>     bloggy blog: http://lars.ingebrigtsen.no

I do this only occasionally. I think having them is no different from having 
the 
`-other-frame' and `-other-window' versions of `find-file-read-only'.

I really only want the FFAP versions of these commands, but I think the other 
versions should exist for consistency.

0001-Improvements-regarding-like-find-file-other-tab.patch
Description: Text Data