From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Tassilo Horn <tsdh@gnu.org>,
Andreas Schwab <schwab@linux-m68k.org>,
20015@debbugs.gnu.org
Subject: bug#20015: 25.0.50; Slow Emacs startup after recent TRAMP changes
Date: Mon, 09 Mar 2015 22:11:13 +0100 [thread overview]
Message-ID: <87egox6fm6.fsf@gmx.de> (raw)
In-Reply-To: <jwvpp8idby9.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Mon, 09 Mar 2015 00:41:57 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> only 3 times, and it is called only when you open a remote file
>> (tramp.el is loaded).
>
> Loading tramp.el does not guarantee we want to open a remote file (it
> could be a local file via /su: for example).
Yes. In Emacs 25, I intend to delay evaluation of the code until it is
really needed. (As usual, it will take some days; I'm too busy in real life).
>> I would like to avoid these calls completely, if somebody could tell me
>> a robust test for knowing which kind of ControlMaster, ControlPath and
>> ControlPersist options are supported by the local ssh stanza. And no, I
>> don't want to check the ssh version; this isn't robust.
>
> I like using "" for tramp-ssh-controlmaster-options, FWIW ;-)
>
> FWIW, I find that for OpenSSH on Debian, "ssh -o
> <optionname>=<optiovalue>" never waits and gives different outputs
> ("command-line: line 0: Bad configuration option: <optionname>",
> "command-line line 0: unsupported option <optionvalue>", or the help
> text). Not sure if it's robust for other systems and other versions of ssh.
That's what I do when checking ControlMaster and ControlPersist. But the
check for ControlPath=%C requires also a hostname, unfortunately.
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2015-03-09 21:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 6:23 bug#20015: 25.0.50; Slow Emacs startup after recent TRAMP changes Tassilo Horn
2015-03-06 8:29 ` Michael Albinus
2015-03-06 8:53 ` Tassilo Horn
2015-03-06 9:23 ` Michael Albinus
2015-03-06 12:39 ` Tassilo Horn
2015-03-06 13:45 ` Ivan Shmakov
2015-03-06 14:38 ` Andreas Schwab
2015-03-06 14:57 ` Tassilo Horn
2015-03-06 16:43 ` Andreas Schwab
2015-03-06 18:05 ` Stefan Monnier
2015-03-06 19:17 ` Andreas Schwab
2015-03-06 22:34 ` Daniel Colascione
2015-03-06 22:45 ` Daniel Colascione
2015-03-07 11:35 ` Michael Albinus
2015-03-07 12:17 ` Eli Zaretskii
2015-03-07 20:08 ` Michael Albinus
2015-03-09 4:41 ` Stefan Monnier
2015-03-09 21:11 ` Michael Albinus [this message]
2015-03-15 15:14 ` Michael Albinus
2015-03-16 15:24 ` Stefan Monnier
2015-03-16 19:20 ` Michael Albinus
2015-03-16 19:31 ` Tassilo Horn
2015-03-17 9:21 ` Michael Albinus
2015-03-07 2:34 ` Stefan Monnier
2015-03-06 19:51 ` Tassilo Horn
2015-03-06 20:07 ` Andreas Schwab
2015-03-06 20:08 ` Tassilo Horn
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=87egox6fm6.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=20015@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.org \
--cc=tsdh@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).