From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: move org line to next superior level
Date: Thu, 29 May 2014 20:03:32 +0200 [thread overview]
Message-ID: <87vbsoxy17.fsf@gmail.com> (raw)
In-Reply-To: loom.20140529T191332-782@post.gmane.org
Uwe Ziegenhagen <ziegenhagen@gmail.com> writes:
> Eric Abrahamsen <eric <at> ericabrahamsen.net> writes:
>>
>> Thorsten Jolitz <tjolitz <at> gmail.com> writes:
>>
>> >
>> > Isn't it a feature of Org-mode that tasks can be added anywhere without
>> > giving a thought in the agenda files, letting the agenda itself sort
>> > them by date? Just changing the timestamp from monday to tuesday would
>> > do the job in a normal workflow, making the agenda-file structuring by
>> > day redundant.
>
> The way that I currently use Org Mode is the following
>
> On level 1 I have all the weeks, on level 2 the tasks
>
> * 2014-05-26--2014-06-01
> ** TODO [#C] Python Test
>
> I know org mode offers way more functionalities, but right now I am
> exploring the basics.
But basic idiomatic use would be a simple
,-----------------------------------------
| * TODO [#C] Python Test <2014-05-29 Do>
`-----------------------------------------
or maybe using a period with 2 timestamps
,---------------------------------
| <2014-05-29 Do>--<2014-05-30 Fr>
`---------------------------------
or SCHEDULED or DEADLINE planning elements. You can even use repeaters
etc then.
Your system uses time info for file structuring, but Org has timestamps
for time info and the agenda for dealing with time and organizing
entries.
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-05-29 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 3:57 move org line to next superior level Uwe Ziegenhagen
2014-05-29 14:28 ` Thorsten Jolitz
2014-05-29 15:12 ` Eric Abrahamsen
2014-05-29 17:16 ` Uwe Ziegenhagen
2014-05-29 18:03 ` Thorsten Jolitz [this message]
2014-05-29 18:15 ` Uwe Ziegenhagen
2014-05-30 9:16 ` Thorsten Jolitz
2014-05-29 17:29 ` Bastien
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=87vbsoxy17.fsf@gmail.com \
--to=tjolitz@gmail.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).