From: Bastien <bzg@gnu.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: emacs-orgmode@gnu.org, John Wiegley <johnw@boostpro.com>
Subject: Re: Bug: "SCHEDULED: " positioning is fragile [7.8.06 (release_7.8.06.181.ga481)]
Date: Mon, 09 Apr 2012 14:49:14 +0200 [thread overview]
Message-ID: <878vi5xe7p.fsf@gnu.org> (raw)
In-Reply-To: <m2pqbh40ec.fsf@boostpro.com> (Dave Abrahams's message of "Mon, 09 Apr 2012 07:20:27 -0400")
Hi Dave,
Dave Abrahams <dave@boostpro.com> writes:
> 1. I strongly disagree that that would be more useful. It would leave
> the newbie trap and usability bug in place.
Well, we disagree then :) I think it is useful to have a function that
let everyone (not just newbies) know that some subtrees don't respect
Org's writing conventions.
> 2. John Wiegley has been working on some code that allows such things to
> be trivially implemented and I'd rather not duplicate / overlap with
> him. John, would you care to push your org-x stuff upstream soon?
You might also look at org-element.el.
FYI: Nicolas and I have been discussing about the issue you raised, and
the integration of org-element.el will force us to be clearer about such
cases, which is good.
In the meantime, let's restate this again: don't put SCHEDULED: and
DEADLINE: cookies anywhere else than on the line right below the
headline.
Thanks,
--
Bastien
next prev parent reply other threads:[~2012-04-09 12:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 14:41 Bug: "SCHEDULED: " positioning is fragile [7.8.06 (release_7.8.06.181.ga481)] Dave Abrahams
2012-04-06 7:38 ` Bastien
2012-04-06 12:18 ` Dave Abrahams
2012-04-09 11:01 ` Bastien
2012-04-09 11:20 ` Dave Abrahams
2012-04-09 12:49 ` Bastien [this message]
2012-04-09 13:58 ` Dave Abrahams
2012-04-09 14:51 ` Bastien
2012-04-09 14:54 ` Dave Abrahams
2012-04-09 15:05 ` Bastien
2012-04-09 15:52 ` Dave Abrahams
2012-04-10 13:43 ` Rainer Stengele
2012-04-10 14:12 ` Bastien
2012-04-09 20:24 ` John Wiegley
2012-04-10 12:13 ` [PATCH] " Jérémie Courrèges-Anglas
2012-04-10 12:34 ` Bastien
2012-04-10 13:34 ` Jérémie Courrèges-Anglas
2012-04-10 13:40 ` Bastien
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=878vi5xe7p.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=dave@boostpro.com \
--cc=emacs-orgmode@gnu.org \
--cc=johnw@boostpro.com \
/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.