From: Po Lu <luangruo@yahoo.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Philip Kaludercic <philipk@posteo.net>,
Visuwesh <visuweshm@gmail.com>, "T.V Raman" <raman@google.com>,
emacs-devel@gnu.org
Subject: Re: man broken?
Date: Sun, 07 Jan 2024 20:02:00 +0800 [thread overview]
Message-ID: <87bk9x73nr.fsf@yahoo.com> (raw)
In-Reply-To: <874jfpfjp1.fsf@gmx.de> (Michael Albinus's message of "Sun, 07 Jan 2024 12:48:26 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
> Finally, I found the culprit. connection-local-value didn't handle a
> local default directory properly.
>
> Fix pushed to master. Again, since this is a macro, you need to
> recompile at least files-x.el and man.el (in this order). Or you run
> 'make bootstrap'.
>
> Best regrds, Michael.
Should the body of this macro be extracted into a separate function, so
that future changes affecting it won't require a recompilation of all
files where it is invoked? I've seen two breaking changes with this
macro involved in some capacity over the past 30 days, which is abnormal
for such a widely used macro.
next prev parent reply other threads:[~2024-01-07 12:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 18:28 man broken? T.V Raman
2023-12-27 18:56 ` Michael Albinus
2023-12-28 9:48 ` Philip Kaludercic
2023-12-28 15:00 ` Emanuel Berg
2023-12-28 15:13 ` T.V Raman
2023-12-28 16:22 ` Michael Albinus
2023-12-29 19:38 ` Philip Kaludercic
2023-12-30 0:31 ` Emanuel Berg
2023-12-30 4:55 ` Visuwesh
2023-12-30 11:37 ` Michael Albinus
2024-01-03 15:45 ` Philip Kaludercic
2024-01-03 15:48 ` Philip Kaludercic
2024-01-07 11:48 ` Michael Albinus
2024-01-07 12:02 ` Po Lu [this message]
2024-01-07 12:13 ` Michael Albinus
2024-01-07 12:54 ` Po Lu
2024-01-07 22:38 ` Emanuel Berg
2023-12-27 18:57 ` Eli Zaretskii
2023-12-27 19:05 ` Michael Albinus
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=87bk9x73nr.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=philipk@posteo.net \
--cc=raman@google.com \
--cc=visuweshm@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.