Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I don't use Textmate....yet. But very cool...
  • I attacked the same problem from a slightly different angle. Assuming I'm already logged in to 'remotehost' via ssh, I want to be able to type:

    vi somefile

    and have the 'right thing' happen automatically. In my case, the right thing is for a message to be sent back to my workstation which responds by opening a GUI editor window using this command:

    gvim scp://remotehost//path/to/somefile

    I used SSH port forwarding to supply the back channel for sending the messages and named the result bcvi - back-ch [perlmonks.org]

  • I use Fugu to navigate over SSH. There's an edit button which loads selected remote file into local text editor (and saving the file puts it automatically back).

    I use TextMate with above and it works like a dream (I believe CyberDuck also as this edit option). Longer term I think MacFuse looks the way to go.

    I can also see smate becoming very useful tool to have available.

    /I3az/
  • BTW, do you have EDITOR=mate in your environment? because you could make it editor-agnostic by just exec'ing $ENV{EDITOR} instead of "mate", which I for one would enjoy ;)

    This is awesome. I like the "bcvi" hack, too; it'd be great if they could merge magically somehow.
    • Yeah, the editor needs a foreground mode and you'd need to know the flags for that, that's the only potential problem.