From: Achim Gratz <Stromeko@Nexgo.DE>
To: emacs-orgmode@gnu.org
Subject: Re: :EXPORT_FILE_NAME: in new exporter possible?
Date: Mon, 25 Mar 2013 18:39:15 +0100 [thread overview]
Message-ID: <kiq236$vtb$1@ger.gmane.org> (raw)
In-Reply-To: <87vc8fa03f.fsf@bzg.ath.cx>
Am 25.03.2013 17:57, schrieb Bastien:
> Can you evaluate my patch against the current state of affair?
The current state of affairs is this:
1. Gnus is doing something it shouldn't do, even though it may once have
been OK or at least not dangerous.
2. Org doesn't have something that can directly be used in Gnus instead.
The first one's a bug in Gnus, not Org. The second would be an
enhancement to Org that might be useful in other places as well,
independently of the issue with Gnus.
> Evaluating it against your ideal fix will obvisouly make it look
> rudimentary. But I think it's better than the current situation.
Both solutions rely on Gnus fixing their bug, so we might just as well
wait until Gnus has done it. Depending on which way Gnus does this, we
may be talking different implementations of the second point above. But
given that Gnus expects to use a major mode with no setup, why not give
them this:
(define-derived-mode org-safe-mode org-mode "Org-Safe"
;; docstring etc.
)
and then conditionalize on the value of mode-name instead of an extra
variable that they should bind? This would also help to later add more
"safe" functionality without changing things again and again in Org,
Gnus or elsewhere. For example, not running source blocks (we already
have a way of doing that for export, so it shouldn't be hard to add this).
I'm not arguing against your fix, I'd just prefer we'd start with
something we just need to extend into a proper safe-mode instead of
having to start again from scratch after hot-fixing this unfortunate
interaction with Gnus (and I still don't know how Gnus gets there, anyway).
Regards,
--
Achim.
(on the road :-)
next prev parent reply other threads:[~2013-03-25 17:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 13:06 :EXPORT_FILE_NAME: in new exporter possible? Rainer Stengele
2013-03-21 15:34 ` Eric Abrahamsen
2013-03-21 23:15 ` Andreas Leha
2013-03-21 23:23 ` Bastien
2013-03-25 5:45 ` Bastien
2013-03-25 10:09 ` Achim Gratz
2013-03-25 14:57 ` Bastien
2013-03-25 15:09 ` Achim Gratz
2013-03-25 15:54 ` Bastien
2013-03-25 16:13 ` Achim Gratz
2013-03-25 16:57 ` Bastien
2013-03-25 17:00 ` Bastien
2013-03-25 17:39 ` Achim Gratz [this message]
2013-03-25 18:52 ` Bastien
2013-03-22 0:20 ` John Hendy
2013-03-22 7:41 ` Rainer Stengele
2013-03-22 14:51 ` John Hendy
2013-03-22 16:04 ` Rainer Stengele
2013-03-22 18:20 ` Nicolas Goaziou
2013-03-22 14:58 ` Nicolas Goaziou
2013-03-22 15:21 ` Rainer Stengele
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='kiq236$vtb$1@ger.gmane.org' \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@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 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).