all messages for Emacs-related lists mirrored at yhetil.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: Sat, 16 Mar 2024 09:16:37 +0200	[thread overview]
Message-ID: <86r0ga7iju.fsf@gnu.org> (raw)
In-Reply-To: <87frwrxnqr.fsf@secretsauce.net> (message from Dima Kogan on Fri,  15 Mar 2024 13:07:40 -0700)

> From: Dima Kogan <dima@secretsauce.net>
> Date: Fri, 15 Mar 2024 13:07:40 -0700
> 
> Hi. Here's a recipe:
> 
> 1. emacs -Q
> 
> 2. M-x shell
> 
> 3. Observe that the shell is live. You can run commands, and the
>    inferior process responds
> 
> 4. C-x C-q
> 
>    Turns on read-only-mode
> 
> 5. Observe that we now cannot interact with the shell since it's
>    read-only. We can C-x C-q again to make it work again. Before step 6,
>    C-x C-q again, to make it read-only
> 
> 6. C-d
> 
>    This normally exits the shell. But if we're read-only, it shouldn't
>    do that. I see that it still works, despite being read-only.

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.





  reply	other threads:[~2024-03-16  7:16 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 [this message]
2024-03-17 19:51   ` Dima Kogan
2024-03-17 20:22     ` Eli Zaretskii
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

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

  git send-email \
    --in-reply-to=86r0ga7iju.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 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.