From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: npostavs@users.sourceforge.net Newsgroups: gmane.emacs.bugs Subject: bug#22819: 25.0.91; Don't try to indent region if the buffer is read-only Date: Sat, 05 Aug 2017 08:47:37 -0400 Message-ID: <87k22i5ggm.fsf@users.sourceforge.net> References: <87vam26amc.fsf@users.sourceforge.net> <83lgmywlo4.fsf@gnu.org> <83r2wqusep.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1501937251 26060 195.159.176.226 (5 Aug 2017 12:47:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 5 Aug 2017 12:47:31 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2.50 (gnu/linux) Cc: 22819@debbugs.gnu.org, Kaushal Modi To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Aug 05 14:47:21 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ddyU8-0005u4-Jr for geb-bug-gnu-emacs@m.gmane.org; Sat, 05 Aug 2017 14:47:16 +0200 Original-Received: from localhost ([::1]:56706 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ddyUC-0002Mu-VF for geb-bug-gnu-emacs@m.gmane.org; Sat, 05 Aug 2017 08:47:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55849) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ddyU4-0002LK-3T for bug-gnu-emacs@gnu.org; Sat, 05 Aug 2017 08:47:16 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ddyTv-0003m7-1z for bug-gnu-emacs@gnu.org; Sat, 05 Aug 2017 08:47:12 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:39930) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ddyTu-0003km-Ps for bug-gnu-emacs@gnu.org; Sat, 05 Aug 2017 08:47:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ddyTu-0003pt-9p for bug-gnu-emacs@gnu.org; Sat, 05 Aug 2017 08:47:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: npostavs@users.sourceforge.net Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 05 Aug 2017 12:47:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22819 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 22819-submit@debbugs.gnu.org id=B22819.150193716614677 (code B ref 22819); Sat, 05 Aug 2017 12:47:02 +0000 Original-Received: (at 22819) by debbugs.gnu.org; 5 Aug 2017 12:46:06 +0000 Original-Received: from localhost ([127.0.0.1]:42606 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ddyT0-0003oe-14 for submit@debbugs.gnu.org; Sat, 05 Aug 2017 08:46:06 -0400 Original-Received: from mail-io0-f193.google.com ([209.85.223.193]:38511) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ddySy-0003nv-FU for 22819@debbugs.gnu.org; Sat, 05 Aug 2017 08:46:04 -0400 Original-Received: by mail-io0-f193.google.com with SMTP id o9so2637596iod.5 for <22819@debbugs.gnu.org>; Sat, 05 Aug 2017 05:46:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=vj9G17l+YRdg885nSj3Y9Itd5+Lzy88qO4J0kFQkv8E=; b=iD29q9bAYiwfllFxtXlW/kL6oaX3Whw0FF9s83qUAJxargqkg5EYd+zI7o4MTJopPy ZoHdJAm7dTM6pfC9GjoNIkdHb6MwOiP1J9RsuM8Jy+zEP7u50o9psBKmonqR/wGvvHYK aDqDIzQJaBxVKyh0ILRZ/QbzozKxp3P0Y+RyjXyymz5a6ahzI/cHAFYvm1NHN1qjfGYf H2Dod3Ae23CR9eFKciqSC0Ct11uVDcdaMC6X+I65UM2hljdI+CAtrHbdxL2i2XN1t+j5 fbKpSNnP9M4ortBhkSVKnjUBdZ+1iq7igSuADCl3rsX3UUfXOXasFXr7WII+Xv52JVVQ ay4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:references:date :in-reply-to:message-id:user-agent:mime-version; bh=vj9G17l+YRdg885nSj3Y9Itd5+Lzy88qO4J0kFQkv8E=; b=kmY0fKMCx8FWEHEZvH6H0m6cj1cq76SjidCAKRJ5+F/8K+/4aknZInI9aUqTryDjh3 06/vg8XB1ONwYU2ODlhlXaoxWnhqY80B++z2gKtl2bqnH62sOStMnnZ2EHcMKFoRgyqb UkxawwdGbmIeiINpe8mKUnq/qG59XEcrfJmRY3rGnPpzvbirp+RMKLl3orEYkIIIQLhV Ad8CYxVUp/8NaZ/7noYYcwksVFU/MZG5aKE2K4zYIc9Q/Fb7AXSXHlIrnE6uJzyXeCJ7 TjSTTEroS0lZtJl+NGLLoAVDpt03uesQq4+MAuC2I4gSlin/brjRqMHAuWJ8qf+f7kqb LZLw== X-Gm-Message-State: AHYfb5g3s0bCwM+HppHiYgonAsoglWcFPt55BtOPyBAd/E+hr8yqOCPr yj11+Kbbdb56HRMZ X-Received: by 10.107.152.197 with SMTP id a188mr5444107ioe.124.1501937158627; Sat, 05 Aug 2017 05:45:58 -0700 (PDT) Original-Received: from zony ([45.2.119.48]) by smtp.googlemail.com with ESMTPSA id y4sm1804841ita.42.2017.08.05.05.45.57 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 05 Aug 2017 05:45:57 -0700 (PDT) In-Reply-To: <83r2wqusep.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 05 Aug 2017 15:10:22 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:135422 Archived-At: Eli Zaretskii writes: >> >against veteran Emacs behavior regarding read-only text, behavior >> >that is present in several other commands, and that AFAIR resulted >> >from some past discussions. >> >> This is the only one that provided me this surprise in about a decade of Emacs use. Which other commands >> do the text manipulation, and then check the buffer read-only status? > > C-w, to name just one. That seems like a bit of a special case, as there is `kill-read-only-ok' which specifically controls this behaviour. > IOW, a command could have useful side effects that are produced even > if the buffer is read-only and its text cannot be changed, thus > preventing the main effect of the command from happening. indent-region doesn't have any side-effects though, right? There are lots of other commands which check read-only status at the beginning: M-x rgrep barf-if-buffer-read-only\|(interactive "\*