From: Jost Burkardt <jost.burkardt@web.de>
To: emacs-orgmode@gnu.org
Subject: Re: #+CATEGORY line being archived
Date: Tue, 20 Mar 2007 20:18:35 +0100 [thread overview]
Message-ID: <87bqin7mgk.fsf@web.de> (raw)
Carsten Dominik <dominik@science.uva.nl> writes:
> On Mar 18, 2007, at 17:09, Bastien wrote:
>
>> Leo <sdl.web@gmail.com> writes:
>>
>>> I found that if I do 'C-c C-x C-s' on headline "Done Task", all text
>>> up to the next headline "CR" is archived. This clearly is not the
>>> right behavior. Am I doing something wrong or is this a bug?
>>
>> I had this problem before and I'm now using #+ARCHIVE like this:
>>
>> ,----
>> | * Head1
>> | * Done Task
>> |
>> | * CR
>> | #+CATEGORY: CR
>> | #+ARCHIVE: %s_archive::* CR
>> | * anything
>> `----
>>
>
> This is a fundamental problem, for which there are only work-arounds,
> no solutions. Because of the structure of an outline, there is no such
> thing as a "location between sections".
One solution which comes to my mind is to bind
#+CATEGORY: CR
to the previous heading, just the way the task keyword SCHEDULE, etc. do.
One possible use case, where this would break the actual beheavious,
which comes to my mind is categorisation of a task list, eg.
* Tasks
#+CATEGORY: @WORK
** TODO Task 1
** TODO Task 2
#+CATEGORY: @HOME
** TODO Task 3
but maybe it would always be possible (and maybe more outliner like)
to categorize via additional Subheadings:
* Tasks
** @WORK
#+CATEGORY: @WORK
*** TODO Task 1
*** TODO Task 2
** @HOME
#+CATEGORY: @HOME
** TODO Task 3
No Idea, how easy such an behaviour could be implemented.
Jost
PS. I was reading this list via gmane for a while, this is my first
post, so let me say, how much I appreciate this fantastic emacs-mode,
which definitely did change my personal planning to the better !
next reply other threads:[~2007-03-20 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 19:18 Jost Burkardt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-18 14:21 #+CATEGORY line being archived Leo
2007-03-18 16:09 ` Bastien
2007-03-18 16:44 ` Leo
2007-03-18 20:00 ` Carsten Dominik
2007-03-18 20:16 ` Leo
2007-03-18 23:42 ` 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=87bqin7mgk.fsf@web.de \
--to=jost.burkardt@web.de \
--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).