From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: tags for functions
Date: Wed, 21 Jan 2009 16:11:43 -0600 [thread overview]
Message-ID: <86y6x49un4.fsf@lifelogs.com> (raw)
In-Reply-To: e01d8a50901201244o298a77cfv7eaa7bccf92aa00b@mail.gmail.com
On Tue, 20 Jan 2009 21:44:29 +0100 Lennart Borgman <lennart.borgman@gmail.com> wrote:
LB> On Tue, Jan 20, 2009 at 9:36 PM, Ted Zlatanov <tzz@lifelogs.com> wrote:
>> Ted Z wrote in comp.emacs and gnu.emacs.help:
>>> I agree this would be useful. It's best done with tags IMO, rather
>>> than explicitly listing the related functions. For example, motion
>>> commands should be tagged "motion" and then every command with that
>>> tag can automatically list every motion command. The key is that the
>>> extra work is in classification, not in tediously listing every
>>> command's peers.
>>>
>>> Tags I could use: motion, file, coding-system, menu, buffer, process
>>>
>>> Each package should probably tag its commands with the package name.
>>>
>>> Short tags are not always descriptive enough, but long tags get
>>> unpleasantly verbose so the real art is in balancing between the two.
>>>
>>> Anything more hierarchical than tags is painful to manage in the long run.
>>
>> A tangential discussion about the inconsistent naming of motion commands
>> led me to the proposal above.
>>
>> I think it would be a nice addition to Emacs. I did a search and didn't
>> find prior relevant discussions.
>>
>> Every package with a comment stating Keywords: at the beginning could
>> automatically give those keywords as tags to its functions. That would
>> probably be 50% or less of the total needed tags, but it's an easy
>> start.
LB> I think the idea is nice, but maybe keywords should be used (like in
LB> defcustom etc) for the implementation?
"Keywords" is an OK name for the concept; "tags" is the same thing
logically but we should stick with what's normal for Emacs Lisp. What's
important is to:
1) build a list of command keywords quickly (using each package's
Keywords?)
2) refine the keywords into a simple taxonomy that is not too big nor
too small.
The first question I have is, how to associate keywords with a function?
Should I use the symbol-plist?
Then I can walk the namespace, find all functions, and display their
tags. That will let me construct a taxonomy proposal.
Thanks
Ted
next prev parent reply other threads:[~2009-01-21 22:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 20:36 tags for functions Ted Zlatanov
2009-01-20 20:44 ` Lennart Borgman
2009-01-21 22:11 ` Ted Zlatanov [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-01-22 8:07 MON KEY
2009-01-22 14:47 ` Ted Zlatanov
2009-01-22 18:15 S+*n_Pe*rm*n
2009-01-22 18:49 ` MON KEY
2009-01-22 20:38 ` Ted Zlatanov
2009-01-23 1:46 S+*n_Pe*rm*n
2009-01-27 18:53 ` MON KEY
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=86y6x49un4.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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.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).