in reply to Remote Editing Shell

We're definitely intending to use Term::ReadLine. I'd like to see it act less like an ftp client and more like a buffer space for your favorite unix commands. We'd really like to know what others might have in mind.

Regarless of the implementation, I wanna be able to do a vi -o file1 file2 where file1 and file2 are remote files. I had it in mind to make an ftpfs module for the linux kernel ... That turn'd out to be too damn'd hard. ;)

What kinds of syntax should we use for this?

Replies are listed 'Best First'.
RE (tilly) 2: Remote Editing Shell
by tilly (Archbishop) on Aug 23, 2000 at 02:08 UTC
    My question.

    What about people who want to use Emacs (not me but...), or people who use methods other than ftp (rsync+ssh here!) to connect to remote files?

[reply]
      XEmacs (and probably emacs too) has a very good module called efs available which makes remotes files available through ftp totally transparently.
[reply]

      Well, that's the thing. Our ftp-shell would let you use whatever editor you want. It would even let you cat and grep and perl -e most things. Well, if we can think of a clever enough shell interface. We would definitely buffer the files with Net::FTP... the whole point is that you wouldn't have to think about it as an ftp client. It's a file manipulation shell for remote files.

      Is there even a Net::scp or anything like that? I would happilly do scp support (though our mud doesn't support that) if there were such a thing. Perhaps I should look into authoring Net::scp. I assume one of the ssh's is open source?

[reply]

In Section Seekers of Perl Wisdom