From: MON KEY <monkey@sandpframing.com>
To: emacs-devel@gnu.org
Subject: Re: Oop customization group
Date: Mon, 08 Jun 2009 17:21:50 -0400 [thread overview]
Message-ID: <87zlciqv4h.fsf@sandpframing.com> (raw)
In-Reply-To: <jwvws7pmbkn.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 06 Jun 2009 15:06:46 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> can be done incrementally. General suggestions for useful categories
> would be welcome (both category name and clear description of what it
> shoujld contain). We could start with `major-mode' (which I'd constrain
> to be modes for use in files-buffers) and `minor-mode'.
The best approach remains to mirror/reflect the structure of the
emacs/elisp manuals ITR esp. as this allows for reasonable and extensibl
xrefs to source and documentation going forward.
The 'delicious tags' approach is _not_ TRT here, nor is a strict class
hiearchy 'multiple inhertiance' or otherwise. TRT is a thesaurus in the
z39.50 sense. Zthes offers a nice set of docs, tagsets, schemas,
attribute sets, etc. for such an implentation see (URL
`http://zthes.z3950.org/z3950/zthes-z3950-1.0.html#2.5')
The CQL, SRU, Soap, interfaces could afford mutiple paths to a
controlled _and_ open 'tagset' in the cataloger/indexer sense as opposed
to the "gee I better tag this library for custom" use that emacser's
tend to employ.
Why is it that programmers believe they make good classifiers?
s_P
prev parent reply other threads:[~2009-06-08 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 12:24 Oop customization group David Reitter
2009-06-06 16:57 ` chad
2009-06-06 18:08 ` Drew Adams
2009-06-07 0:14 ` Stephen J. Turnbull
2009-06-07 3:32 ` Drew Adams
2009-06-07 5:43 ` Stephen J. Turnbull
2009-06-06 19:06 ` Stefan Monnier
2009-06-08 21:21 ` MON KEY [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zlciqv4h.fsf@sandpframing.com \
--to=monkey@sandpframing.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.