From: ken <gebser@speakeasy.net>
Cc: GNU Emacs List <help-gnu-emacs@gnu.org>
Subject: Re: tramp 2.1.3 compile funkiness
Date: Fri, 26 Aug 2005 13:17:10 -0400 [thread overview]
Message-ID: <430F4E96.8030407@speakeasy.net> (raw)
In-Reply-To: <nqfyt2mj11.fsf@alcatel.de>
Michael Albinus wrote:
> zl <gebser@speakeasy.net> writes:
>
>
>>Just yesterday compiled tramp. Got a bunch of errors during the
>>compile-- see session copy below. And I've tried all kinds of syntax
>
> As Peter already wrote, this are warnings only. Nasty (we should
> decrease the noise in make), but nothing serious AFAICS.
>
>>and can't get a tramp connection (though I can ssh just fine).
>
> Here we would need more details. Which filename syntax did you apply
> (example)? Are there error messages, or just a hanging Emacs?
[user@host]/filename [=> create (local) subdirectory]
[user@host]:/filename [=> create (local) subdirectory]
[user@host.domain.tld]:/filename [=> create (local) subdirectory]
[user@host.domain.tld]:filename [=> create (local) subdirectory]
/user@host.domain.tld:/path/filename [=> ftp failure]
/[user@host.domain.tld]:~/filename [=> ftp failure]
/[user@host.domain.tld]/path/file [=> create (local) subdirectory]
In the case of the ftp failure message, I'm promted for a password
first, then the ftp failure message comes up. I believe that emacs is
trying to do ange-ftp.
In the case of the "create directory" errors, emacs (I'm guessing) is
trying to create a file on the local machine.
So does anyone know the correct syntax for tramp these days?
tnx,
ken
>
> If you believe you did everything right, you could submit a bug report
> with "M-x tramp-submit-bug". It will contain more information for
> analysis.
>
>>TIA for making my life worth living again... or just getting this
>>working for me.
>
> Best regards, Michael.
>
--
A lot of us are working harder than we want, at things we don't like to
do. Why? ...In order to afford the sort of existence we don't care to live.
-- Bradford Angier
next prev parent reply other threads:[~2005-08-26 17:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 21:38 tramp 2.1.3 compile funkiness zl
2005-08-19 9:08 ` Peter Dyballa
2005-08-22 9:13 ` Michael Albinus
2005-08-26 17:17 ` ken [this message]
2005-08-27 20:14 ` Michael Albinus
2005-09-01 19:04 ` tramp2 not loading (?) (was: Re: tramp 2.1.3 compile funkiness) ken
2005-09-02 7:48 ` tramp2 not loading (?) Michael Albinus
2005-09-02 15:39 ` ken
2005-09-03 10:55 ` Michael Albinus
2005-09-16 11:49 ` tramp " ken
2005-09-16 14:39 ` Michael Albinus
2005-09-16 15:44 ` Kevin Rodgers
2005-09-17 13:29 ` tramp not loading (?)... ftp session instead ken
[not found] ` <mailman.7299.1126885772.20277.help-gnu-emacs@gnu.org>
2005-09-16 19:27 ` tramp not loading (?) Chris McMahan
2005-09-16 20:14 ` Drew Adams
2005-09-16 20:25 ` Enila Nero
2005-09-18 9:37 ` Michael Albinus
[not found] ` <mailman.5157.1125078882.20277.help-gnu-emacs@gnu.org>
2005-08-26 19:54 ` tramp 2.1.3 compile funkiness rgb
2005-09-15 22:41 ` rgb
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=430F4E96.8030407@speakeasy.net \
--to=gebser@speakeasy.net \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).