On 10 Mar 2001, Daniel Pittman wrote:
Directory aliases can be done trivially using environment variable
substitutions, I think. Does this do what you need:
(setenv "src" "/local/dev/tlroche")
C-x C-f /.../$src/Score...
I think it even works to say
(setenv "remote"
"/r@sm:[EMAIL
On 09 Mar 2001, Daniel Pittman wrote:
Hrm. I will add it to the tramp2 todo list because of the
compatibility needs with tramp1. I don't know how soon it will be
working, though.
IMVHO it's not necessary to try too hard to make the filename syntax
be compatible with the old one. After all,
Presuming TRAMP2 is still wish-list-able, could I suggest what might
be a feature?
I work with several servers, more than a few of which have ungodly
long user/host/paths: e.g.
[EMAIL PROTECTED]:/local/dev/tlroche/webassign/v4
PuTTY, like many FTPs, has a nice feature whereby one can save the
the protocol anyhow...
In any case, I don't think it's a bad idea. Grab the tramp2 sources and
look at the construction of the file-names as is. Then make a suggestion
about exactly what to use there. :)
Directory aliases can be done trivially using environment variable
substitutions, I think. Does
internally.
I think that having different possible styles of file names is a good
thing. That way, we can experiment practically with them, and hopefully
find a sort of consensus about which one is better.
I mentioned mc because it has a similar problem as us, and it solved it.
A syntax like
On Mon, 05 Mar 2001, Francesco Potorti` wrote:
The midnight commander uses this sort of file names:
/#sh:[user@]machine[:options]/[remote-dir]
I wonder what the beginning means? Does "/#sh:" mean it's to be
fetched via ssh? And are there other "/#" filenames?
On 07 Mar 2001, Kai Grojohann wrote:
On Mon, 05 Mar 2001, Francesco Potorti` wrote:
The midnight commander uses this sort of file names:
/#sh:[user@]machine[:options]/[remote-dir]
I wonder what the beginning means? Does "/#sh:" mean it's to be
fetch
The midnight commander uses this sort of file names:
/#sh:[user@]machine[:options]/[remote-dir]
I've been thinking about default login names. Right now, deep down in
the bowels of rcp.el, every file name with a missing login name is
rewritten to put in the local user name instead.
I was thinking of allowing nil as user name everywhere, with the
semantics that the user name
It wouldn't properly quote the special characters when copying files.
Hope this is fixed now.
ftp://ls6-ftp.cs.uni-dortmund.de/pub/src/emacs/rcp.el
kai
--
Abort this operation? [Abort] [Cancel]
10 matches
Mail list logo
