all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: tags for functions
Date: Thu, 22 Jan 2009 14:38:45 -0600	[thread overview]
Message-ID: <86eiyv6ppm.fsf@lifelogs.com> (raw)
In-Reply-To: d2afcfda0901221015t400ed53bp43eeaef1baee8300@mail.gmail.com

On Thu, 22 Jan 2009 13:15:21 -0500 "S+*n_Pe*rm*n" <stan@derbycityprints.com> wrote: 

SP> Tagging in the sense that you seem to be using the term is best left
SP> to domains which lack a characteristic structure and/or which can't
SP> be pre-limited/defined.

I think Emacs Lisp lacks a characteristic structure and it can't be
pre-limited or pre-defined.  It's an amorphous tangle of functions and
symbols.  Attempting to impose any kind of structure on that tangle is
not useful IMHO.

SP> You have the opportunity *now* to reduce the number of potential core
SP> `tags'. You appear to be suggesting that this is your intention. Such
SP> an effort is best characterized as the production of a controlled
SP> vocabulary.  Apropos of this, I am proposing you formalize the
SP> production according to the best practices outlined by the standard.

I will try, but I'm not going to follow a 180 page standard to the
letter.  The goal is discovery of similar functions, not classification
of everything (see my original post).

>> and others like proper name conventions just don't apply.
SP> What about Internationalization?

If you can be specific, one of the maintainers may give you an official
statement, but AFAIK at the Emacs Lisp level that's not a concern.

I appreciate your comments but I think your vision is far more ambitious
than my proposal and has completely different goals (though it could use
the facilities I plan to implement).  Perhaps you should start a
separate thread and make a specific proposal.  The standards you have
listed, while very thorough, are not as helpful in such a proposal as a
clear classification proposal that can be seen and touched.

Ted





  parent reply	other threads:[~2009-01-22 20:38 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
2009-01-22 20:38 ` Ted Zlatanov [this message]
  -- 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86eiyv6ppm.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 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.