unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dima Kogan <dima@secretsauce.net>
Cc: 69819@debbugs.gnu.org
Subject: bug#69819: 30.0.50; comint-mode does not always respect the read-only flag
Date: Sun, 17 Mar 2024 22:22:56 +0200	[thread overview]
Message-ID: <86v85k4nhb.fsf@gnu.org> (raw)
In-Reply-To: <874jd4y6fq.fsf@secretsauce.net> (message from Dima Kogan on Sun,  17 Mar 2024 12:51:20 -0700)

> From: Dima Kogan <dima@secretsauce.net>
> Cc: 69819@debbugs.gnu.org
> Date: Sun, 17 Mar 2024 12:51:20 -0700
> 
> > 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.

What expectation, exactly?  The buffer is not changed; the process is
terminated, but that's not the same as changing the process's buffer!





  reply	other threads:[~2024-03-17 20:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 20:07 bug#69819: 30.0.50; comint-mode does not always respect the read-only flag Dima Kogan
2024-03-16  7:16 ` Eli Zaretskii
2024-03-17 19:51   ` Dima Kogan
2024-03-17 20:22     ` Eli Zaretskii [this message]
2024-03-18  4:57       ` Dima Kogan
2024-03-18 13:16         ` Eli Zaretskii

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=86v85k4nhb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69819@debbugs.gnu.org \
    --cc=dima@secretsauce.net \
    /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).