unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Heime <heimeborgia@protonmail.com>
Cc: 65913@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#65913: with-help-window arranges for 'inhibit-read-only' to be set to 't'
Date: Wed, 13 Sep 2023 22:03:25 +0300	[thread overview]
Message-ID: <83o7i5nbeq.fsf@gnu.org> (raw)
In-Reply-To: <VGwO3aLT6xZ2HURKYEX_GFOfphrZIL2QzV2rzflaZ6BJQLarccdg6TqjKGUleIeEWeJaz2hY-73BWj7BbNRD17HPDch4ETEtBzRIZdYnN1A=@protonmail.com> (message from Heime on Wed, 13 Sep 2023 14:54:04 +0000)

> Date: Wed, 13 Sep 2023 14:54:04 +0000
> From: Heime <heimeborgia@protonmail.com>
> Cc: Stefan Kangas <stefankangas@gmail.com>, 65913@debbugs.gnu.org
> 
> > > > Stefan, WDYT?
> > > 
> > > I tend to agree with you.
> > 
> > 
> > OK, so I'm closing this bug.
> 
> Congratulations for the disregard !  A disease that makes only the
> the opinion of maintainers relevant rather than those using it.
> A Total Disaster.

Please don't be unfair.  Your opinions were heard and considered.
They were not rejected because they are irrelevant or for any other
such reason.  We do not have to agree with everything you say,
especially after we explain why the doc string of that particular
function is not the right place to mention inhibit-read-only.  Other
doc strings, which are a better place, do mention it.





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

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=83o7i5nbeq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65913@debbugs.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).