emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 11:52:33 -0400	[thread overview]
Message-ID: <m2mx6k298e.fsf@boostpro.com> (raw)
In-Reply-To: <87pqbhgd32.fsf@gnu.org> (Bastien's message of "Mon, 09 Apr 2012 17:05:37 +0200")


on Mon Apr 09 2012, Bastien <bzg-AT-gnu.org> wrote:

> Hi Dave,
>
> Dave Abrahams <dave@boostpro.com> writes:
>
>> I want the rule to be that you can have as much body text as you want
>> between the headline and the SCHEDULED: line.  
>
> This won't happen.  

Because...?

>> Or failing that, I'd like
>> org's default keybindings to make it really hard to insert text between
>> the headline and SCHEDULED:.  Any typing in that area should, by
>> default, force the point to jump after SCHEDULED:
>
> Yes, this is a possibility.  The other possibility is to store SCHEDULED
> and DEADLINE information in a drawer.

That would be an "easy" solution.

> In both cases, this requires a careful discussion.
>
> As I cannot spend this time right now, the helper function to fix
> misformatted subtrees is better than nothing.  

Yes.

> And unless there is a Global Internet Strike (©) requesting this issue
> to be fixed, I think we should live with it -- or make a collective
> effort.

I understand.

>> Thanks, I think... but I can't tell if everybody is missing my point.
>> I've been trying to argue for something that doesn't allow mistakes
>> to happen in the first place.
>
> I understand.
>
> But again: the mistake happens for people who move this line manually
> and for poeple who don't read the manual.

And again: this is a developer-centric response.  As a matter of
usability it doesn't matter very much that "you told me so" (in a manual
100s of pages long --- and it's buried in a footnote, for chrissake!)
when the mistake is trivially easy to make... and it is.  I only have
only ever "moved that line" without knowing I was doing it.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

  reply	other threads:[~2012-04-09 15:52 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
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 [this message]
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=m2mx6k298e.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).