From: Dave Abrahams <dave@boostpro.com>
To: Bastien <bzg@gnu.org>
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 09:58:53 -0400 [thread overview]
Message-ID: <m2iph92ehu.fsf@boostpro.com> (raw)
In-Reply-To: <878vi5xe7p.fsf@gnu.org> (Bastien's message of "Mon, 09 Apr 2012 14:49:14 +0200")
on Mon Apr 09 2012, Bastien <bzg-AT-gnu.org> wrote:
> 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.
It would be very useful. Just not /more/ useful. The most useful
functionality is the one that just works without any intervention from
the user.
>> 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.
Sorry, but I don't want to spend the time on that. I'm trying to get
the rules changed so that it isn't so easy to corrupt an org file. I'm
not much interested in building a tool to undo corruption.
> 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.
I sincerely hope that when you become clearer about such cases you pick
a liberal set of rules that isn't so error-prone. The ideas that I
can't just hit return after a headline and start typing a body, and that
I'll be nagged about misplaced SCHEDULED: lines, are both very
unappealing.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2012-04-09 13:59 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
2012-04-09 13:58 ` Dave Abrahams [this message]
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
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=m2iph92ehu.fsf@boostpro.com \
--to=dave@boostpro.com \
--cc=bzg@gnu.org \
--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 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).