From: S Boucher <stbya@yahoo.com>
To: Perry Smith <pedzsan@gmail.com>,
help-gnu-emacs List <help-gnu-emacs@gnu.org>
Subject: Re: Upgrading suggestions
Date: Tue, 4 Oct 2011 13:32:16 -0700 (PDT) [thread overview]
Message-ID: <1317760336.80462.YahooMailNeo@web161610.mail.bf1.yahoo.com> (raw)
In-Reply-To: <C0729F91-44CC-4A84-B773-296A4579180D@gmail.com>
----- Original Message -----
> How do others, when moving up to a new level of emacs, deal with this?
I add tests based on emacs-major-version and emacs-minor-version. For example, if I overwrite/clobber a particular defun (like I've done for vc-git), I add a check on the version that will throw me an error if I run in a version of emacs I've yet to use. This way, I know I have to go back and review whether I still need the hack or not.
(if (not (and (= emacs-major-version 23) (= emacs-minor-version 2)))
(error "....")
(defun ....))
next prev parent reply other threads:[~2011-10-04 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 17:28 Upgrading suggestions Perry Smith
2011-10-04 18:09 ` Jambunathan K
2011-10-04 20:32 ` S Boucher [this message]
2011-10-06 19:19 ` Ken Goldman
[not found] <mailman.5127.1317749352.939.help-gnu-emacs@gnu.org>
[not found] ` <87fwj8tadw.fsf@notengoamigos.org>
[not found] ` <j82j09$fun$3@reader1.panix.com>
2011-10-24 3:38 ` Jason Earl
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=1317760336.80462.YahooMailNeo@web161610.mail.bf1.yahoo.com \
--to=stbya@yahoo.com \
--cc=help-gnu-emacs@gnu.org \
--cc=pedzsan@gmail.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.
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).