emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Alan E. Davis" <lngndvs@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Best way to implement Keywords feature
Date: Thu, 5 Nov 2009 23:25:20 +0000	[thread overview]
Message-ID: <7bef1f890911051525x72620078h292a7e6dfa130118@mail.gmail.com> (raw)
In-Reply-To: <20524da70911051458u7e20e0ddy66cdec034406fa4e@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1169 bytes --]

On Thu, Nov 5, 2009 at 10:58 PM, Samuel Wales <samologist@gmail.com> wrote:

>
>
> One such solution is to use header-line-format to display olpath.
>
> I don't understand this.

In scientific/academic publications, one often sees a list of Keywords in
the topmatter.  That being said, I am not certain how people use them.
There are often a dozen or more.

I have had to throttle back my use of tags, to avoid long header lines.
Also, tags are limited to head lines, only.

I would like to implement a secondary list of keywords, that might be
searched in an agenda search.  I don't know whether properties would be
appropriate, although I understand properties can slow the system down.
Don't know.   Probably something similar to properties.

So, for example, if I am taking notes and indexing video clips or PDFs, a
larger number of keywords would enable me to retrieve them in a less
structured, free form manner.  A custom agenda search would be perfect.

Probably barking up a tree.  Probably just better use of tags would solve
this problem.   Keywords, though, could be implemented outside of
headlines.  Maybe I should just use more headlines.

Thanks.

Alan

[-- Attachment #1.2: Type: text/html, Size: 1519 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-11-05 23:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05 22:42 Best way to implement Keywords feature Alan E. Davis
2009-11-05 22:58 ` Samuel Wales
2009-11-05 23:25   ` Alan E. Davis [this message]
2009-11-05 23:40     ` Samuel Wales
2009-11-06 11:48       ` Alan E. Davis
2009-11-06 13:28         ` Renzo Been :-)
2009-11-06 13:46           ` Giovanni Ridolfi
2009-11-06  9:09 ` Giovanni Ridolfi
2009-11-08 11:24   ` Paul Mead
2009-11-08 12:03     ` Matt Lundin
2009-11-08 18:18       ` Paul Mead
2009-11-08 18:51         ` Matthew Lundin
2009-11-09  0:00           ` Paul Mead
2009-11-09 12:27             ` Matthew Lundin
2009-11-09 13:05               ` Paul Mead
2009-11-09 14:26               ` Darlan Cavalcante Moreira
2009-11-09 14:52 ` Martin Pohlack
2009-11-10 14:47   ` Martin Pohlack
2009-11-20 18:06     ` 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=7bef1f890911051525x72620078h292a7e6dfa130118@mail.gmail.com \
    --to=lngndvs@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@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).