Re: [Orgmode] Feature request [7.3]

[Manish]

On Wed, Dec 8, 2010 at 2:29 AM, Dave Abrahams wrote:
>
> 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.

I am not sure what you mean by agenda here since you don't see the
full entry in the agenda.

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

When in the entry in org file, use `C-c C-z' and when in agenda just
use `z' to add a correctly formatted  and timestamped note.

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

FWIW, I find shift+up/down arrow sufficiently magical for my use case,
but I suppose you have already tried that.

> 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?

You mean like if you clicked/returned on an item in agenda it should
take you to the entry in org file but narrowed to that item?  I had
earlier added a call to org-narrow (I think) to the code that enables
follow mode and the code that jumps to the entry in the org file.  It
used to work nice but was a minor irritation when I needed to widen it
all the time.  I have since lost the code but it should be reasonable
easy to reproduce.

HTH
-- 
Manish