unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: "Nicolas Goaziou" <mail@nicolasgoaziou.fr>,
	"Ludovic Courtès" <ludo@gnu.org>,
	31056@debbugs.gnu.org
Subject: [bug#31056] [PATCH] gnu: emacs-org: fix byte compilation
Date: Sun, 08 Apr 2018 12:13:50 +0200	[thread overview]
Message-ID: <m1d0zam2e9.fsf@ordinateur-de-catherine--konrad.home> (raw)
In-Reply-To: <87vad54yz2.fsf@nicolasgoaziou.fr>

Hi Nicolas,

Thanks for your comments!

> IMO, compiling a dedicated Emacs only for Org seems a bit overkill.

True, but then most users will get emacs-org as a substitute, so the
main impact is on the build farms.

> I'd rather have it fixed upstream than papering over the problem.

The problem has been around for years, so I have given up hope for an
upstream fix. Emacs 26 will include org-mode 9, so the problem will go
away when release 26 becomes official. I doubt anyone will work on a fix
in the meantime.

Concerning Guix, the question is if we care about fixing the bug before
switching to Emacs 26.  The number of users concerned may be small (it's
only org-babel that is affected, not the more widely used PIM
functionality of org-mode), but for those users it's a show-stopper.  If
I invested much time into this patch, it's because I cannot work without
it.

Konrad.

  reply	other threads:[~2018-04-08 10:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 16:08 [bug#31056] [PATCH] gnu: emacs-org: fix byte compilation Konrad Hinsen
2018-04-04 12:15 ` Ludovic Courtès
2018-04-05 12:30   ` Nicolas Goaziou
2018-04-08 10:13     ` Konrad Hinsen [this message]
2018-04-08 12:49       ` Nicolas Goaziou
2018-04-08 15:49         ` Konrad Hinsen
2018-05-13 20:36           ` Ludovic Courtès
2018-06-05  9:59             ` Konrad Hinsen
2018-06-05 10:14               ` Nicolas Goaziou
2018-06-08 14:44                 ` bug#31056: " Ludovic Courtès

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=m1d0zam2e9.fsf@ordinateur-de-catherine--konrad.home \
    --to=konrad.hinsen@fastmail.net \
    --cc=31056@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).