> I've been running emacs 19.34 for decades (its practically
> perfect) I was horrified when my usual method of file
> transfer - ange-ftp - was replaced by tramp
Just set option `tramp-default-method' to `ftp'.
AFAIK, that causes Tramp to pass through to ange-ftp. I don't think you will
see any slowdown, but I'm no expert on this.
Later, when you are more comfortable, you might want to give other methods
(i.e., Tramp per se) a try. And you might even find later that a recent Emacs
version is more convenient and more useful than 19.34. YMMV, though.
Tami <kd5...@wb5aoh.dyndns.org> writes:
> How do I use just ange-ftp for these in-house transfers without disabling the
> ability to use tramp if I ever need it?
As Drew already said, `tramp-default-method' shall preserve your
ange-ftp settings.
> Is tramp actually good for anything useful? If not, how do I disable it
> permanently for myself when using his machines?
> If it is useful, can it be sped up? I've had faster FTP transfers between MIT
> and Finland when the 2 countries were connected by one shared 56k line across
> an ocean! The 2 computers I refer to are 4 feet apart!
Emacs 22 comes with Tramp 2.0, which is way slow. Upgrading to Emacs 23
shall speed up.
There are also lots of settings, which would ease your life (for example
avoiding to type your passwords again and again).
Tramp is useful to access machines which do not run an ftp daemon. It
offers a lot of different access methods, for example you can access
machines running MS Windows, or even Android based cellular phones. (*)
Tramp does more than file transfer. It allows you also to run remote
processes. (*)
> Emacs 22 comes with Tramp 2.0, which is way slow. Upgrading to Emacs 23
> shall speed up.
> There are also lots of settings, which would ease your life (for example
> avoiding to type your passwords again and again).
> Tramp is useful to access machines which do not run an ftp daemon. It
> offers a lot of different access methods, for example you can access
> machines running MS Windows, or even Android based cellular phones. (*)
> Tramp does more than file transfer. It allows you also to run remote
> processes. (*)
> (*): depends on the installed Tramp version.
Thanks for the info.
Tramp may be a useful program to keep on my promiscuous netbook, but
unnecessary for home machines where ftp is enabled behind the firewall. I'll
upgrade the netbook & keep my comfy emacs.
19.34 was the first emacs version GNU ported to M$windoz. In the process it
got thoroughly debugged. In 1998 I used it to access Windoz-2000 machines
(on the same lan) using ange-ftp. I used dired to mark files to transfer.
It all worked seamlessly on my GNU/Linux 350MB laptop.
A decade later I tried an early version of emacs23 hoping to be able to run
packet radio in emacs shell, but the development version was too riddled
with bugs to use. I'm still waiting for emacs23 to appear on a Debian
(stable) distro. (I'm a wait-til-its-stable adopter.)
Meanwhile we're looking at zenirc with an eye to tweaking the code to run
unproto packet radio. Packet is just another chat mode, and TNCs speak modem
to serial ports.
Once I have zenpacket there will be no incentive to upgrade emacs :)
* * *
PS After I sent my query, someone on the list mentioned that they used
screen to maintain local states on multiple machines.
I have been doing this for decades. I have 11 screens on 4 machines, with
each screen devoted to one or 2 remote-local tasks. Its fast and I can
multitask on multiple machines with just a keystroke to switch.
And I still have 6 terminals on my own machine for local tasks!
I really don't need tramp at all except on slut, the promiscuous netbook :)
Glad I asked!
.Tami
.signature: syntax error at line 1: `(' unexpected
On Tue, Feb 7, 2012 at 4:42 PM, Tami <kd5...@wb5aoh.dyndns.org> wrote:
> A decade later I tried an early version of emacs23 hoping to be able to run
> packet radio in emacs shell, but the development version was too riddled
> with bugs to use. I'm still waiting for emacs23 to appear on a Debian
> (stable) distro. (I'm a wait-til-its-stable adopter.)
Emacs 23.2 is in Debian Squeeze, which was released almost exactly one year ago.
-PJ
Gehm's Corrollary to Clark's Law: Any technology distinguishable from
magic is insufficiently advanced.
>> 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).
> Conceptually, too, it's cleaner if each of my (color-coded) text
> windows is acting on a single host.
> TRAMP sounds terrific, but it seems to be meant for a different sort
> of workflow.
Yes. Your work flow works if you have an account on the remote machine, if the machine has emacs, and if the bandwidth and latency are adequate.
If any of these are false, tramp is the solution - pull the file over, edit locally, and send it back when you're done.
I am not an expert linux user. Can someone describe how to apply the gnome patch?
Also regarding the VTE bug report - it claims it is fixed, but I still experience it with libvte9 1:0.28.2-3ubuntu2. I also find that I have another VTE package installed - libvte-2.90-9 build 1:0.32.1-1ubuntu0.
I am not an expert linux user. Can someone describe how to apply the gnome patch?
Also regarding the VTE bug report - it claims it is fixed, but I still experience it with libvte9 1:0.28.2-3ubuntu2. I also find that I have another VTE package installed - libvte-2.90-9 build 1:0.32.1-1ubuntu0.
