From: MON KEY <monkey@sandpframing.com>
To: tzz@lifelogs.com
Cc: emacs-devel@gnu.org
Subject: Re: tags for functions
Date: Thu, 22 Jan 2009 13:49:26 -0500 [thread overview]
Message-ID: <d2afcfda0901221049m6cf05d81v640e398305717f4@mail.gmail.com> (raw)
In-Reply-To: <d2afcfda0901221015t400ed53bp43eeaef1baee8300@mail.gmail.com>
Forgot to mention that the initial formulation of a controlled
vocabulary may well be already done for you.
If you consider that the emacs/elisp info manuals are *already*
formatted in a structured manner not unlike the Z39.19 you might
recognize that many of the `keywords' and relationships you need are
already in the .texi source.
I suggest you start with the the .texi source and extract the relevant
terms as a proposed hierarchy for your controlled vocabulary. This can
then be extended by with `freely assignable 'sub-tags' attached to the
core controlled headwords.
BT: Yanking::Replacing Yanks <= post :: is the authors `freely
assigned' sub-tag
NT: Earlier Kills::Regexp on Kill Ring <= post :: is the authors
`freely assigned' sub-tag
RT: Mark Ring::Conditional Yanks <= post :: is the authors `freely
assigned' sub-tag
Such a structure might afford integration/reflection with make-info at
build time and present a more consistent interface at a higher level.
next prev parent reply other threads:[~2009-01-22 18:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 18:15 tags for functions S+*n_Pe*rm*n
2009-01-22 18:49 ` MON KEY [this message]
2009-01-22 20:38 ` Ted Zlatanov
-- strict thread matches above, loose matches on Subject: below --
2009-01-23 1:46 S+*n_Pe*rm*n
2009-01-27 18:53 ` MON KEY
2009-01-22 8:07 MON KEY
2009-01-22 14:47 ` Ted Zlatanov
2009-01-20 20:36 Ted Zlatanov
2009-01-20 20:44 ` Lennart Borgman
2009-01-21 22:11 ` Ted Zlatanov
2009-01-21 22:13 ` Lennart Borgman
2009-01-22 14:20 ` Ted Zlatanov
2009-01-22 19:39 ` Stefan Monnier
2009-01-22 20:09 ` Ted Zlatanov
2009-01-21 22:22 ` Glenn Morris
2009-01-22 14:54 ` Ted Zlatanov
2009-01-25 0:32 ` Juri Linkov
2009-01-26 19:50 ` Ted Zlatanov
2009-01-26 23:55 ` Juri Linkov
2009-01-27 14:31 ` Ted Zlatanov
2009-01-28 0:02 ` Juri Linkov
2009-01-28 0:36 ` Lennart Borgman
2009-01-28 17:41 ` Ted Zlatanov
2009-01-28 18:40 ` Stefan Monnier
2009-01-28 20:38 ` Ted Zlatanov
2009-01-29 1:43 ` Stefan Monnier
2009-01-29 20:03 ` Ted Zlatanov
2009-01-29 21:52 ` Stefan Monnier
2009-01-30 15:34 ` Ted Zlatanov
2009-01-30 16:06 ` Drew Adams
2009-01-30 16:52 ` Ted Zlatanov
2009-01-31 17:52 ` Juri Linkov
2009-01-31 1:55 ` Stefan Monnier
2009-01-31 2:02 ` Drew Adams
2009-01-29 20:32 ` Lennart Borgman
2009-01-30 15:29 ` Ted Zlatanov
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d2afcfda0901221049m6cf05d81v640e398305717f4@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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.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).