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 16:56:30 +0300 [thread overview]
Message-ID: <834jjynpm9.fsf@gnu.org> (raw)
In-Reply-To: <_hKt5j_6bUwtEyWyE-e6GenkfdjfDll8AAVkejgxh3gyiYkvovpnhPNs1-ijjzyQaXlAJNSKb917yFQKrejO0q4tTql2vw0iu35n-JbUl8w=@protonmail.com> (message from Heime on Wed, 13 Sep 2023 13:26:51 +0000)
> Date: Wed, 13 Sep 2023 13:26:51 +0000
> From: Heime <heimeborgia@protonmail.com>
> Cc: Stefan Kangas <stefankangas@gmail.com>, 65913@debbugs.gnu.org
>
> Docstrings have become so short at times that reading them is of no practical
> use.
Only because you think everything can be learned from scratch by
reading only some more or less random doc strings. That's not how
programming in Emacs Lisp should be learned. There's a large Emacs
Lisp Reference manual, which has a separate section named "Read-Only
Buffers". If you read it when you started working with read-only
buffers, you'd have found the inhibit-read-only variable described
there.
Our recommendation is to read the relevant parts of the ELisp manual
whenever you need for the first time work with a specific aspect of
Emacs Lisp.
next prev parent reply other threads:[~2023-09-13 13:56 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 [this message]
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
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=834jjynpm9.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 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.