From: Martin Pohlack <mp26@os.inf.tu-dresden.de>
To: "Alan E. Davis" <lngndvs@gmail.com>, org-mode <emacs-orgmode@gnu.org>
Subject: Re: Best way to implement Keywords feature
Date: Mon, 09 Nov 2009 15:52:22 +0100 [thread overview]
Message-ID: <4AF82CA6.8030102@os.inf.tu-dresden.de> (raw)
In-Reply-To: <7bef1f890911051442h28d45647h4f128a241d4e0116@mail.gmail.com>
Alan E. Davis wrote:
> In some cases, a single headword entry can relate to a large number of
> topics. I have tried dealing with longer tag lists: automatic
> adjustment of tags column (on this list a little utility was posted:
> org-adjust-tags-column-reset-tags. I THINK that a keyword list may
> allow more freedom to cross-index, especially if it is easy to use.
>
> Can someone suggest a way to implement a keywording system, perhaps with
> a custom agenda search? Or have others dealt with this issue in
> innovative ways?
>
> I would appreciate any ideas.
I still have the feeling that tags are the way to go. Searching etc.
already works with tags. Their disadvantage seems to be that lines get
cluttered if many tags are used.
Maybe this can be solved with two approaches:
* In agendas, one could have a filter for which tags to show / hide.
This would be useful otherwise too, as it would allow to hide context
tags in already defined agendas.
org-agenda-hide-tags-regex
For example, all my contexts start with "@", so I would set it to be
"^@work$" to hide redundant information in my work agendas, or use
"^@" to remove all context information from a specific agenda.
* For plain view, could we have a soft newline between tags and content
for an item (like in long-lines-mode)?
Tags would be shown on a new line (with indentation etc.) but would be
stored on the same line in files?
For example, the file content ("\" added by me, should be one long
line):
*** TODO test1 :keyword1:keyword2:keyword3:keyword4:keyword5: \
keyword6:keyword7:keyword8:keyword9:keyword10:keyword11:
Is shown like this in org-mode:
*** TODO test1
:keyword1:keyword2:keyword3:keyword4:keyword5:keyword6:keyword7:
keyword8:keyword9:keyword10:keyword11:
Cheers,
Martin Pohlack
next prev parent reply other threads:[~2009-11-09 14:52 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
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 [this message]
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=4AF82CA6.8030102@os.inf.tu-dresden.de \
--to=mp26@os.inf.tu-dresden.de \
--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).