From: Tassilo Horn <tassilo@member.fsf.org>
To: Silvio Levy <levy@msri.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Keybindings for Emacs with no X?
Date: Fri, 03 Feb 2012 22:06:13 +0100 [thread overview]
Message-ID: <87y5sjmxtm.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <20120203205256.0538F180323@neo.msri.org> (Silvio Levy's message of "Fri, 03 Feb 2012 12:52:55 -0800")
Silvio Levy <levy@msri.org> writes:
>> Yes, X11 forwarding is clearly not the way to go. But why not open
>> files on the remote server using TRAMP which comes with emacs?
>
> In my case, the answer is that editing files is only part of what I do
> remotely. I keep an ssh window open on the remote host anyway; it
> makes little sense to then use a *local* invocation of emacs to open a
> remote file (with the corresponding overhead of transfer protocols,
> mimencode and all that jazz).
Yes, I frequently keep a TRAMP dired or shell buffer open on remote
hosts. In such a buffer, even completion after C-x C-f defaults to the
remote directory of the dired current buffer or the shell buffers cwd.
> Conceptually, too, it's cleaner if each of my (color-coded) text
> windows is acting on a single host.
You could use one frame per host, and also have the frames colored
differently. But I don't want to evangelize anyone. I was just curious
why many experienced emacs users don't use TRAMP. In my experience, it
enormously matured over the last years from a slow and flaky
implementation of a good idea to a highly usable and convenient tool.
Bye,
Tassilo
next prev parent reply other threads:[~2012-02-03 21:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 20:52 Keybindings for Emacs with no X? Silvio Levy
2012-02-03 21:06 ` Tassilo Horn [this message]
2012-02-13 15:21 ` Ken Goldman
[not found] <mailman.3017.1328246410.15002.help-gnu-emacs@gnu.org>
2012-10-04 19:23 ` gtassone
-- strict thread matches above, loose matches on Subject: below --
2012-02-03 20:09 Silvio Levy
2012-02-03 22:54 ` Angel de Vicente
2012-02-03 4:38 Angel de Vicente
2012-02-03 7:10 ` Bob Proulx
2012-02-03 7:33 ` 郭晓峰
2012-02-03 7:47 ` Philipp Haselwarter
2012-02-03 9:44 ` Angel de Vicente
2012-02-03 9:42 ` Angel de Vicente
2012-02-03 18:30 ` 郭晓峰
2012-02-03 9:40 ` Angel de Vicente
2012-02-03 19:53 ` Bob Proulx
2012-02-04 0:10 ` Angel de Vicente
2012-02-28 18:40 ` Oleksandr Gavenko
2012-02-28 18:32 ` Oleksandr Gavenko
2012-02-03 7:48 ` Tassilo Horn
2012-02-03 9:47 ` Angel de Vicente
2012-02-03 12:25 ` Peter Dyballa
2012-02-03 20:03 ` Tassilo Horn
2012-02-03 22:09 ` Peter Dyballa
2012-02-03 7:50 ` Jiaxin Cao
2012-02-03 19:58 ` Bob Proulx
2012-02-03 20:12 ` Tassilo Horn
2012-02-03 20:37 ` Bob Proulx
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=87y5sjmxtm.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=help-gnu-emacs@gnu.org \
--cc=levy@msri.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).