From: Carsten Dominik <dominik@science.uva.nl>
To: Brian van den Broek <broek@cc.umanitoba.ca>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: possible misfeature regarding multiple #+ARCHIVE lines in a file
Date: Mon, 3 Sep 2007 09:30:54 +0200 [thread overview]
Message-ID: <fc9e51c7b4b6db4d05c2f8c32051e22b@science.uva.nl> (raw)
In-Reply-To: <46D9E22B.10207@cc.umanitoba.ca>
On Sep 2, 2007, at 0:05, Brian van den Broek wrote:
> Brian van den Broek said unto the world upon 09/01/2007 05:51 PM:
> In a thread from 2007-03 started by
> <http://lists.gnu.org/archive/html/emacs-orgmode/2007-03/
> msg00084.html>
> a similar problem was discussed regarding #+CATEGORY lines. Carsten
> <http://lists.gnu.org/archive/html/emacs-orgmode/2007-03/
> msg00089.html> said that what I called `dummy' headlines was one of
> two possible work-arounds he could see. What didn't come up was the
> suggestion I made:
>
>> It seems to me that a possible fix would be to look at the end of any
>> subtree that is being archived, and leave behind an #+ARCHIVE line
>> (or perhaps uninterrupted block of #+ lines) that terminates the tree
>> being archived.
>
> Now I am curious as to if this is unworkable. Carsten, if it is, would
> you mind briefly sketching why? (Time permitting, of course.)
Hi Brian,
In principle the solution you propose is workable of course.
You are, in fact, not the first to think of this: for example
the file outline.el in Emacs 22 states:
;;; Todo:
;; - subtree-terminators
;; - better handle comments before function bodies (i.e. heading)
;; - don't bother hiding whitespace
This is an issue in many types of files that would like to use
outline to get a structured view on a file. For example
Programmers often write comments *before* a function definition.
I find it hard to envision a *clean* implementation, however.
Problems with this approach are:
- Lets say we say that comments before a headline so not belong
to the entry before it. Do they belong to the entry after it?
If I archive the entry after it, should I move the comment then?
- What if I have a normal entry with some text in there, and I decide to
comment it out, just temporarily. All of a sudden this text no longer
belongs to the entry, when I move the entry up or down, using
structure editing commands, how should I decide in a safe way what
comment does and what dow not belong to an entry?
The current outline implementation is at least clean in the sense
that it is totally predictable what will happen if you issue
certain commands.
I still believe that the best work-around it to have top-level
sections in your file, make the #+ARCHIVE lint the first line *inside*
the section, and then have your TODO items as level 2 entries below it.
If you are going to structure your document anyway in a way that
requires multiple archives, why not reflect this structure also
with top-level headlines?
- Carsten
next prev parent reply other threads:[~2007-09-03 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 21:51 possible misfeature regarding multiple #+ARCHIVE lines in a file Brian van den Broek
2007-09-01 22:05 ` Brian van den Broek
2007-09-03 7:30 ` Carsten Dominik [this message]
2007-09-03 17:43 ` Brian van den Broek
2007-09-03 18:25 ` Carsten Dominik
2007-09-03 19:31 ` Brian van den Broek
2007-09-03 20:43 ` Carsten Dominik
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=fc9e51c7b4b6db4d05c2f8c32051e22b@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=broek@cc.umanitoba.ca \
--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).