all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Bernd Rellermeyer <bernd.rellermeyer@t-online.de>, 61652@debbugs.gnu.org
Subject: bug#61652: 28.2; Read-only mode and View mode
Date: Tue, 5 Sep 2023 16:48:02 -0700	[thread overview]
Message-ID: <CADwFkmnL_g_OHsRun0CttVGU5HbN=JReCM_TbzxbRNuCFEOHxQ@mail.gmail.com> (raw)
In-Reply-To: <83a617tbby.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 21 Feb 2023 15:08:49 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Bernd Rellermeyer <bernd.rellermeyer@t-online.de>
>> Date: Tue, 21 Feb 2023 13:46:50 +0100
>> Cc: 61652@debbugs.gnu.org
>>
>> In step 3, View mode is entered implicitly, because `view-read-only` is
>> non-nil. From the user perspective it is only one command. I.e. the user just
>> turns off and on Read-only mode. That means the user enters View mode vie
>> Read-Only mode from a writable buffer. I think this should not alter the
>> behavior of `View-exit` and after calling `View-exit` he should be in a
>> writable buffer. Or am I wrong?
>
> I'm not sure I agree with your interpretation.
>
> Does anyone else have an opinion?

I don't think I agree either.  Once the user starts changing
read-only-mode, I think disabling it when leaving view-mode would be
surprising.

In any case, leaving it as read-only is only a minor annoyance.
Changing it to read-write means the user can suddenly start doing
destructive things in a situation where that might be unexpected.

So I'm not sure we should do anything at all here.





  reply	other threads:[~2023-09-05 23:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20  8:41 bug#61652: 28.2; Read-only mode and View mode Bernd Rellermeyer
2023-02-20 14:42 ` Eli Zaretskii
2023-02-21 12:46   ` Bernd Rellermeyer
2023-02-21 13:08     ` Eli Zaretskii
2023-09-05 23:48       ` Stefan Kangas [this message]
2023-09-06 11:32         ` Eli Zaretskii
2023-09-06 12:08           ` Stefan Kangas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkmnL_g_OHsRun0CttVGU5HbN=JReCM_TbzxbRNuCFEOHxQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=61652@debbugs.gnu.org \
    --cc=bernd.rellermeyer@t-online.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.