From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65913@debbugs.gnu.org, Heime <heimeborgia@protonmail.com>,
stefankangas@gmail.com
Subject: bug#65913: with-help-window arranges for 'inhibit-read-only' to be set to 't'
Date: Wed, 13 Sep 2023 19:16:52 +0000 [thread overview]
Message-ID: <CNeJlFQpoczT37z5upMBy9LG9VXTcs_NooNk12Kw6fx0jrmoYV0zpOoRaezNW0_uMYHfiRccrEtCybXVZIqg2oUro8cSRqAZvz33yOSh7c8=@proton.me> (raw)
In-Reply-To: <83o7i5nbeq.fsf@gnu.org>
------- Original Message -------
On Thursday, September 14th, 2023 at 7:03 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > 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.
The purpose of the docstring should be expanded. And if using the manual
is required, please provide that information from the self documentation.
I disagree with the notion that working with emacs should be hard. With
most people I communicate with, it is generally agreed that using the
language is hard. It is the solution that I disagree with. Because the
solution that I am usually given is to endure the time it takes for everyone
to learn it.
next prev parent reply other threads:[~2023-09-13 19:16 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 [this message]
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='CNeJlFQpoczT37z5upMBy9LG9VXTcs_NooNk12Kw6fx0jrmoYV0zpOoRaezNW0_uMYHfiRccrEtCybXVZIqg2oUro8cSRqAZvz33yOSh7c8=@proton.me' \
--to=bug-gnu-emacs@gnu.org \
--cc=65913@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=heimeborgia@protonmail.com \
--cc=stefankangas@gmail.com \
--cc=uzibalqa@proton.me \
/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).