From: Sam Steingold <sds@gnu.org>
To: emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Org mode update breaking build?
Date: Wed, 10 May 2023 14:12:59 -0400 [thread overview]
Message-ID: <871qjoawd0.fsf@gnu.org> (raw)
In-Reply-To: <83jzxh9vcw.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 09 May 2023 22:07:43 +0300")
> * Eli Zaretskii <ryvm@tah.bet> [2023-05-09 22:07:43 +0300]:
>
> The general idea is simple, indeed, but there are rocks under the
> surface.
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62762#206
> for the description of some of them.
Sigh.
I guess there is a reason why most Lisp software is build using
Lisp-based build systems (defsystem, asdf &c)
--
Sam Steingold (https://aphar.dreamwidth.org/) on Pop 22.04 (jammy) X 11.0.12101004
https://lastingimpactpsychology.com https://steingoldpsychology.com
https://fairforall.org https://www.peaceandtolerance.org/ https://camera.org
Software is like sex: it's better when it's free.
next prev parent reply other threads:[~2023-05-10 18:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 15:26 Org mode update breaking build? Tobias Bading
2023-05-03 15:55 ` Alan Mackenzie
2023-05-03 16:11 ` Tobias Bading
2023-05-03 16:58 ` Eli Zaretskii
2023-05-03 17:02 ` Tobias Bading
2023-05-04 4:42 ` Po Lu
2023-05-04 5:48 ` Eli Zaretskii
2023-05-09 16:34 ` Sam Steingold
2023-05-09 16:47 ` Eli Zaretskii
2023-05-09 17:17 ` Sam Steingold
2023-05-09 19:07 ` Eli Zaretskii
2023-05-10 18:12 ` Sam Steingold [this message]
2023-05-08 12:00 ` Madhu
2023-05-08 13:22 ` Eli Zaretskii
2023-05-14 5:49 ` Madhu
2023-05-14 5:59 ` Eli Zaretskii
2023-05-03 16:04 ` Eli Zaretskii
2023-05-03 16:07 ` Tobias Bading
2023-05-03 16:57 ` Eli Zaretskii
2023-05-03 18:56 ` John ff
2023-05-03 19:02 ` Tassilo Horn
2023-05-04 2:00 ` Michael Heerdegen
2023-05-04 3:23 ` Bob Rogers
2023-05-04 3:30 ` Michael Heerdegen
2023-05-04 3:44 ` Bob Rogers
2023-05-04 5:42 ` Eli Zaretskii
2023-05-04 5:58 ` Bob Rogers
2023-05-04 5:41 ` Eli Zaretskii
2023-05-04 5:13 ` Eli Zaretskii
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=871qjoawd0.fsf@gnu.org \
--to=sds@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.