From: Corwin Brust <corwin@bru.st>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43844@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#43844: 27.1; Mouse-3 avoid "Buffer is read-only" *patch*
Date: Fri, 29 Jan 2021 09:10:04 -0600 [thread overview]
Message-ID: <CAJf-WoSXxbN11C5NiT4+KqggzcnkLUPKonPsGORZJui0e5WH2g@mail.gmail.com> (raw)
In-Reply-To: <87czxoxrml.fsf@gnus.org>
Thanks again Lars.
On Thu, Jan 28, 2021 at 11:02 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Corwin Brust <corwin@bru.st> writes:
>
> > Should it be the users responsibility to set this variable (in some
> > hook? which?) for any buffers that default to read-only?
>
> Yes. Some buffers have read-only text, and killing that text will
> signal an error (by design), whether you kill the text using the mouse
> or with `C-w'. If the user wants to be able to kill the text, then the
> user should set that variable.
Would you recommend packages such as ERC (or dired?) that essentially
create only read-only buffers to set this such that unconfigured
defaults don't lead to a user-error?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
Regards,
Corwin
next prev parent reply other threads:[~2021-01-29 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 11:34 bug#43844: 27.1; Mouse-3 avoid "Buffer is read-only" *patch* Corwin Brust
2020-10-07 15:14 ` Noam Postavsky
2021-01-27 5:37 ` Lars Ingebrigtsen
2021-01-28 20:20 ` Corwin Brust
2021-01-29 5:02 ` Lars Ingebrigtsen
2021-01-29 15:10 ` Corwin Brust [this message]
2021-01-30 6:14 ` Lars Ingebrigtsen
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=CAJf-WoSXxbN11C5NiT4+KqggzcnkLUPKonPsGORZJui0e5WH2g@mail.gmail.com \
--to=corwin@bru.st \
--cc=43844@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.com \
/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.