From unknown Mon Jun 23 04:10:47 2025 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 From: bug#61652 <61652@debbugs.gnu.org> To: bug#61652 <61652@debbugs.gnu.org> Subject: Status: 28.2; Read-only mode and View mode Reply-To: bug#61652 <61652@debbugs.gnu.org> Date: Mon, 23 Jun 2025 11:10:47 +0000 retitle 61652 28.2; Read-only mode and View mode reassign 61652 emacs submitter 61652 Bernd Rellermeyer severity 61652 normal tag 61652 wontfix notabug thanks From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 20 09:08:54 2023 Received: (at submit) by debbugs.gnu.org; 20 Feb 2023 14:08:55 +0000 Received: from localhost ([127.0.0.1]:51061 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU6qc-0003sI-4t for submit@debbugs.gnu.org; Mon, 20 Feb 2023 09:08:54 -0500 Received: from lists.gnu.org ([209.51.188.17]:45884) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU1kg-0000hh-MO for submit@debbugs.gnu.org; Mon, 20 Feb 2023 03:42:27 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pU1kW-00017l-HY for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 03:42:21 -0500 Received: from mailout02.t-online.de ([194.25.134.17]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pU1kT-0006MW-6r for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 03:42:15 -0500 Received: from fwd76.dcpf.telekom.de (fwd76.aul.t-online.de [10.223.144.102]) by mailout02.t-online.de (Postfix) with SMTP id 3A65033AC for ; Mon, 20 Feb 2023 09:41:56 +0100 (CET) Received: from Bernds-Mac-mini.fritz.box ([62.216.207.90]) by fwd76.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1pU1kB-1IDbaT0; Mon, 20 Feb 2023 09:41:55 +0100 From: Bernd Rellermeyer To: bug-gnu-emacs@gnu.org Subject: 28.2; Read-only mode and View mode Date: Mon, 20 Feb 2023 09:41:33 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-TOI-EXPURGATEID: 150726::1676882515-E5D7A2C2-13E740D5/0/0 CLEAN NORMAL X-TOI-MSGID: 03ffb622-471b-4a3c-b4eb-5eb072c1ac34 Received-SPF: none client-ip=194.25.134.17; envelope-from=bernd.rellermeyer@t-online.de; helo=mailout02.t-online.de X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: submit X-Mailman-Approved-At: Mon, 20 Feb 2023 09:08:49 -0500 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) I have the following scenario: 1. View a buffer in View mode. 2. Turn off Read-Only mode, e.g. by pressing `C-x C-q`. 3. Turn on Read-Only mode and View mode again, eg. by pressing `C-x C-q`- 4. Exit View mode by `View-exit`, e.g. by pressing `e`. Now the buffer is in Read-Only mode. In my opinion it should be writable. The reason is the variable `view-old-buffer-read-only`, which is set on entering View mode (`view--enable`) to the (old) value of `buffer-read-only`. But in my scenario, the value of `buffer-read-only` is already the new one, as set in `read-only-mode`. I think the solution is to reset `read-only-mode` to nil in the specific branch of `read-only-mode` and depend on the fact that it is set to t in `view--enable`: ``` (cond ((and (not buffer-read-only) view-mode) (View-exit-and-edit) (setq-local view-read-only t)) ; Must leave view mode. ((and buffer-read-only view-read-only ;; If view-mode is already active, `view-mode-enter' is a nop. (not view-mode) (not (eq (get major-mode 'mode-class) 'special))) (setq buffer-read-only nil) (view-mode-enter)))) ``` In GNU Emacs 28.2 (build 1, x86_64-apple-darwin18.7.0, NS appkit-1671.60 Version 10.14.6 (Build 18G95)) of 2022-09-12 built on builder10-14.lan Windowing system distributor 'Apple', version 10.3.2299 System Description: macOS 13.2.1 Configured using: 'configure --with-ns '--enable-locallisppath=/Library/Application Support/Emacs/${version}/site-lisp:/Library/Application Support/Emacs/site-lisp' --with-modules' Configured features: ACL GMP GNUTLS JSON LIBXML2 MODULES NOTIFY KQUEUE NS PDUMPER THREADS TOOLKIT_SCROLL_BARS ZLIB Important settings: value of $LANG: de_DE.UTF-8 locale-coding-system: utf-8-unix Major mode: Help Minor modes in effect: which-function-mode: t delete-selection-mode: t cua-mode: t global-auto-revert-mode: t global-display-glyphs-mode: t override-global-mode: t tooltip-mode: t global-eldoc-mode: t show-paren-mode: t electric-indent-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t buffer-read-only: t line-number-mode: t transient-mark-mode: t Load-path shadows: /Users/bernd/.config/emacs/elpa/magit-3.3.0/magit-section-pkg hides /Users/bernd/.config/emacs/elpa/magit-section-3.3.0/magit-section-pkg /Users/bernd/.config/emacs/elpa/transient-0.3.7/transient hides /Applications/Emacs.app/Contents/Resources/lisp/transient /Users/bernd/.config/emacs/elpa/xref-1.6.1/xref hides /Applications/Emacs.app/Contents/Resources/lisp/progmodes/xref /Users/bernd/.config/emacs/elpa/project-0.9.8/project hides /Applications/Emacs.app/Contents/Resources/lisp/progmodes/project Features: (shadow sort mail-extr emacsbug calc-alg calc-ext calc-menu calc calc-loaddefs rect calc-macs pandoc-mode pandoc-mode-utils hydra lv markdown-mode edit-indirect transient magit-utils dash org-colview org-clock disp-table zetteltags-global zetteltags pcre2el rxt pcase re-builder crm adaptive-wrap text-face face-remap org-element avl-tree generator ol-eww eww xdg url-queue mm-url ol-rmail ol-mhe ol-irc ol-info ol-gnus nnselect gnus-search gnus-art mm-uu mml2015 mm-view mml-smime smime dig gnus-sum shr kinsoku svg dom gnus-group gnus-undo gnus-start gnus-dbus dbus xml gnus-cloud nnimap nnmail mail-source utf7 netrc nnoo parse-time gnus-spec gnus-int gnus-range message rmc puny rfc822 mml mml-sec epa derived epg rfc6068 epg-config mm-decode mm-bodies mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader gnus-win ol-docview doc-view image-mode exif ol-bibtex ol-bbdb ol-w3m ol-doi org-link-doi org-agenda org-refile reftxt reftex-cite reftex reftex-loaddefs reftex-vars org ob ob-tangle ob-ref ob-lob ob-table ob-exp org-macro org-footnote org-src ob-comint org-pcomplete pcomplete comint ansi-color org-list org-faces org-entities noutline outline org-version ob-emacs-lisp ob-core ob-eval org-table oc-basic bibtex iso8601 org-keys oc org-loaddefs ol rx org-compat advice org-macs format-spec cal-menu calendar cal-loaddefs eieio-opt speedbar ezimage dframe shortdoc undo-fu debug dabbrev misearch multi-isearch pulse thai-util thai-word help-fns radix-tree cl-print edebug backtrace find-func dired-aux dired-x dired dired-loaddefs add-log which-func imenu delsel cua-base quail autorevert filenotify view-x hi-lock scroll-lock view god-mode cl-extra help-mode ns-plist jka-compr display-glyphs unfill color modus-vivendi-theme modus-operandi-theme modus-themes launch my-skeletons skeleton xref project bind-key easy-mmode zetteldeft ace-window thingatpt avy ring deft gnus nnheader gnus-util rmail rmail-loaddefs text-property-search time-date sendmail rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-utils cus-edit pp cus-load wid-edit edmacro kmacro tex-site info package browse-url url url-proxy url-privacy url-expand url-methods url-history url-cookie url-domsuf url-util mailcap url-handlers url-parse auth-source cl-seq eieio eieio-core cl-macs eieio-loaddefs password-cache json subr-x map url-vars seq byte-opt gv bytecomp byte-compile cconv cl-loaddefs cl-lib iso-transl tooltip eldoc paren electric uniquify ediff-hook vc-hooks lisp-float-type elisp-mode mwheel term/ns-win ns-win ucs-normalize mule-util term/common-win tool-bar dnd fontset image regexp-opt fringe tabulated-list replace newcomment text-mode lisp-mode prog-mode register page tab-bar menu-bar rfn-eshadow isearch easymenu timer select scroll-bar mouse jit-lock font-lock syntax font-core term/tty-colors frame minibuffer cl-generic cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech european ethiopic indian cyrillic chinese composite emoji-zwj charscript charprop case-table epa-hook jka-cmpr-hook help simple abbrev obarray cl-preloaded nadvice button loaddefs faces cus-face macroexp files window text-properties overlay sha1 md5 base64 format env code-pages mule custom widget hashtable-print-readable backquote threads kqueue cocoa ns multi-tty make-network-process emacs) Memory information: ((conses 16 605640 36594) (symbols 48 36818 4) (strings 32 124518 7449) (string-bytes 1 4182471) (vectors 16 67356) (vector-slots 8 1431598 28878) (floats 8 501 324) (intervals 56 10795 698) (buffers 992 32)) From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 20 09:42:27 2023 Received: (at 61652) by debbugs.gnu.org; 20 Feb 2023 14:42:28 +0000 Received: from localhost ([127.0.0.1]:51138 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU7N5-00078s-KU for submit@debbugs.gnu.org; Mon, 20 Feb 2023 09:42:27 -0500 Received: from eggs.gnu.org ([209.51.188.92]:52448) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU7N1-00078d-Sc for 61652@debbugs.gnu.org; Mon, 20 Feb 2023 09:42:25 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pU7Mw-0002T8-CP; Mon, 20 Feb 2023 09:42:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=WprOZY+z6cxer6FjtqsYbwerFfTqL2lbnHzIKvumHcI=; b=nYzjFn+UqLTx 1IGymWUIGsoFS88IG6WvolUxglcVb7JmvLKDoZd26WRytiR5jmmuqpRgLdw48mRmiGkpdPdT3m1f7 24bqnvJyfCvTuNqxs9EMLgsvQLQnfLqNqfcmVT86nH8vj6jRWQnBdHM7GvysejMGjnqmlGWJ4WKw7 Wi6N9JtGEE17dV6nta+E9aG2GZSOsKFtZQ/cP6/C1rBYjzCS0pWWtaHtbmAHduSjsBCRm2E76xZa8 2W6x3i9YLqkdTVVR5HLh+9ixmrNaIb/p0aATs+TKu0o2kwCK+eKUTZo5E7fOVnY7IFH4x1CKXNTew J50E/aUtJGrYMIkpWEqNHA==; Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pU7Mv-0003KH-G2; Mon, 20 Feb 2023 09:42:17 -0500 Date: Mon, 20 Feb 2023 16:42:25 +0200 Message-Id: <83bklov1ny.fsf@gnu.org> From: Eli Zaretskii To: Bernd Rellermeyer In-Reply-To: (message from Bernd Rellermeyer on Mon, 20 Feb 2023 09:41:33 +0100) Subject: Re: bug#61652: 28.2; Read-only mode and View mode References: X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 61652 Cc: 61652@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Bernd Rellermeyer > Date: Mon, 20 Feb 2023 09:41:33 +0100 > > > I have the following scenario: > > 1. View a buffer in View mode. > 2. Turn off Read-Only mode, e.g. by pressing `C-x C-q`. > 3. Turn on Read-Only mode and View mode again, eg. by pressing `C-x > C-q`- > 4. Exit View mode by `View-exit`, e.g. by pressing `e`. > > Now the buffer is in Read-Only mode. In my opinion it should be > writable. The reason is the variable `view-old-buffer-read-only`, which > is set on entering View mode (`view--enable`) to the (old) value of > `buffer-read-only`. But in my scenario, the value of `buffer-read-only` > is already the new one, as set in `read-only-mode`. If the buffer is already read-only when you enter View mode, why should we reset read-only when exiting View mode? We are trying to leave the buffer as we found it, which in this case is read-only. Or what am I missing? From debbugs-submit-bounces@debbugs.gnu.org Tue Feb 21 08:08:46 2023 Received: (at 61652) by debbugs.gnu.org; 21 Feb 2023 13:08:46 +0000 Received: from localhost ([127.0.0.1]:54940 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pUSNy-0003gR-4q for submit@debbugs.gnu.org; Tue, 21 Feb 2023 08:08:46 -0500 Received: from eggs.gnu.org ([209.51.188.92]:47838) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pUSNw-0003g7-I2 for 61652@debbugs.gnu.org; Tue, 21 Feb 2023 08:08:45 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pUSNr-0003bA-0W; Tue, 21 Feb 2023 08:08:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=P06NEZFt1pCrI59o4j4Zj9MO8NonkLQx0ccD6YTSU9A=; b=DORmAs336rFF lnq5ME902DTu51ScXBiXeikmIuq2sajnBqfx99TbGPYMccC/HnWlvTLUtvseaEqbE2BGfjAnPaNts jbXYCXc82VT2YVmgdbmX+m2SpTxt5mQHw+s8ExLRte7Fv9dq7KKjsikQnwGqsY9luOH3A0d+cjvH/ q7m9Di6er/lG2v7LxAmG0vRGua3Tzn2olP5CZcmmt/IUCZ45PDyuI/E6iRDzP4mi081mOiQiXlj7t lTvyEJ5E6G2vpEpaL5cQHrLWtfMsipP9s99x+1nikQ6nOPfD4oZdpBFW2yaWIENY1F9nZd5Xg3cZz yaY/bUSy7phQLYiokW1Wmw==; Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pUSNq-0007iy-6W; Tue, 21 Feb 2023 08:08:38 -0500 Date: Tue, 21 Feb 2023 15:08:49 +0200 Message-Id: <83a617tbby.fsf@gnu.org> From: Eli Zaretskii To: Bernd Rellermeyer In-Reply-To: <3C58A00D-8E01-4CC8-BFEA-CCC6CB798B35@t-online.de> (message from Bernd Rellermeyer on Tue, 21 Feb 2023 13:46:50 +0100) Subject: Re: bug#61652: 28.2; Read-only mode and View mode References: <83bklov1ny.fsf@gnu.org> <3C58A00D-8E01-4CC8-BFEA-CCC6CB798B35@t-online.de> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 61652 Cc: 61652@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Bernd Rellermeyer > 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? From debbugs-submit-bounces@debbugs.gnu.org Tue Feb 21 08:37:19 2023 Received: (at 61652) by debbugs.gnu.org; 21 Feb 2023 13:37:19 +0000 Received: from localhost ([127.0.0.1]:55021 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pUSpa-00054Y-D2 for submit@debbugs.gnu.org; Tue, 21 Feb 2023 08:37:19 -0500 Received: from mailout10.t-online.de ([194.25.134.21]:36108) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pUS2x-0002ht-3Z for 61652@debbugs.gnu.org; Tue, 21 Feb 2023 07:47:04 -0500 Received: from fwd88.dcpf.telekom.de (fwd88.aul.t-online.de [10.223.144.114]) by mailout10.t-online.de (Postfix) with SMTP id 78C003E0B6; Tue, 21 Feb 2023 13:47:01 +0100 (CET) Received: from smtpclient.apple ([62.216.210.159]) by fwd88.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1pUS2v-0Xydg90; Tue, 21 Feb 2023 13:47:01 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) Subject: Re: bug#61652: 28.2; Read-only mode and View mode From: Bernd Rellermeyer In-Reply-To: <83bklov1ny.fsf@gnu.org> Date: Tue, 21 Feb 2023 13:46:50 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <3C58A00D-8E01-4CC8-BFEA-CCC6CB798B35@t-online.de> References: <83bklov1ny.fsf@gnu.org> To: Eli Zaretskii X-Mailer: Apple Mail (2.3731.400.51.1.1) X-TOI-EXPURGATEID: 150726::1676983621-726BD7D8-7C9B7B2A/0/0 CLEAN NORMAL X-TOI-MSGID: 08b201bc-19d3-4a44-917c-8ff33ed1f1c1 X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 61652 X-Mailman-Approved-At: Tue, 21 Feb 2023 08:37:15 -0500 Cc: 61652@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) In step 3, View mode is entered implicitly, because `view-read-only` is = non-nil. =46rom 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? > Am 20.02.2023 um 15:42 schrieb Eli Zaretskii : >=20 >> From: Bernd Rellermeyer >> Date: Mon, 20 Feb 2023 09:41:33 +0100 >>=20 >>=20 >> I have the following scenario: >>=20 >> 1. View a buffer in View mode. >> 2. Turn off Read-Only mode, e.g. by pressing `C-x C-q`. >> 3. Turn on Read-Only mode and View mode again, eg. by pressing `C-x >> C-q`- >> 4. Exit View mode by `View-exit`, e.g. by pressing `e`. >>=20 >> Now the buffer is in Read-Only mode. In my opinion it should be >> writable. The reason is the variable `view-old-buffer-read-only`, = which >> is set on entering View mode (`view--enable`) to the (old) value of >> `buffer-read-only`. But in my scenario, the value of = `buffer-read-only` >> is already the new one, as set in `read-only-mode`. >=20 > If the buffer is already read-only when you enter View mode, why > should we reset read-only when exiting View mode? We are trying to > leave the buffer as we found it, which in this case is read-only. >=20 > Or what am I missing? From debbugs-submit-bounces@debbugs.gnu.org Tue Sep 05 19:48:17 2023 Received: (at 61652) by debbugs.gnu.org; 5 Sep 2023 23:48:17 +0000 Received: from localhost ([127.0.0.1]:59858 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qdfmI-0005K0-7Q for submit@debbugs.gnu.org; Tue, 05 Sep 2023 19:48:17 -0400 Received: from mail-lf1-x130.google.com ([2a00:1450:4864:20::130]:46497) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qdfmD-0005Jg-Mi for 61652@debbugs.gnu.org; Tue, 05 Sep 2023 19:48:13 -0400 Received: by mail-lf1-x130.google.com with SMTP id 2adb3069b0e04-500c7796d8eso4926022e87.1 for <61652@debbugs.gnu.org>; Tue, 05 Sep 2023 16:48:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693957683; x=1694562483; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=SDJ9HrUUZbLA9fkSassC2FT6glo938FmkYgjs0ofpSc=; b=JVWt2beUTSlgdfIABnRG9CWkqX3EW+HHUCBq0BaoGmAfNjeexpkS01oAx80jxWm1ls IGuC/9yv/JWRr/7jegjv2jcqXrx3/GFP2r1+77WkQlHIPoWl39PohDG1izFO5//06IeT KB2jNi/JtAoWp/jhv+vdedjM09C0gXZOPlSIxBa+RWoAfrhgnepmyyVnj1jWRSHxwzBA kmUMHQckx0v4kQp65YqvEJEbhBTO090zjr9tc5JoENUgw/e25ePlXqjd07vPabF6k8ZK TWX3NAY7RRt+N2pWl9HpgK8EtoDN7bvCLotGtIyjm6Hk0+QlMcT/0i8eXM14YdLCOZ9B D94Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693957683; x=1694562483; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=SDJ9HrUUZbLA9fkSassC2FT6glo938FmkYgjs0ofpSc=; b=gnPLKJkvJ4qm3sBN83+S8wOpkinIQAi63gv9cmSgtcUL2AGryYMVrUoVWkxYO1btsw OnrFqLAdDAp0NJZDrR2r57U43Fv9SmvtIsxQyKcyYyk8CcwocG6+aCsnE422Z4O1vT5A k7dwKdPyp9HKAPKIpbzwozrOvRMwlEJqwx2REacUImbKRp5XuicFn0mWxys6wmiD4JQ3 sf+ahoZogUDbS212Az2Gus7hVbLK8hfOMQCOU1IuvTFQIbdwe32KUHYIWV3e+xYhh0Aa BfE8ePL1P5m5vYVXbCQQT/vNCJqoEQSReC3oZu3kWU65CHhwIMUrZjUhktdJvn/t9K9n AhoQ== X-Gm-Message-State: AOJu0YzV6GOIn9nVsMxr5iYVbpOke/PpzTGKFzRRSX2vRZWW45mBe6kH jk+FvAtzLVWpm9Ai7Ji8M2UH03V51KDskSaRBoM= X-Google-Smtp-Source: AGHT+IFiAMBlMsOod5MwK0hkH4JzYFjpxDcc+bWRFZMW6hMnxHnltQQzC9nrDKBP1gHfHoCQDTXlBFtxJF4Zx6EInK0= X-Received: by 2002:a19:6555:0:b0:4fb:7559:aea3 with SMTP id c21-20020a196555000000b004fb7559aea3mr766225lfj.39.1693957682776; Tue, 05 Sep 2023 16:48:02 -0700 (PDT) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Tue, 5 Sep 2023 16:48:02 -0700 From: Stefan Kangas In-Reply-To: <83a617tbby.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 21 Feb 2023 15:08:49 +0200") References: <83bklov1ny.fsf@gnu.org> <3C58A00D-8E01-4CC8-BFEA-CCC6CB798B35@t-online.de> <83a617tbby.fsf@gnu.org> MIME-Version: 1.0 Date: Tue, 5 Sep 2023 16:48:02 -0700 Message-ID: Subject: Re: bug#61652: 28.2; Read-only mode and View mode To: Eli Zaretskii Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 61652 Cc: Bernd Rellermeyer , 61652@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Eli Zaretskii writes: >> From: Bernd Rellermeyer >> 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. From debbugs-submit-bounces@debbugs.gnu.org Wed Sep 06 07:32:54 2023 Received: (at 61652) by debbugs.gnu.org; 6 Sep 2023 11:32:54 +0000 Received: from localhost ([127.0.0.1]:33189 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qdqmE-0001IC-91 for submit@debbugs.gnu.org; Wed, 06 Sep 2023 07:32:54 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:37756) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qdqmC-0001I0-I8 for 61652@debbugs.gnu.org; Wed, 06 Sep 2023 07:32:52 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qdqlx-0000VX-0X; Wed, 06 Sep 2023 07:32:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=uGmZEFd/+Ff84uSBxSDHipENkimZRHK48r6UBLgyX4U=; b=BdXGYS0Q5Zi5 NT1ZGoFU9DcoJVBBwWq/R89Im8O50r7Yk6aDd2TaYmQhyzKnlcpiZ/1yFNleCcjS1AgR+yzFTC6mo OpZBkAK9RxtSNYJFhuTL6FmiJhUy9yv217IwfW64HQ/xpaTXFaGv9avBgDNJboGzMGgFmoP2A/hfr 9/995A8ksfDVZyCkpW3Lh/JwRK41cikSSTykdEPzptwEoi19ItGYlT9qWlzbInqZREjEZYnMhO83s 8a72R9ciLXKvHizZSKDJ6/WkvD173smEW51wtyNhDqK1YMbLWoGMVdduLtLAgJn6FGX7Tr/V1UFcN Gri9WWl/pSZVCVyGi4Cknw==; Date: Wed, 06 Sep 2023 14:32:18 +0300 Message-Id: <83il8n35bx.fsf@gnu.org> From: Eli Zaretskii To: Stefan Kangas In-Reply-To: (message from Stefan Kangas on Tue, 5 Sep 2023 16:48:02 -0700) Subject: Re: bug#61652: 28.2; Read-only mode and View mode References: <83bklov1ny.fsf@gnu.org> <3C58A00D-8E01-4CC8-BFEA-CCC6CB798B35@t-online.de> <83a617tbby.fsf@gnu.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 61652 Cc: bernd.rellermeyer@t-online.de, 61652@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Stefan Kangas > Date: Tue, 5 Sep 2023 16:48:02 -0700 > Cc: Bernd Rellermeyer , 61652@debbugs.gnu.org > > Eli Zaretskii writes: > > >> From: Bernd Rellermeyer > >> 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. Since no one has chimed in during all this time, I think we should leave this alone. From debbugs-submit-bounces@debbugs.gnu.org Wed Sep 06 08:08:32 2023 Received: (at 61652) by debbugs.gnu.org; 6 Sep 2023 12:08:32 +0000 Received: from localhost ([127.0.0.1]:33257 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qdrKh-0004xJ-UT for submit@debbugs.gnu.org; Wed, 06 Sep 2023 08:08:32 -0400 Received: from mail-lf1-x12a.google.com ([2a00:1450:4864:20::12a]:52550) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qdrKf-0004wt-R5 for 61652@debbugs.gnu.org; Wed, 06 Sep 2023 08:08:30 -0400 Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-501bd6f7d11so2980625e87.1 for <61652@debbugs.gnu.org>; Wed, 06 Sep 2023 05:08:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694002103; x=1694606903; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=+CvV4LiK7yOioR4ikDiOzO2grd4rIBVT0MGmFxwM+xE=; b=oXV27BdZW+FpVTqbmzc/zyAbgzsfhXAa7JopZqsbgdzuBKaPbkc3I6InrTKYwXGpXZ lvmAIN2SskIgkZQCq8chUG4o67RetuAuEJcUA9zfz/pxfJuV4OPO8jjfBg5TX7/iFzfB 8HCMu8J2M0c4zTGuaba5FPCwIT5oYy+nbbS8rCH78POTZV9ykKvUsAPga0zbYVX1pvky g8gxG5tPxY6lAaNvfE1n2H5gK6xQ9mgvbe01jI/CQK4nnK0vX31SB/GPlA/TygNUsy3Y XvkKsGEEnU9+FjvI6AksAnC40HFi5wmEoRNNeR8DiIx4bZfdeekIO3wBLuDfQCGGgcxN geXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1694002103; x=1694606903; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=+CvV4LiK7yOioR4ikDiOzO2grd4rIBVT0MGmFxwM+xE=; b=D8yCOqpFnDWjz1hA/DSpNeZFgaI5xIYE+dDdrGrLew424ZbPwfaYqBnC7HItriyOKL B+WyI/iQwy/L+FCFXYDq8FJmDXfW7Tipa/jk3LuI+UuxhOVx0e6nJSMaELjufeFK6Pay L3zT4RX+Ny+1i8W/hz13wDGWT6pg+SjiOjGEbHrIvJmWOXHW8AbyK/JwnG6UKMlNGKBn k5lYC6xqIX9O+Bo1yghEWTgADwKFgZupxAav1p23f/MTpeGhZluBLg6So7My97CWzWkW HN3fwOMwWWwgqKGpRL+izyegZRxkvYALXSZtuqWYC0wTHlS8kCwNzL8cbHEYpsyyl8br oI7A== X-Gm-Message-State: AOJu0YxacZoIYCDqfABHjhNidSQ0de/FKhxYnDcLwv0kGG2t23j/GOcW +IndswiOD4YQMWROgl+MZDq/HJacpdTSWgC4ll0= X-Google-Smtp-Source: AGHT+IGsSajHn5mbOKlCc/gzKrpPTv6N6gHArLXUjr1JUsNjdDO59Wh5S8YkX1j53hMu8UXWg/Tp2HFUY9qG8+Ebrzw= X-Received: by 2002:ac2:4e8b:0:b0:500:77c4:108 with SMTP id o11-20020ac24e8b000000b0050077c40108mr1839526lfr.9.1694002102747; Wed, 06 Sep 2023 05:08:22 -0700 (PDT) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Wed, 6 Sep 2023 05:08:22 -0700 From: Stefan Kangas In-Reply-To: <83il8n35bx.fsf@gnu.org> References: <83bklov1ny.fsf@gnu.org> <3C58A00D-8E01-4CC8-BFEA-CCC6CB798B35@t-online.de> <83a617tbby.fsf@gnu.org> <83il8n35bx.fsf@gnu.org> MIME-Version: 1.0 Date: Wed, 6 Sep 2023 05:08:22 -0700 Message-ID: Subject: Re: bug#61652: 28.2; Read-only mode and View mode To: Eli Zaretskii Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 61652 Cc: bernd.rellermeyer@t-online.de, 61652@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) tags 61652 wontfix notabug close 61652 thanks Eli Zaretskii writes: > Since no one has chimed in during all this time, I think we should > leave this alone. Agreed, closing. From unknown Mon Jun 23 04:10:47 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Thu, 05 Oct 2023 11:24:09 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator