emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Dave Abrahams <dave@boostpro.com>
To: emacs-orgmode@gnu.org
Subject: Feature request [7.3]
Date: Tue, 07 Dec 2010 15:59:18 -0500	[thread overview]
Message-ID: <m2tyipfgex.fsf@boostpro.com> (raw)


When using Org for planning, I often find myself corrupting my Org
files.  All kinds of things can go wrong, but the basic issue is that
agenda items have a syntax, and it's easy to violate, especially when
I'm going *fast*, which after all is what Org is supposed to enable!

For example, a typical captured item looks like:

** TODO Set up yasnippet
   SCHEDULED: <2010-11-22 Mon>
   :PROPERTIES:
   :Link: [[some-nasty-link]]
   :ID:       A0B4159C-D796-40DF-9ADD-93DF03577B68
   :END:
   [2010-11-20 Sat 20:17]

Now, suppose I'm looking at this in the agenda and I want to add some
commentary.  Where should I open the new line?  If I choose wrongly, my
agenda will start to misbehave (e.g. items will appear to be
un-reschedulable because they'll acquire a second SCHEDULED date).  

So I'm requesting some more help from Org in maintaining proper Org
syntax.  Could Org have a mode that prevents things from being modified
incorrectly?  For example, it'd be awesome if dates were smart (TAB into
one, hit return, get a smart date editor).  It'd be great if there were
a way to make the ID property read-only (or really really hard to
change).  I'd love it if there were a way to create a link to an org
item that narrows the view to just that item, so I don't inadvertently
mess anything else up.  Do you get the idea?

Thanks for listening,

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

next             reply	other threads:[~2010-12-07 20:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 20:59 Dave Abrahams [this message]
2010-12-08  4:37 ` Feature request [7.3] Jeff Horn
2010-12-08 16:20 ` Eric S Fraga
2010-12-09  2:48   ` Dave Abrahams
2010-12-09  8:57     ` Eric S Fraga
2010-12-09 10:42       ` Dave Abrahams
2010-12-08 17:41 ` Manish
2010-12-08 22:14   ` Dave Abrahams

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=m2tyipfgex.fsf@boostpro.com \
    --to=dave@boostpro.com \
    --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

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).