From: Jean Louis <bugs@gnu.support>
To: Joel Reicher <joel.reicher@gmail.com>
Cc: emacs-tangents@gnu.org
Subject: Re: [External] : Exiting from mapc
Date: Fri, 3 Jan 2025 10:49:09 +0300 [thread overview]
Message-ID: <Z3eWdeVwRl2XgaIi@lco2> (raw)
In-Reply-To: <867c7cagpd.fsf@gmail.com>
* Joel Reicher <joel.reicher@gmail.com> [2025-01-03 03:25]:
> Jean Louis <bugs@gnu.support> writes:
>
> > * Joel Reicher <joel.reicher@gmail.com> [2025-01-02 03:33]:
> > > Heime via Users list for the GNU Emacs text editor
> > > <help-gnu-emacs@gnu.org> writes:
> > >
> > > > How can one get the result of the throw? With a let?
> > >
> > > Why are you asking on this list when it should be possible to get
> > > this information from (info "(elisp) Catch and Throw")?
> >
> > Sometimes it is helpful to provide info, and too often people have
> > misunderstanding and need explanation. Emacs is full of terms, concepts,
> > definitions which cause misunderstandings. If that would not be so, I
> > would be very happy, though it is.
> >
> > You must know that there are different types of readers, different
> > audience. Emacs Lisp manual is written in technical manner, it wasn't
> > written in manner of a tutorial.
>
> If the problem is in understanding the manual, then my very strong opinion
> is that the question should be asked in terms of the manual.
>
> This does three things:
>
> 1) Demonstrates good faith on the part of the enquirer that they have
> attempted to read the manual
> 2) Helps phrase the question in common terms with a minimum of unstated
> assumptions
> 3) Potentially leads to improvements in the manual
It is very good opinion, but people are not programmed robots.
--
Jean Louis
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
next parent reply other threads:[~2025-01-03 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7cSjmNb9wbuuXOPxnBml1e6cPaldn8EPTGZ2LZdnm-ZjIANwQBYOYq9a-nJDcaCG8QKkb09TGeUjlQ6vLFyFVzOPZfJniDINxCNXT1TW6vQ=@protonmail.com>
[not found] ` <DS7PR10MB5232E8A7953DA7FC414B7A44F30A2@DS7PR10MB5232.namprd10.prod.outlook.com>
[not found] ` <jRyI_Qbdrh3o3zgnhZJwzV6mef3kjs7H3bXI7__dAc7Rvv8pEc_iBILjla9vaSAmDEcQGgNUdVmP63roQBzlPR7ETJJaEKI2G88YrJic53o=@protonmail.com>
[not found] ` <BLAPR10MB5219799D1F5207C3D060B4ECF30A2@BLAPR10MB5219.namprd10.prod.outlook.com>
[not found] ` <jmirkZGqJQeK8mfQWIZypEsikAsU5tRp61e2P1hNzMkrhpzmOfdgeM8xAWh3xwoN8xqJWADSFTVnHa5TPG-PuI7IWb9gKW3-6qnMi02IOt4=@protonmail.com>
[not found] ` <86seq26oox.fsf@gmail.com>
[not found] ` <Z3ZrYzjrzZ94GlHd@lco2>
[not found] ` <867c7cagpd.fsf@gmail.com>
2025-01-03 7:49 ` Jean Louis [this message]
2025-01-03 12:59 ` [External] : Exiting from mapc Van Ly via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2025-01-03 14:55 ` Jean Louis
2025-01-11 8:19 ` Joel Reicher
2025-01-11 10:35 ` Van Ly via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2025-01-11 12:19 ` Eduardo Ochs
2025-01-11 8:17 ` Joel Reicher
2025-01-11 8:14 ` Joel Reicher
2025-01-11 9:14 ` was - " Jean Louis
2025-01-11 13:42 ` Joel Reicher
2025-01-11 14:02 ` Jean Louis
2025-01-11 14:15 ` Joel Reicher
2025-01-11 14:37 ` Jean Louis
2025-01-12 8:46 ` Joel Reicher
2025-01-12 9:24 ` Jean Louis
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=Z3eWdeVwRl2XgaIi@lco2 \
--to=bugs@gnu.support \
--cc=emacs-tangents@gnu.org \
--cc=joel.reicher@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.
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).