unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 14:51:30 +0000	[thread overview]
Message-ID: <04_YeulwxttSgx-ucr-VfmWTxKH81JSzyGT-sOTCmIoygmC3J7tNUFEY6pzA1O53iwhjtDqN88gX6pkBNR7e7b_kCefsrYMoIGPKJKt99rM=@protonmail.com> (raw)
In-Reply-To: <CADwFkm=-i3hhoS2xf-CGVS7FjkXG3D2cJSKcgj3u9tjh_x=qGg@mail.gmail.com>






Sent with Proton Mail secure email.

------- Original Message -------
On Thursday, September 14th, 2023 at 2:04 AM, Stefan Kangas <stefankangas@gmail.com> wrote:


> Eli Zaretskii eliz@gnu.org writes:
> 
> > I disagree. The use of inhibit-read-only is an implementation detail
> > of with-help-window (and of many other functions in Emacs); mentioning
> > it in the doc string will IMO have no useful purpose.
> > 
> > The doc string of "C-x C-q" (read-only-mode) does mention
> > inhibit-read-only, which is I think a much more reasonable place for a
> > reference to that variable.
> > 
> > Stefan, WDYT?
> 
> 
> I tend to agree with you.

Stefan, is this to say that for you it is good that there is no way
to figure out that there is no requirement to reset buffer-read-only 
from the self documentation ?  And that it is even unnecessary to
state that the duffer is read only by going through the different 
docstrings.  Such conclusions is seriously deficient with little regard
to how much time developers waste in working with the language.





  parent reply	other threads:[~2023-09-13 14:51 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 [this message]
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

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='04_YeulwxttSgx-ucr-VfmWTxKH81JSzyGT-sOTCmIoygmC3J7tNUFEY6pzA1O53iwhjtDqN88gX6pkBNR7e7b_kCefsrYMoIGPKJKt99rM=@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).