From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dima Kogan Newsgroups: gmane.emacs.bugs Subject: bug#69819: 30.0.50; comint-mode does not always respect the read-only flag Date: Sun, 17 Mar 2024 12:51:20 -0700 Message-ID: <874jd4y6fq.fsf@secretsauce.net> References: <87frwrxnqr.fsf@secretsauce.net> <86r0ga7iju.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30497"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.10.8; emacs 30.0.50 Cc: 69819@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Mar 17 21:02:05 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rlwhn-0007ex-0h for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 17 Mar 2024 21:02:05 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rlwhC-0008GV-N7; Sun, 17 Mar 2024 16:01:26 -0400 Original-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 1rlwhB-0008F0-6g for bug-gnu-emacs@gnu.org; Sun, 17 Mar 2024 16:01:25 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rlwhA-0002Y4-UU for bug-gnu-emacs@gnu.org; Sun, 17 Mar 2024 16:01:24 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rlwhm-0005Cr-BW for bug-gnu-emacs@gnu.org; Sun, 17 Mar 2024 16:02:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dima Kogan Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 17 Mar 2024 20:02:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 69819 X-GNU-PR-Package: emacs Original-Received: via spool by 69819-submit@debbugs.gnu.org id=B69819.171070569819933 (code B ref 69819); Sun, 17 Mar 2024 20:02:02 +0000 Original-Received: (at 69819) by debbugs.gnu.org; 17 Mar 2024 20:01:38 +0000 Original-Received: from localhost ([127.0.0.1]:38685 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rlwhO-0005BP-7H for submit@debbugs.gnu.org; Sun, 17 Mar 2024 16:01:38 -0400 Original-Received: from wfout8-smtp.messagingengine.com ([64.147.123.151]:48737) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rlwhL-0005B0-Eu for 69819@debbugs.gnu.org; Sun, 17 Mar 2024 16:01:36 -0400 Original-Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfout.west.internal (Postfix) with ESMTP id 2A4451C000B2; Sun, 17 Mar 2024 16:00:51 -0400 (EDT) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sun, 17 Mar 2024 16:00:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=secretsauce.net; h=cc:cc:content-type:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to; s=fm1; t=1710705650; x= 1710792050; bh=cqUiIFtRiFRgZlImESWU1CJVO/G0aeG9TrYI8PF6fK4=; b=F 85vP2BLP10F4TJ/L1aa6yTVl5tSYoOqp1tzDuCSxQgpAndn2rkR2E1+tL8TNYPX6 2tOFpx1PIAtJaXs65i+6k/ZxEHpGtoCkxBKKPYjA/zkNciKXgDkA4KCf5yNGsi7P jkdwYT0Vw7gGJRmGlrIFKsdOvKtKQ6uOyxyof3lYilAkSkttNPhMcBl1YsESdDjQ WPle7werSFAVS8GU5Y7jB6E8C+1bKdnUZjoAXskPIpJ1uwcUTkw8Vfx/RLfRW9DX BMV6zwuSqts8FtbEtjiD0YCiPW+Dd7rf35MyIhl8hZl4t1FceGMWTTHhZccTWSpv djQxaN/NE29oFZ9rP7MTA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1710705650; x=1710792050; bh=cqUiIFtRiFRgZlImESWU1CJVO/G0 aeG9TrYI8PF6fK4=; b=OL6S8l14obyvR1ZYGbvp82rp31C+j809z9T3LzV9MLhT uax+6OaQ8CqmqEeVYW6Vlkt1TcfGNFXtCE22JJbcFaiw4KaFOYGjs5zchTMFbfpq HdCXpsoE4bEy/awP/mDxM8TA7a9w7YjQcZVpaLSBHC+lBuXrMGImWDp5HS/PVNh8 QN4gKOFZYXraBCEp1JIOpc32L768XRxErK9/wsdz/2I/p/fNxK70eaWWivqeSHMt Vr5lwNhzgQKSrO0w2pS1oCcDNRyIrkMgx98UuGos+JziPRJewEST8CMSCvOIzjdI MrXYO8ZrIapnFoVxgyYHBO3XB6uqJQaWjKU0NLLadQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrkeehgddutdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfhgfhffvvefuffgjkfggtgesthdtredttdertdenucfhrhhomhepffhimhgr ucfmohhgrghnuceoughimhgrsehsvggtrhgvthhsrghutggvrdhnvghtqeenucggtffrrg htthgvrhhnpefgieefheegvdekkedvvedvledvgeelveetvdeujedvjeevudevueelveel veduteenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe guihhmrgesshgvtghrvghtshgruhgtvgdrnhgvth X-ME-Proxy: Feedback-ID: i3e8042a0:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 17 Mar 2024 16:00:49 -0400 (EDT) In-reply-to: <86r0ga7iju.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:281779 Archived-At: > Why do you think C-d shouldn't work when the buffer is read-only? > >> I'm observing this with all comint-based modes, not just shell-mode. > > It's a feature, AFAICT. But I'm interested in hearing why you thought > it was a bug. Is there no expectation that a "read-only" mode would block any changes to a buffer? Killing the inferior process breaks that expectation, hence this report. That said, I've been a daily user of shell-mode for something like 25 years, and encountered it for the first time just recently, so fixing this surely isn't very high priority. But still. Thanks!