From: Jesper Harder <harder@myrealbox.com>
Subject: Re: detect emacs/xemacs in elisp?
Date: Mon, 09 Dec 2002 19:52:48 +0100 [thread overview]
Message-ID: <m365u36n3z.fsf@defun.localdomain> (raw)
In-Reply-To: 49e2e83d.0212091030.7c05b32@posting.google.com
jason_addison@hotmail.com (Jason Addison) writes:
> I have some elisp that works/doesn't work in emacs/xemacs in my
> ".emacs" file. I would like to be able to execute or not execute code
> depending on which type of emacs I'm running.
(if (featurep 'xemacs)
(progn
;; do Xemacs stuff
)
;; do Emacs stuff
)
> Another way around this would be to know how to determine if a
> function is defined before calling it. Any idea on how to do this in
> elisp?
Use `fboundp' to determine if a function is defined.
> Also, how do you determine the version of emacs that is running in
> elisp?
E.g the function `emacs-version'.
next prev parent reply other threads:[~2002-12-09 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 18:30 detect emacs/xemacs in elisp? Jason Addison
2002-12-09 18:52 ` Jesper Harder [this message]
2002-12-09 21:57 ` Tim X
2002-12-09 22:19 ` Benjamin Lewis
2002-12-10 0:50 ` Stefan Monnier <foo@acm.com>
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=m365u36n3z.fsf@defun.localdomain \
--to=harder@myrealbox.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).