emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Brian van den Broek <broek@cc.umanitoba.ca>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: possible misfeature regarding multiple #+ARCHIVE lines in	a file
Date: Sat, 01 Sep 2007 18:05:31 -0400	[thread overview]
Message-ID: <46D9E22B.10207@cc.umanitoba.ca> (raw)
In-Reply-To: <46D9DEE6.6060503@cc.umanitoba.ca>

Brian van den Broek said unto the world upon 09/01/2007 05:51 PM:

Hi all,

Sorry for the self-reply, but after posting I expanded the parameters 
of my google search, and thought a follow-up worthwhile.

I posted woes regarding #+ARCHIVE lines getting archived or left 
behind. And I suggested a dummy headline to ameliorate the problem:

> As I understand org-mode, this is a consequence of taking a subtree of 
> level n to continue until a headline of level m, m <= n occurs or EOF. 
> But, unless I am missing something, I don't see how the multiple 
> #+ARCHIVE lines technique can be made to work with this definition, 
> short of including dummy level 1 headlines in the file to `protect' the 
> #+ARCHIVE lines. (I mean something like inserting
> 
> * To make org happy
> #+ARCHIVE: ./_testofarchiveARCHIVE.org::* Third
> 
> between * Second 2007 and * Third 2007.)

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.)

Thanks and best,

Brian vdB

  reply	other threads:[~2007-09-01 22:05 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 [this message]
2007-09-03  7:30   ` Carsten Dominik
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=46D9E22B.10207@cc.umanitoba.ca \
    --to=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).