From: Steve Youngs <youngs@xemacs.org>
Subject: Re: Latest CVS Gnus just doesn't wanna play fair.
Date: Thu, 02 Aug 2001 00:13:23 +1000 [thread overview]
Message-ID: <microsoft-free.x4snfbamws.fsf@slackware.mynet.pc> (raw)
In-Reply-To: <vafhevvzblo.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sun, 29 Jul 2001 23:09:23 +0200")
|--==> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
KG> On Sun, 29 Jul 2001, Steve Youngs wrote:
>>OK this time I'm certain that the problem _isn't_ my ~/.gnus :-)
>>
>>When composing a mail and trying to move between the mail headers
>>with C-c C-f whatever:
>>
>>Symbol's function definition is void:
>>comint-extract-current-pathname
KG> Very curious. What's the major mode in effect when you do that? What
KG> does C-h c C-c C-f <foo> print?
KG> What does a backtrace produced via M-x set-variable RET debug-on-error
KG> RET t RET look like? The other backtraces you show look really
KG> strange, and I'm not sure whether it's because something strange was
KG> going on, or because I'm not familiar with the XEmacs backtraces you
KG> show.
Hi Kai
I fixed this (although I don't think properly), see my followup to my
original post.
When I get a chance I'll look into it at more depth and fix it
properly.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs@xemacs.org>---|
next prev parent reply other threads:[~2001-08-01 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-29 7:02 Steve Youngs
2001-07-29 21:09 ` Kai Großjohann
2001-08-01 14:13 ` Steve Youngs [this message]
2001-07-30 2:12 ` Steve Youngs
2001-08-08 9:03 ` Didier Verna
2001-08-08 9:43 ` Katsumi Yamaoka
2001-08-08 10:12 ` Didier Verna
2001-08-08 12:21 ` Didier Verna
2001-08-15 1:59 ` Steve Youngs
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.x4snfbamws.fsf@slackware.mynet.pc \
--to=youngs@xemacs.org \
/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).