From: "Ehud Karni" <ehud@unix.mvs.co.il>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: New function `emacs-version>='
Date: Sat, 3 May 2003 14:12:09 +0300 [thread overview]
Message-ID: <200305031112.h43BC9tL013684@beta.mvs.co.il> (raw)
In-Reply-To: <20030502232146.C2FF.LEKTU@terra.es> (message from Juanma Barranquero on Fri, 02 May 2003 23:35:14 +0200)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 02 May 2003 23:35:14 +0200, Juanma Barranquero <lektu@terra.es> wrote:
>
> On Fri, 02 May 2003 17:14:07 -0400, "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> wrote:
>
> > It's just that sometimes it's difficult
> > to test whether A works or not. For instance, how do you check whether
> > the `display' property is supported by your version of Emacs ?
>
> Yeah, sure. But most features are not isolated, there are related
> variables, functions and sometimes even an entry in `features'... And if
> not, I'd call that a bug in the feature/fix implementation (I'm
> exaggerating, but only a bit.)
>
> And, as a last resort, you can often do something like
>
> (unless (ignore-errors XXXX)
> YYYY)
That is NOT always possible, I have another actual example:
How do you check that `perform-replace' accept a function in its
REPLACEMENTS argument (id does in 21.x, does not in 20.x or lower) ?
I have a hacked `perform-replace-20' (which is not the same as the
current version) function for older emacs's and I do:
(if (< emacs-major-version 21)
(defalias 'perform-replace 'perform-replace-20))
please suggest a better way.
Ehud.
- --
Ehud Karni Tel: +972-3-7966-561 /"\
Mivtach - Simon Fax: +972-3-7966-667 \ / ASCII Ribbon Campaign
Insurance agencies (USA) voice mail and X Against HTML Mail
http://www.mvs.co.il FAX: 1-815-5509341 / \
mailto:ehud@unix.mvs.co.il Better Safe Than Sorry
-----BEGIN PGP SIGNATURE-----
Comment: use http://www.keyserver.net/ to get my key (and others)
iD8DBQE+s6QILFvTvpjqOY0RAv4GAJ0RHsSfJ0aNVElMgYAHDXV5z64BBwCeIAvn
GZvWUHM04ex9P10bz8Clpr8=
=HykV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-05-03 11:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 19:55 [Suggestion] New function `emacs-version>=' Wedler, Christoph
2003-05-02 21:00 ` Juanma Barranquero
2003-05-02 21:14 ` Stefan Monnier
2003-05-02 21:35 ` Juanma Barranquero
2003-05-03 11:12 ` Ehud Karni [this message]
2003-05-03 13:54 ` Juanma Barranquero
2003-05-03 16:08 ` Stephen J. Turnbull
2003-05-04 19:15 ` Juanma Barranquero
2003-05-06 11:05 ` Stephen J. Turnbull
2003-05-04 13:04 ` Richard Stallman
2003-05-03 17:48 ` Reiner Steib
2003-05-03 18:42 ` Stefan Monnier
2003-05-05 13:47 ` sort-coding-systems in 21.3 and RC branch (was: New function `emacs-version>=') Reiner Steib
2003-05-06 7:08 ` Kenichi Handa
2003-05-02 21:16 ` [Suggestion] New function `emacs-version>=' Thien-Thi Nguyen
2003-05-04 13:03 ` Richard Stallman
2003-05-05 12:52 ` Wedler, Christoph
2003-05-05 13:20 ` Juanma Barranquero
2003-05-05 19:11 ` Richard Stallman
2003-05-05 21:59 ` Luc Teirlinck
2003-05-06 23:42 ` Istvan Marko
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=200305031112.h43BC9tL013684@beta.mvs.co.il \
--to=ehud@unix.mvs.co.il \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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).