From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Andreas Politz <politza@fh-trier.de>, 13677@debbugs.gnu.org
Subject: bug#13677: 24.2.50; workng on remote hosts with eshell is not very enjoyable
Date: Wed, 13 Feb 2013 17:32:30 +0100 [thread overview]
Message-ID: <87sj5041k1.fsf@gmx.de> (raw)
In-Reply-To: <jwva9rbzkeb.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 10 Feb 2013 20:54:32 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> Every stat command starts a new tramp process, which, in my case, takes
>>> about 3-4 seconds to get going and renders eshell fairly useless for
>>> this kind of work.
>
> I think you want to enable "ControlPersist" and/or related options in
> your ~/.ssh/config, so that only the first ssh needs to authenticate and
> subsequent ones just reuse the connection already setup by the first.
I've committed a patch to Tramp to use ControlMaster=auto whenever
possible. This might speed up remote processes a little bit, but most of
the startup time is still spent in Tramp's hand-shaking.
It would be good if we could have a mechanism to say eshell, whether an
external command shall run synchronously or asynchronously. I doubt,
that there will be a clever automatic detection. Eshell cannot know in
advance, wheter an external command is interactive, or not.
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2013-02-13 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 17:25 bug#13677: 24.2.50; workng on remote hosts with eshell is not very enjoyable Andreas Politz
2013-02-10 20:58 ` Michael Albinus
2013-02-11 1:54 ` Stefan Monnier
2013-02-13 16:32 ` Michael Albinus [this message]
2013-02-13 16:55 ` Andreas Politz
2015-02-20 17:01 ` bug#13677: have a second connection for interactive eshell cmds (to avoid long handshaking) Ivan Zakharyaschev
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=87sj5041k1.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=13677@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=politza@fh-trier.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.