unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: emacs-devel@gnu.org
Subject: Re: tramp again
Date: Thu, 22 Aug 2002 17:00:03 +0000 (UTC)	[thread overview]
Message-ID: <m17hvJT-000IeIC@localhost> (raw)
In-Reply-To: vafn0re6g6u.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de

   > However, the following:
   >
   >     (find-file
   >      "/multi:ssh:bob@24.161.120.95:ssh:bob@192.168.2.48:/home/bob" nil)
   >
   > `worked but with a problem':  tramp visited both both a multi-hop
   > remote file that I did not seek, ...

   Fascinating.  I have never heard of this behavior.

I figured out what happened.  I don't know whether to call this a
self-generated problem or a user-interface problem.  Probably, it is
best to call it a self-generated problem caused by typing a RET ahead
of time and not realizing that I did that.

I redid the find-file, but this time typed my (rather complicated)
second password correctly and the directory came up properly.

In the earlier attempt, I typed the password to 192.168.2.48 twice
erroneously before succeeding the third time.  What I think now is
that after I typed the password the last time, I also typed an extra
carriage return.  This carriage return was then saved for the 29
seconds that passed before the directory got listed, at which point
the extra carriage return evoked the `dired-advertised-find-file'
command on the ~bob/.alias file.

I can reproduce the problem by typing a second carriage return
immediately after I type the second password.  I can also reproduce
the problem by typing an `e' or an `f' immediately after typing the
RET for my password.

I think this is my problem, not an interface problem:  type-ahead
should occur.  Perhaps it would be a good idea to remind people about
type-ahead in the documentation, if it is not described already.

In this case, I did not realize I had typed ahead. (All I remember of
that attempt is that I made many mistakes when I typed that password;
however, since I can reproduce the problem with a typed-ahead RET,
`e', or `f', I assume that is what I did.)

-- 
    Robert J. Chassell            bob@rattlesnake.com  bob@gnu.org
    Rattlesnake Enterprises       http://www.rattlesnake.com
    Free Software Foundation      http://www.gnu.org   GnuPG Key ID: 004B4AC8

  reply	other threads:[~2002-08-22 17:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-22  1:12 tramp again Miles Bader
2002-08-22  8:13 ` Andreas Schwab
2002-08-22 12:19   ` Robert J. Chassell
2002-08-22 15:55     ` Kai Großjohann
2002-08-22 17:00       ` Robert J. Chassell [this message]
2002-08-22 17:38         ` Kai Großjohann
2002-08-22 15:31 ` Kai Großjohann
2002-08-23  1:36   ` Miles Bader

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=m17hvJT-000IeIC@localhost \
    --to=bob@rattlesnake.com \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).