From: "Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74637@debbugs.gnu.org
Subject: bug#74637: [PATCH] Make view-read-only behave like view-file
Date: Mon, 02 Dec 2024 20:08:46 +0200 [thread overview]
Message-ID: <19894.809152332$1733162977@news.gmane.org> (raw)
In-Reply-To: <86ldwy46al.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 02 Dec 2024 14:29:22 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sun, 01 Dec 2024 22:40:16 +0200
>> From: Björn Bidar via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> Make view-mode behave like when called in view-file when entered because
>> `view-read-only' is true on a file which is not writable.
>> The change makes the view-read-only behave better on files which are
>> not writable.
>> Now it makes Emacs behave more like less on these files.
>
> That's an incompatible behavior change. Is that justified? How can
> we be sure that everyone agrees with your interpretation of this mode?
All other view-file like modes behave like this, you view the file and
leave the file with q.
But even going with that point: You open a file file which isn't
writable. Once you hit q the window is quit and the buffer is buried.
What do you do now next time you visit that file?
The buffer was buried, view-mode isn't active anymore, you would have
to activate view-mode again to go where you left off.
If you would want to edit the file the you visited this way you would
have not pressed q but e to exit view mode and the proceeded to exit
read-only-mode and edit the file.
next prev parent reply other threads:[~2024-12-02 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ldwzm91r.fsf@>
2024-12-02 12:29 ` bug#74637: [PATCH] Make view-read-only behave like view-file Eli Zaretskii
2024-12-02 18:08 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
[not found] ` <87ttbmj6tt.fsf@>
2024-12-02 19:33 ` Eli Zaretskii
2024-12-03 10:06 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87mshdjd2k.fsf@>
2024-12-03 14:01 ` Eli Zaretskii
2024-12-03 14:25 ` Visuwesh
2024-12-03 19:33 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-03 19:39 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <874j3kimjv.fsf@>
2024-12-03 19:43 ` Eli Zaretskii
2024-12-01 20:40 Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='19894.809152332$1733162977@news.gmane.org' \
--to=bug-gnu-emacs@gnu.org \
--cc=74637@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).