From: Gregor Zattler <telegraph@gmx.net>
To: Daniel Ortmann <daniel.ortmann@oracle.com>,
Ihor Radchenko <yantar92@gmail.com>,
Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [External] : Re: org-mode compile issue this morning - how to report this?
Date: Thu, 25 Aug 2022 22:26:01 +0200 [thread overview]
Message-ID: <87wnawt6hy.fsf@no.workgroup> (raw)
In-Reply-To: <230c1073-2f55-aae6-c98a-9da2abfc0b16@oracle.com>
Hi Daniel,
* Daniel Ortmann <daniel.ortmann@oracle.com> [2022-08-25; 09:36 -05]:
> FYI,
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57394
>
> Lars at gnu says it is fixed in emacs 29
> The bug's web page says, more specifically, "bug marked as fixed in
> version 29.1"
>
> ... I can't find emacs 29.1; my 'git pull' still says 29.0 and I don't
> see any 29.1 branches available.
> I have not been able to test and verify the fix.
it's this commit on the emacs master branch:
commit b28b2cefaea0d7846ab9a45dc92f68ad00e92085
Author: Lars Ingebrigtsen <larsi@gnus.org>
Date: Thu Aug 25 14:54:49 2022 +0200
Fix warning about obsoleted generalized variables
* lisp/emacs-lisp/bytecomp.el (byte-compile-warn-obsolete):
Autoload so that the call here from gv.el (about obsolete
generalized variables) doesn't bug out (bug#57394).
Do a git fetch --all; git pull on the emacs master branch
and you are able to test the fix. I cannot tell since my
machine is slow and still in the early stadium of building
emacs.
Ciao; Gregor
--
-... --- .-. . -.. ..--.. ...-.-
next prev parent reply other threads:[~2022-08-25 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 19:36 org-mode compile issue this morning - how to report this? Daniel Ortmann
2022-08-23 2:26 ` Ihor Radchenko
2022-08-23 6:38 ` Tim Cross
2022-08-23 7:28 ` Ihor Radchenko
2022-08-24 22:15 ` [External] : " Daniel Ortmann
2022-08-25 14:36 ` Daniel Ortmann
2022-08-25 17:37 ` Daniel Ortmann
2022-08-25 20:26 ` Gregor Zattler [this message]
2022-08-25 22:50 ` Tim Cross
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnawt6hy.fsf@no.workgroup \
--to=telegraph@gmx.net \
--cc=daniel.ortmann@oracle.com \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@gmail.com \
--cc=yantar92@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).