From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: doc and help for defvaralias
Date: Mon, 3 Jul 2006 14:30:32 -0700 [thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMAEEICJAA.drew.adams@oracle.com> (raw)
In-Reply-To: <EIENLHALHGIMHGDOLMIMMEEHCJAA.drew.adams@oracle.com>
Let me be clearer about the connection to variables in this use case:
2. I have used `defvaralias' to provide an alias (!) - no
connection with deprecation. I have two libraries, one of which
(eyedropper.el) is a rudimentary version the other (palette.el),
providing only some of its functionality. The rudimentary library
is for Emacs versions before Emacs 22, but that is irrelevant -
one might simply be a lightweight, reduced version of the other.
Some other libraries use (require) the eyedropper functionality,
calling functions
and using variables
defined in eyedropper.el and named using prefix `eyedrop-'.
Library palette.el redefines the eyedropper commands,
providing them with additional bells and whistles. Because the
other libraries use functions
and variables
that start with `eyedrop-', library palette.el provides
`eyedrop-' aliases to its fancier versions (which are defined
with prefix `palette-').
The point here was about variable aliases, but I didn't make that clear in
the use-case description. Libraries use the `eyedrop-' variables and in fact
get the `palette-' variables.
If you use Emacs 22 and you have palette.el loaded, then you can
use the other libraries as is and take advantage of the palette.el
versions
of `eyedrop-' functions and variables,
thanks to the aliases.
next prev parent reply other threads:[~2006-07-03 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 18:23 doc and help for defvaralias Drew Adams
2006-06-26 4:22 ` Miles Bader
2006-07-03 19:15 ` Stefan Monnier
2006-07-03 21:11 ` Drew Adams
2006-07-03 21:30 ` Drew Adams [this message]
2006-07-04 12:55 ` Richard Stallman
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=EIENLHALHGIMHGDOLMIMAEEICJAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/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.