From: "Arne Jørgensen" <arne@arnested.dk>
Subject: executable-find moved to files.el in Emacs 22
Date: Fri, 13 May 2005 10:13:25 +0200 [thread overview]
Message-ID: <8764xnk0gq.fsf@arnested.dk> (raw)
[-- Attachment #1: Type: text/plain, Size: 209 bytes --]
Hi,
`executable-find' has just been moved from `executable' to `files' in
Emacs 22.
This patch fixes the two autoloads of `executable-find' in Gnus.
Kind regards,
--
Arne Jørgensen <http://arnested.dk/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: executable-find.patch --]
[-- Type: text/x-patch, Size: 2039 bytes --]
Index: lisp/ChangeLog
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/ChangeLog,v
retrieving revision 7.694
diff -u -p -r7.694 ChangeLog
--- lisp/ChangeLog 9 May 2005 19:18:02 -0000 7.694
+++ lisp/ChangeLog 13 May 2005 08:05:38 -0000
@@ -1,3 +1,10 @@
+2005-05-13 Arne J^[,Ax^[(Brgensen <arne@arnested.dk>
+
+ * dgnushack.el: Autoload `executable-find' from `files' instead of
+ `executable' in Emacs 22.
+
+ * hashcash.el: Ditto.
+
2005-05-09 Simon Josefsson <jas@extundo.com>
* pgg-gpg.el (pgg-gpg-possibly-cache-passphrase): Fix PIN caching,
Index: lisp/dgnushack.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/dgnushack.el,v
retrieving revision 7.16
diff -u -p -r7.16 dgnushack.el
--- lisp/dgnushack.el 26 Jan 2005 08:54:34 -0000 7.16
+++ lisp/dgnushack.el 13 May 2005 08:05:39 -0000
@@ -195,7 +195,9 @@ fixed in Emacs after 21.3."
(autoload 'delete-annotation "annotations")
(autoload 'dolist "cl-macs" nil nil 'macro)
(autoload 'enriched-decode "enriched")
- (autoload 'executable-find "executable")
+ (if (>= emacs-major-version 22)
+ (autoload 'executable-find "files")
+ (autoload 'executable-find "executable"))
(autoload 'font-lock-fontify-buffer "font-lock" nil t)
(autoload 'info "info" nil t)
(autoload 'mail-fetch-field "mail-utils")
Index: lisp/hashcash.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/hashcash.el,v
retrieving revision 7.11
diff -u -p -r7.11 hashcash.el
--- lisp/hashcash.el 16 Jan 2005 10:00:19 -0000 7.11
+++ lisp/hashcash.el 13 May 2005 08:05:39 -0000
@@ -50,7 +50,9 @@
;;; Code:
(eval-and-compile
- (autoload 'executable-find "executable"))
+ (if (>= emacs-major-version 22)
+ (autoload 'executable-find "files")
+ (autoload 'executable-find "executable")))
(defcustom hashcash-default-payment 20
"*The default number of bits to pay to unknown users.
next reply other threads:[~2005-05-13 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 8:13 Arne Jørgensen [this message]
2005-05-13 8:39 ` Katsumi Yamaoka
2005-05-13 8:47 ` Norbert Koch
2005-05-13 9:07 ` Katsumi Yamaoka
2005-05-13 9:26 ` Norbert Koch
2005-05-13 9:34 ` Katsumi Yamaoka
2005-05-13 10:14 ` Norbert Koch
2005-05-13 8:55 ` Arne Jørgensen
2005-05-13 9:27 ` Katsumi Yamaoka
2005-05-13 9:37 ` Katsumi Yamaoka
2005-05-15 20:06 ` Arne Jørgensen
2005-05-16 4:27 ` Katsumi Yamaoka
2005-09-15 8:51 ` Jari Aalto
2005-09-15 9:54 ` Katsumi Yamaoka
2005-09-16 11:16 ` Jari Aalto
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=8764xnk0gq.fsf@arnested.dk \
--to=arne@arnested.dk \
/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 NNTP newsgroup(s).