From: "Drew Adams" <drew.adams@oracle.com>
To: "'Glenn Morris'" <rgm@gnu.org>, "'Chong Yidong'" <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: RE: VC filesets
Date: Sun, 19 Oct 2008 14:35:59 -0700 [thread overview]
Message-ID: <005b01c93232$adfb7020$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <dhprlwe2o6.fsf@fencepost.gnu.org>
> On this subject, it's unfortunate that VC now uses the term "fileset"
> extensively, with a totally different meaning to the pre-existing
> "filesets.el" package; but I don't have a solution.
I know nothing about VC filesets, but I agree about the problem - and I too
don't have a solution. ;-)
I think the problem comes from the adoption of "fileset" by filesets.el - that
term is too general as a name for the specific feature that the library
implements.
There was nothing wrong with that characterization by filesets.el at the time.
It's just that the term is intrinsically so general that it naturally leads to
verbal gymnastics to avoid confusion with the limited meaning it has taken on in
Emacs.
As another illustration, Icicles supports Emacs filesets but it also supports
other kinds of saved sets of file names. The Icicles doc refers to the latter in
just that roundabout way, because "fileset" has been given a narrow meaning by
Emacs.
I'm not proposing anything here - just adding another anecdote about the
unfortunate terminology situation.
Similar things could be said about other features - bookmarks, for instance.
Googling or searching the Emacs wiki will show that there are other packages
that provide bookmarking features, but calling those features "bookmarks" leads
to confusion in cases where they are incompatible with the bookmarks of
bookmarks.el.
I doubt that there is a good general solution to problems such as this.
Proactively we could try to use more specific terms for new features - or to
invent new terms, instead of eagerly adopting very general existing terms.
There probably is a natural tendency, unfortunately, for a feature inventor to
characterize the feature in the most general terms. Bookmarking (or tabs or ...)
in Emacs means just this feature...
Another thing that might help a little bit (but not much) would be to choose a
different name for the library itself, if a general name is chosen for the
feature.
It's pretty clear, for example, if you speak of "Bm bookmarks", or "Info
breadcrumbs", or "Tabbar tabs". It's less clear if you have to speak of
"Bookmarks bookmarks", or "Breadcrumbs breadcrumbs", or "Tabs tabs" (for a
fictitious library tabs.el).
next prev parent reply other threads:[~2008-10-19 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 3:07 VC filesets Chong Yidong
2008-10-19 8:08 ` Dan Nicolaescu
2008-10-20 19:55 ` Chong Yidong
2008-10-21 0:30 ` Dan Nicolaescu
2008-10-19 20:43 ` Glenn Morris
2008-10-19 21:35 ` Drew Adams [this message]
2008-10-20 5:24 ` Richard M. Stallman
2008-10-20 6:04 ` Drew Adams
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='005b01c93232$adfb7020$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).