From: Carsten Dominik <dominik@science.uva.nl>
To: "Alan E. Davis" <lngndvs@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Drawers for plain old stuff
Date: Tue, 6 May 2008 09:24:40 +0200 [thread overview]
Message-ID: <66ACEB07-AB9B-4BA1-BC09-3AAC84B559AA@science.uva.nl> (raw)
In-Reply-To: <481F0BAE.6060108@gmail.com>
On May 5, 2008, at 3:29 PM, Alan E. Davis wrote:
>
>> the drawer cannot contain a headline, i.e. a line starting with one
>> or several stars followed by a space character. Most likely, this
>> is what was causing you problems?
> Exactly.
>
> A case I can think of---perhaps not convincing?---for regular
> expression of drawer names is a file with many pasted in, lengthy
> notes or data sets. So as to be able to distinguish them without
> opening them, one might wish to title them:
>
> :DATA-PROFILE1:
>
> :DATA-PROFILE2X:
>
> :DATA-TRANSECT_A:
>
> :DATA-SALINITY-2008-04-29:
>
> An extremely simple regular expression would be "DATA.*" . One can
> argue, convincingly, that each data set would best be stored in a
> file, and could be linked to.
> I did have two sets of calendars from 1984 and 1985 that were not
> huge, but were in the way. I can as easily entitle each with a
> headline, then brace them in :CACHE: drawers.
> You have convinced me, but I hope I would not bore you by asking you
> for comments about this.
Of course, not, I always like to get feedback and new ideas.
As for your example, I do think that headlines with a drawer below
them would be just as useful and efficient in this case. Seems that
you agree, so for now: no regexp for drawer names. But I put it on my
list, maybe now that you suggested it, I will actually find a use for
this.
Thanks.
- Carsten
next prev parent reply other threads:[~2008-05-06 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 9:19 Drawers for plain old stuff Alan E. Davis
2008-05-03 10:42 ` Carsten Dominik
2008-05-05 13:29 ` Alan E. Davis
2008-05-06 7:24 ` Carsten Dominik [this message]
2008-05-06 22:01 ` Daniel J. Sinder
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=66ACEB07-AB9B-4BA1-BC09-3AAC84B559AA@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=lngndvs@gmail.com \
/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).