From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stephen.berman@gmx.net, emacs-devel@gnu.org
Subject: Re: Small correction to commit ae2463796f236b8ee2cef3b5e38bffa13abd2233
Date: Sat, 7 Sep 2024 07:17:35 +0200 [thread overview]
Message-ID: <CAO48Bk-UwHHBVm3CXt=mkk4qjfbk-1Ze=st69j5tOX759nqWOQ@mail.gmail.com> (raw)
In-Reply-To: <86ikv911sl.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
I know and that may be a long task. But highlighting tricky points may
help in more than one direction:
1.- reduce frustration in people customising their Emacs (at least because
you understand what you did)
2.- encourage people to investigate more and potentially come up with a way
of getting rid of these caveats
My .2c, /PA
On Fri, 6 Sept 2024 at 13:04, Eli Zaretskii <eliz@gnu.org> wrote:
>
> I don't see a reason to make each caveat in the manual stand out.
> There are too many of them.
>
We
--
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
[-- Attachment #2: Type: text/html, Size: 1371 bytes --]
prev parent reply other threads:[~2024-09-07 5:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 7:02 Small correction to commit ae2463796f236b8ee2cef3b5e38bffa13abd2233 Pedro Andres Aranda Gutierrez
2024-09-04 12:25 ` Eli Zaretskii
2024-09-04 13:55 ` Stephen Berman
2024-09-04 15:11 ` Stephen Berman
2024-09-06 8:13 ` Pedro Andres Aranda Gutierrez
2024-09-06 11:04 ` Eli Zaretskii
2024-09-07 5:17 ` Pedro Andres Aranda Gutierrez [this message]
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='CAO48Bk-UwHHBVm3CXt=mkk4qjfbk-1Ze=st69j5tOX759nqWOQ@mail.gmail.com' \
--to=paaguti@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen.berman@gmx.net \
/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).