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: Mon, 03 Sep 2007 15:31:55 -0400	[thread overview]
Message-ID: <46DC612B.9090903@cc.umanitoba.ca> (raw)
In-Reply-To: <72e7a9ad50ae8764e85f070921edee7a@science.uva.nl>

Carsten Dominik said unto the world upon 09/03/2007 02:25 PM:
> Hi Brian,
> 
> On Sep 3, 2007, at 19:43, Brian van den Broek wrote:

<snip>

>> The only way I can see to do it with #+ARCHIVE lines would be to have 
>> my teaching.org look like
>>
>> * Heading setting ARCHIVE line for following tree
>> * Intro to Logic Fall20072008
>> * Heading setting ARCHIVE line for following tree
>> * Intro to Philosophy 20072008
>> etc.
>>
>> That makes for ugly clutter, IMHO. (The problem is acute in my 
>> intended case, as each level 1 heading needs its own ARCHIVE line.)
> 
> I would say that this only requires a litte creative restructuring,
> and to give up the idea that in teaching.org, courses must be level 1.
> 
> In teaching.org:
> 
> * Intro to Logic
> #+ARCHIVE: archive settings for logic
> ** Fall200072008
> 
> * Intro to Philosophy
> #+ARCHIVE: settings for philosophy
> ** FALL20072008
> 


Hi Carsten,

Sure that would work, if only I could get past the tunnel vision 
induced by my first conception of how to structure things ;-)

Thanks for the discussion.

Best,

Brian vdB

  reply	other threads:[~2007-09-03 19:32 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
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 [this message]
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=46DC612B.9090903@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).