At Wed, 08 Dec 2010 16:20:44 +,
Eric S Fraga wrote:
>
> Dave Abrahams writes:
>
> > 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
>
> I do have a couple of rules I follow to avoid problems.
>
>
At Thu, 09 Dec 2010 08:57:54 +,
Eric S Fraga wrote:
>
> Dave Abrahams writes:
>
> [...]
>
> >> > It'd be great if there were a way to make the ID property
> >> > read-only (or really really hard to change).
> >>
> >> This is where column mode comes in quite handy?
> >
> > Link please?
>
Dave Abrahams writes:
[...]
>> > It'd be great if there were a way to make the ID property
>> > read-only (or really really hard to change).
>>
>> This is where column mode comes in quite handy?
>
> Link please?
Apologies; I meant column view within org mode: info -> org ->
Properties and C
At Wed, 8 Dec 2010 23:11:09 +0530,
Manish wrote:
>
> Manish
> Subject: Re: [Orgmode] Feature request [7.3]
> Date: Wed, 8 Dec 2010 23:11:09 +0530
> To: Dave Abrahams
> Cc: emacs-orgmode@gnu.org
> Message-ID:
>
> On Wed, Dec 8, 2010 at 2:29 AM, Dave Abrahams wrote:
Dave Abrahams writes:
> 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
I do have a couple of rules I follow to avoid problems.
1. I usually have a blank line between the meta data (scheduled,
propert
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
I don't know about others, but I just put note text below everything
else, but before the next headline
On Tue, Dec 7, 2010 at 3:59 PM, 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 th
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 typica
