From: henry atting <henry@literaturlatenight.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Two tramp questions
Date: Wed, 24 Oct 2007 20:44:01 +0200 [thread overview]
Message-ID: <87prz4ic9a.fsf@literaturlatenight.de> (raw)
In-Reply-To: mailman.2516.1193249272.18990.help-gnu-emacs@gnu.org
"Drew Adams" <drew.adams@oracle.com> writes:
>> > I use tramp to edit remote or root files. Although I've read
>> > tramp works well with ido-mode I don't understand it. If ido (or
>> > icicles) is enabled the moment I start typing '/ssh:...' into
>> > the the minibuffer a tramp process is started and dies right
>> > away.
>>
>> This is why I started using iswitchb mode instead. The processes
>> wouldn't die, on the other hand they would be going and tie up the
>> entire Emacs session. That was worse ;) iswitchb-mode works really
>> well: it does not enforce completion in situations like this, only on
>> buffers. I found the file-finding of icicles and ido-mode to just
>> slow me down.
>
> In response to a specific bug report, the Tramp developer (Michael Albinus)
> and I recently worked on making Tramp and Icicles play well together. Ido
> also has a good deal of code that tries to make it get along well with
> Tramp.
>
> It is always better to report a specific bug than to ignore a problem you
> encounter. Even if you don't really care whether something works, others
> might benefit from reporting the problem. Please try the latest version of
> Icicles and let me know if you encounter a problem with Tramp. Thx.
I installed the latest version and it works fine. Great!
Thanks
henry
next parent reply other threads:[~2007-10-24 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2516.1193249272.18990.help-gnu-emacs@gnu.org>
2007-10-24 18:44 ` henry atting [this message]
2007-10-24 20:53 ` Two tramp questions Drew Adams
2007-10-24 14:58 henry atting
2007-10-24 15:23 ` Joel J. Adamson
2007-10-24 18:05 ` Drew Adams
2007-10-24 20:02 ` Peter Dyballa
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=87prz4ic9a.fsf@literaturlatenight.de \
--to=henry@literaturlatenight.de \
--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).