From: Jeff Horn <jrhorn424@gmail.com>
To: Dave Abrahams <dave@boostpro.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature request [7.3]
Date: Tue, 7 Dec 2010 23:37:30 -0500 [thread overview]
Message-ID: <AANLkTim2ueSXbHZTwAvmFKxcSsN1gXsgqA8VXhMxKUtO@mail.gmail.com> (raw)
In-Reply-To: <m2tyipfgex.fsf@boostpro.com>
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 <dave@boostpro.com> 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. 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
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
--
Jeffrey Horn
Graduate Lecturer and PhD Student in Economics
George Mason University
(704) 271-4797
jhorn@gmu.edu
jrhorn424@gmail.com
http://www.failuretorefrain.com/jeff/
next prev parent reply other threads:[~2010-12-08 4:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 20:59 Feature request [7.3] Dave Abrahams
2010-12-08 4:37 ` Jeff Horn [this message]
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=AANLkTim2ueSXbHZTwAvmFKxcSsN1gXsgqA8VXhMxKUtO@mail.gmail.com \
--to=jrhorn424@gmail.com \
--cc=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
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).