all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'David Reitter' <david.reitter@gmail.com>,
	'Emacs-Devel devel' <emacs-devel@gnu.org>
Subject: RE: Oop customization group
Date: Sun, 07 Jun 2009 14:43:19 +0900	[thread overview]
Message-ID: <87k53ofvk8.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <2ADA2594AEBC491B83F4A0C5329C4ECD@us.oracle.com>

Drew Adams writes:
 > >  > Group inheritance can be multiple. This is essentially a tagging
 > >  > mechanism (in the sense of del.icio.us tags, not Emacs tags),
 > > 
 > > No, it's not, not until the UI reflects that.
 > 
 > You seem to be in violent agreement. ;-)

Well, not entirely.  Some hierarchy is necessary, and the tagging
mechanisms I'm familiar with don't really provide that.  A few minutes
trying to get help on any GUI application whether from Microsoft or
GNOME convinces me that documentation is not something that should be
left to non-developer users.  (I don't know about del.icio.us, I stay
as far away from that kind of Web2.0 as I can.)

 > Perhaps gnu.org could have a Web service that would federate user
 > tagging, and which could be used to update one's local Emacs. That
 > is, local tagging by users could be pushed out, and tags collected
 > from non-local users could be pulled in.

This is what I had in mind, although like you I don't really know how
the "federating" algorithm should work.





  reply	other threads:[~2009-06-07  5:43 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 [this message]
2009-06-06 19:06 ` Stefan Monnier
2009-06-08 21:21   ` 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

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

  git send-email \
    --in-reply-to=87k53ofvk8.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=david.reitter@gmail.com \
    --cc=drew.adams@oracle.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.