From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manish Subject: Re: Feature request [7.3] Date: Wed, 8 Dec 2010 23:11:09 +0530 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=36357 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PQO1D-0001NU-Tg for emacs-orgmode@gnu.org; Wed, 08 Dec 2010 12:41:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PQO1C-00042G-SV for emacs-orgmode@gnu.org; Wed, 08 Dec 2010 12:41:31 -0500 Received: from mail-qy0-f176.google.com ([209.85.216.176]:46073) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PQO1C-000425-Pu for emacs-orgmode@gnu.org; Wed, 08 Dec 2010 12:41:30 -0500 Received: by qyk10 with SMTP id 10so730998qyk.14 for ; Wed, 08 Dec 2010 09:41:29 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Dave Abrahams Cc: emacs-orgmode@gnu.org 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. =A0All 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 > =A0 SCHEDULED: <2010-11-22 Mon> > =A0 :PROPERTIES: > =A0 :Link: [[some-nasty-link]] > =A0 :ID: =A0 =A0 =A0 A0B4159C-D796-40DF-9ADD-93DF03577B68 > =A0 :END: > =A0 [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? =A0If 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. =A0Could Org have a mode that prevents things from being modified > incorrectly? =A0For example, it'd be awesome if dates were smart (TAB int= o > 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. =A0Do 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 --=20 Manish