From: Tassilo Horn <heimdall@uni-koblenz.de>
Subject: Re: Possible Gnus/Emacs 22 Tramp bug?
Date: Mon, 15 May 2006 12:15:32 +0200 [thread overview]
Message-ID: <87odxzmw57.fsf@baldur.nicundtas.de> (raw)
In-Reply-To: <87fyjbagih.fsf@tiger.rapttech.com.au>
Tim X <timx@nospam.dev.null> writes:
Hi Tim,
> I'm guessing your running Debian unstable?
No, Gentoo. But I don't use and prepacked (distribution) snapshots but
get the sources directly from CVS. Those version (0.4 or 22.0.50.1)
numbers don't have a very exact meaning, because they don't change very
often. So it's likely that this bug has already been fixed in CVS, but
the debian snapshots are all too old.
> Actually, now that I think about it, I did an upgrade today to the
> newest emacs-snapshot. I'll have to check to see if the issue has been
> resolved since.
If not, check out the sources directly from CVS.
Bye,
Tassilo
--
A child of five could understand this! Fetch me a child of five!
prev parent reply other threads:[~2006-05-15 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 22:31 Tim X
2006-05-15 7:12 ` Tassilo Horn
[not found] ` <mailman.1814.1147677181.9609.info-gnus-english@gnu.org>
2006-05-15 7:33 ` Tim X
2006-05-15 10:15 ` Tassilo Horn [this message]
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=87odxzmw57.fsf@baldur.nicundtas.de \
--to=heimdall@uni-koblenz.de \
/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).