From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: Pierre Neidhardt <mail@ambrevar.xyz>,
dario <dario.klingenberg@web.de>,
39804@debbugs.gnu.org
Subject: [bug#39804] [PATCH] gnu: add emacs-exwm-next package (i.e. exwm for emacs-next)
Date: Tue, 10 Mar 2020 23:54:54 -0400 [thread overview]
Message-ID: <87zhcn35rl.fsf@gmail.com> (raw)
In-Reply-To: <87d09ukwnn.fsf@gmail.com> (Maxim Cournoyer's message of "Mon, 02 Mar 2020 21:19:24 -0500")
Hello Leo,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Leo Prikler <leo.prikler@student.tugraz.at> writes:
>
>> Am Freitag, den 28.02.2020, 09:32 +0100 schrieb Pierre Neidhardt:
>>> The `#:emacs` field tells the build system which Emacs package to use
>>> to
>>> build this package. There may be something that not compatible
>>> between
>>> our current build system and emacs-next.
>>>
>>> I've CC'ed Maxim and Leo, they might know more than me.
>> This issue should be addressed by #39375, which is currently waiting to
>> be pushed to master or staging.
>
> If we don't hear back from
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39823 in a day or two, I'd
> be OK with pushing #39375 to master.
There have been no activity or reply on #39823 yet, so feel free to push
the workaround discussed earlier (on the master branch is fine).
Maxim
next prev parent reply other threads:[~2020-03-11 3:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 21:07 [bug#39804] [PATCH] gnu: add emacs-exwm-next package (i.e. exwm for emacs-next) dakling
2020-02-27 9:53 ` Pierre Neidhardt
2020-02-27 22:04 ` dario
2020-02-28 8:32 ` Pierre Neidhardt
2020-02-28 9:53 ` Leo Prikler
2020-02-28 14:45 ` Maxim Cournoyer
2020-03-03 2:19 ` Maxim Cournoyer
2020-03-11 3:54 ` Maxim Cournoyer [this message]
2020-03-15 13:48 ` Leo Prikler
2020-03-17 1:59 ` Maxim Cournoyer
2020-03-23 1:52 ` Maxim Cournoyer
2020-03-23 8:57 ` Pierre Neidhardt
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhcn35rl.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=39804@debbugs.gnu.org \
--cc=dario.klingenberg@web.de \
--cc=leo.prikler@student.tugraz.at \
--cc=mail@ambrevar.xyz \
/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/guix.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).