From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 65913@debbugs.gnu.org
Subject: bug#65913: with-help-window arranges for 'inhibit-read-only' to be set to 't'
Date: Wed, 13 Sep 2023 16:24:23 +0000 [thread overview]
Message-ID: <cLzdL9yBCq7zuNITxtrfgN0IUnBZXgxuIEWEheji0RPG5g7q5SkdCSPMHZXyZrpkAu7Sbm48jVXxCIu0VfRnVB2d45ZxlThHqxZocH0dGYo=@protonmail.com> (raw)
In-Reply-To: <CADwFkmknyxsL1cQ2vWsnq5jknmkSk0WrgpWwe5_JtaVS4yXU3A@mail.gmail.com>
Sent with Proton Mail secure email.
------- Original Message -------
On Thursday, September 14th, 2023 at 3:51 AM, Stefan Kangas <stefankangas@gmail.com> wrote:
> Heime heimeborgia@protonmail.com writes:
>
> > I cannot see the harm if after the general docstring description there
> > is
> >
> > 1. A corollary on some additional things that add value from the
> > practical point oy view.
>
>
> I basically agree, but the details on how to do it have to be worked out
> in each case individually.
Right Right
> > 2. A reference to the relevant section of the manual that would be
> > important to read about.
>
>
> Agreed. See Bug#60587 where a more general feature like this is being
> worked on.
Glad to know that some of the deliberations are recognised. I usually take
the bother even at the risk of some antagonisms. Whenever you want perspective
from someone who knows too little, I am available.
prev parent reply other threads:[~2023-09-13 16:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 10:41 bug#65913: with-help-window arranges for 'inhibit-read-only' to be set to 't' Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 13:13 ` Eli Zaretskii
2023-09-13 13:26 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 13:56 ` Eli Zaretskii
2023-09-13 14:26 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 14:04 ` Stefan Kangas
2023-09-13 14:46 ` Eli Zaretskii
2023-09-13 14:54 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 15:21 ` Stefan Kangas
2023-09-13 19:03 ` Eli Zaretskii
2023-09-13 19:16 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-14 4:53 ` Eli Zaretskii
2023-09-14 10:41 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-14 12:50 ` Eli Zaretskii
2023-09-14 13:17 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-14 16:03 ` Drew Adams
2023-09-14 16:15 ` Eli Zaretskii
2023-09-14 16:40 ` Christopher Dimech
2023-09-14 16:55 ` Eli Zaretskii
2023-09-14 19:04 ` Christopher Dimech
2023-09-14 16:29 ` Christopher Dimech
2023-09-13 14:51 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 15:14 ` Stefan Kangas
2023-09-13 15:34 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 15:51 ` Stefan Kangas
2023-09-13 16:24 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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='cLzdL9yBCq7zuNITxtrfgN0IUnBZXgxuIEWEheji0RPG5g7q5SkdCSPMHZXyZrpkAu7Sbm48jVXxCIu0VfRnVB2d45ZxlThHqxZocH0dGYo=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=65913@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=heimeborgia@protonmail.com \
--cc=stefankangas@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 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).