From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Allowing loose ordering in Org files
Date: Mon, 09 Nov 2015 21:04:44 +0100 [thread overview]
Message-ID: <874mgvym5f.fsf@Rainer.invalid> (raw)
In-Reply-To: m2twovgeme.fsf@Vulcan.attlocal.net
John Wiegley writes:
>> You will find that the argument really wasn't about performance, but
>> complexity.
>
> I can accept a complexity argument,
I meant O() complexity, not implementation complexity.
> if my request were really "a separate
> code-path". I'm not sure it is. For example, my needs could be satisfied by
> something as simple as:
>
> (defun parse-org-entry (...)
> (let ((props (funcall 'parse-org-properties-function ...)))
> ...))
>
> `parse-org-properties-function' would point to a function that does what Org
> 8.3 does now. This gives me the option of porting over the 8.2 version and
> keeping the old behavior. All that needs to be done is to allow this hook, no?
If it's not about providing the alternative behaviour within Org, then
what does this allow you to do that advising parse-org-entry can't? A
hook still has the cost of simply being there even when I don't use it.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2015-11-09 20:05 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 0:11 bug in org-habits Mark A. Hershberger
2015-11-03 9:56 ` Marco Wahl
2015-11-03 11:16 ` Puneeth Chaganti
2015-11-03 13:11 ` John Wiegley
2015-11-03 13:46 ` Marco Wahl
2015-11-03 14:20 ` Stelian Iancu
2015-11-03 16:31 ` Nicolas Goaziou
2015-11-03 19:20 ` John Wiegley
2015-11-03 19:35 ` Nicolas Goaziou
2015-11-03 20:17 ` John Wiegley
2015-11-03 20:52 ` Nicolas Goaziou
2015-11-03 20:55 ` John Wiegley
2015-11-03 21:31 ` Achim Gratz
2015-11-03 21:36 ` John Wiegley
2015-11-03 21:48 ` Jonathan Leech-Pepin
2015-11-03 21:56 ` John Wiegley
2015-11-03 22:36 ` Achim Gratz
2015-11-03 22:45 ` John Wiegley
2015-11-04 13:01 ` Bastien Guerry
2015-11-04 20:26 ` John Wiegley
2015-11-09 15:13 ` Allowing loose ordering in Org files (Was: bug in org-habits) John Wiegley
2015-11-09 17:47 ` Allowing loose ordering in Org files Rasmus
2015-11-09 18:15 ` John Wiegley
2015-11-09 19:28 ` Rasmus
2015-11-09 19:57 ` John Wiegley
2015-11-09 19:12 ` Achim Gratz
2015-11-09 19:24 ` John Wiegley
2015-11-09 20:04 ` Achim Gratz [this message]
2015-11-09 21:13 ` Stelian Iancu
2015-11-09 21:30 ` John Wiegley
2015-11-10 1:40 ` Allowing loose ordering in Org files (Was: bug in org-habits) Aaron Ecay
2015-11-10 1:52 ` Allowing loose ordering in Org files John Wiegley
2015-11-10 5:31 ` Thomas S. Dye
2015-11-10 17:37 ` Nicolas Goaziou
2015-11-10 19:20 ` Thomas S. Dye
2015-11-10 20:02 ` John Wiegley
2015-11-10 20:42 ` Matt Lundin
2015-11-10 20:44 ` Matt Lundin
2015-11-10 17:51 ` Matt Lundin
2015-11-10 18:19 ` Matt Lundin
2015-11-10 19:49 ` Achim Gratz
2015-11-10 20:11 ` John Wiegley
2015-11-10 20:38 ` Achim Gratz
2015-11-10 22:35 ` John Wiegley
2015-11-11 16:13 ` Karl Voit
2015-11-10 11:30 ` Allowing loose ordering in Org files (Was: bug in org-habits) Stelian Iancu
2015-11-03 23:43 ` bug in org-habits Nicolas Goaziou
2015-11-04 1:01 ` John Wiegley
2015-11-04 9:02 ` Stelian Iancu
2015-11-04 9:16 ` Eric S Fraga
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=874mgvym5f.fsf@Rainer.invalid \
--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).