From: Heime 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: uzibalqa@proton.me, stefankangas@gmail.com, 65913@debbugs.gnu.org
Subject: bug#65913: with-help-window arranges for 'inhibit-read-only' to be set to 't'
Date: Thu, 14 Sep 2023 13:17:43 +0000 [thread overview]
Message-ID: <W4v75bDDj0EDuJfSdzxej3VOGBQaCfaDqx16NQ2OOzcn6celIBT1aebmn_s1TQZVEywKtLajKH0MFoT0hPxJnDBuK-JIfFT-cjGEqqhiBLM=@protonmail.com> (raw)
In-Reply-To: <83y1h8lxzu.fsf@gnu.org>
------- Original Message -------
On Friday, September 15th, 2023 at 12:50 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Thu, 14 Sep 2023 10:41:06 +0000
> > From: Heime heimeborgia@protonmail.com
> > Cc: uzibalqa uzibalqa@proton.me, 65913@debbugs.gnu.org, stefankangas@gmail.com
> >
> > > So do we. But this issue has nothing to do with how hard it is to
> > > work with Emacs. You simply looked for the information you were after
> > > in the wrong place, when the right place should have been pretty
> > > obvious for someone who writes Lisp programs: the ELisp manual.
> >
> > Stefan mentioned a project to have the docstring communicate with the manual
> > so that finding the information will not be too laborious.
>
>
> That's an existing feature, we use it when appropriate.
>
> > > In general, there's no need to mention in each and every doc string
> > > that to learn about some subject you should read the manual where that
> > > subject is described. This is trivial, and having to repeat that
> > > everywhere will just bloat Emacs for no good reason. Consulting the
> > > documentation is one of the first lessons that each Emacs user learns,
> > > and resisting that lesson is not recommended.
> >
> > There could be some manual or metadata that could provide rapid search
> > and association capabilities to find relevant information and avoid much
> > manual labour.
>
> We have commands for that: "M-x apropos", Info-index, and others.
Many thanks, shall look into this and see how far that gets me.
next prev parent reply other threads:[~2023-09-14 13:17 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 [this message]
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='W4v75bDDj0EDuJfSdzxej3VOGBQaCfaDqx16NQ2OOzcn6celIBT1aebmn_s1TQZVEywKtLajKH0MFoT0hPxJnDBuK-JIfFT-cjGEqqhiBLM=@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 \
--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 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.