From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Nnslashdot group containing "\w+:\s+\w+" causes error
Date: Fri, 02 Jan 2004 20:38:58 +0100 [thread overview]
Message-ID: <m3lloqb0od.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87hdze1eem.fsf@emptyhost.emptydomain.de>
Kai Grossjohann <kai@emptydomain.de> writes:
> Currently, Tramp uses the same regexes as Ange-FTP used to, I think.
Hey! While I have you here, a Tramp problem: :-)
If I say `C-x f /user@host.somewhere:' it insists on using ssh instead
of ftp.
Debugger entered--Lisp error: (quit)
accept-process-output(#<process *tramp/ssh host.somewhere*> 1)
tramp-wait-for-output()
tramp-handle-expand-file-name("/user@host.somewhere:" nil)
How do I get it to not do that? I mean, without actually reading the
manual?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2004-01-02 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 7:10 Matti Saarinen
2003-12-31 2:27 ` Lars Magne Ingebrigtsen
2004-01-02 16:52 ` Kai Grossjohann
2004-01-02 19:38 ` Lars Magne Ingebrigtsen [this message]
2004-01-03 15:52 ` Kai Grossjohann
2004-01-03 18:47 ` Lars Magne Ingebrigtsen
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=m3lloqb0od.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).