From: Steve Youngs <sryoungs@bigpond.net.au>
Subject: Re: [PATCH] Trivial itimer tweaks for password.el
Date: Wed, 07 Jan 2004 14:31:18 +1000 [thread overview]
Message-ID: <microsoft-free.8765foidm1.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <m3llok32cn.fsf@quimbies.gnus.org>
[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]
|--==> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> This is with:
LMI> XEmacs 21.4 (patch 6) "Common Lisp" [Lucid] (i386-debian-linux,
LMI> Mule) of Sat Apr 6 2002 on eeyore
LMI> Before running Gnus, `C-h f set-text-properties' returns this:
LMI> `set-text-properties' is a compiled Lisp function
LMI> -- loaded from "/usr/lib/xemacs-21.4.6/lisp/text-props.elc"
LMI> (set-text-properties START END PROPS &optional BUFFER-OR-STRING)
LMI> After starting Gnus, it says this:
LMI> Signaling: (void-function set-text-properties)
[...]
A wee test...
XEmacs 21.4 (patch 14) "Reasonable Discussion" [Lucid] (i586-pc-linux,
Mule) of Sun Dec 21 2003 on eicq
$ xemacs -vanilla
(describe-function 'set-text-properties)
=> `set-text-properties' is a compiled Lisp function
-- loaded from "/usr/local/src/xemacs/lisp/text-props.elc"
(set-text-properties START END PROPS &optional BUFFER-OR-STRING)
(load-user-init-file)
=> nil
(describe-function 'set-text-properties)
=> `set-text-properties' is a compiled Lisp function
-- loaded from "/usr/local/src/xemacs/lisp/text-props.elc"
(set-text-properties START END PROPS &optional BUFFER-OR-STRING)
(gnus)
=> #<network connection "nntpd" ("nntp" . "localhost") state:run>
C-h f set-text-properties RET
=> `set-text-properties' is a compiled Lisp function
-- loaded from "/usr/local/src/xemacs/lisp/text-props.elc"
(set-text-properties START END PROPS &optional BUFFER-OR-STRING)
q
(describe-function 'set-text-properties)
=> `set-text-properties' is a compiled Lisp function
-- loaded from "/usr/local/src/xemacs/lisp/text-props.elc"
(set-text-properties START END PROPS &optional BUFFER-OR-STRING)
LMI> It's pretty bizarre...
Truly. Perhaps update your XEmacs?
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Ashes to ashes, dust to dust. |
| The proof of the pudding, is under the crust. |
|------------------------------<sryoungs@bigpond.net.au>---|
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-01-07 4:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 2:02 Steve Youngs
2004-01-06 3:10 ` Katsumi Yamaoka
2004-01-06 4:15 ` Steve Youngs
2004-01-06 5:18 ` Lars Magne Ingebrigtsen
2004-01-06 5:36 ` Katsumi Yamaoka
2004-01-06 5:47 ` Lars Magne Ingebrigtsen
2004-01-06 5:55 ` Katsumi Yamaoka
2004-01-06 5:57 ` Lars Magne Ingebrigtsen
2004-01-06 6:23 ` Lars Magne Ingebrigtsen
2004-01-06 15:33 ` Steve Youngs
2004-01-07 2:43 ` Lars Magne Ingebrigtsen
2004-01-07 4:31 ` Steve Youngs [this message]
2004-01-07 4:43 ` Lars Magne Ingebrigtsen
2004-01-07 5:42 ` Steve Youngs
2004-01-06 6:30 ` Steve Youngs
2004-01-06 6:33 ` Lars Magne Ingebrigtsen
2004-01-06 9:53 ` Kai Grossjohann
2004-01-06 10:09 ` Katsumi Yamaoka
2004-01-06 11:03 ` Kai Grossjohann
2004-01-07 2:37 ` Lars Magne Ingebrigtsen
2004-01-06 5:23 ` Katsumi Yamaoka
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=microsoft-free.8765foidm1.fsf@eicq.dnsalias.org \
--to=sryoungs@bigpond.net.au \
/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).