is there a Perl IDE / Editor that supports working on files remotely (via SSH)?
Currently I'm using the shell with vim & nano on the remote machine, and when working locally, I usually use Aptana Studio (Eclipse + EPIC).
p.s: I'm working under linux.
Thanks,
You could mount the remote file system with sshfs then work on it with any local IDE
I've been using Active State's Komodo Edit for the last few years. It's free, cross platform (linux, OSX, windows), can edit over scp or sftp and works well with perl. Active State also make the non-free Komodo IDE that is a more full featured IDE.
Komodo can also do vi emulation, which was a trifecta for me (perl/ssh/vi).
It's not an IDE in the click and drool sense, but Emacs + Tramp is what I use (and these days, Tramp is included with Emacs).
I use Geany via Putty + WinSCP
Related
I'm running a Linux subsystem with an Ubuntu terminal inside Windows 10 - I wanted to make use of the functionalities of both operating systems without partitions or virtual machines.
In an Ubuntu terminal on Linux, I use the command 'code .' to open up the VS Code IDE but it doesn't seem to work when the terminal is part of a subsystem on Windows.
I can open up the IDE from Windows 10 and set my path into the Linux system but I remember reading some guidance that it's okay to save files from the Linux onto the Windows side but not vice versa.
Any solutions are much appreciated, thanks in advance!
If you wish to invoke windows binaries from WSL (Windows Subsystem for Linux) like for the example you want to run visual-studio-code, you can do so by setting your visual-code's installation directory into your %PATH% system variable and invoking it using this way
$ [application-name].exe notice the .exe is important.
And this interoperability is added in the Fall Creator Update of windows.
You can follow this documentation from Microsoft for more help.
In vim 7.3 on OSX, if I type
vim ~/myfiles
vim will put me into the Vim File Explorer for that directory, and I can open or rename files.
In vim 7.4 on Ubuntu, I get the unhelpful error message
"~/myfiles" is a directory
Looking through the compiled options (vim --version) and online documentation, I see no obvious way to activate this functionality through, say, a command-line or compile-time option. It is such a great feature of vim that I'm surprised it is not enabled on the version of vim available in the Linux package.
Use the :E command for the explorer mode.
The ability to edit a directory like this depends on a plugin. Most of the time, that plugin is the "netrw" plugin provided with Vim in the official runtime files. In Ubuntu (and Debian) you install that runtime separately so that every Vim package can use it rather than duplicating functionality. Try installing the vim-runtime package, and maybe a more feature-full Vim while you are at it, if you have not already done so.
To summarize and answer my own question...
File explorer functionality is actually provided by a plug-in, "netrw", which seems not to be installed by default in the two or three versions of vim I tried via apt-get.
Installing NERDTree solved the problem brilliantly - it can do so much more than the default explorer. I have not yet figured out how to rename a file using NERDTree - something that is easy with 'netrw', but that is a minor irritant and there is probably a way to do it.
So, I've been using ubuntu linux for a few months and loved it for my web dev. Everything simply works!
But I switched back to windows because linux sadly doesn't run 90% of my apps :(
So now I have a question, how do you work with git, composer and ssh on windows?
Should I setup a linux virtualbox or is it possible to be able to work comfortably without it?
"TortoiseGit" is a nice extension if you prefer some graphical support, and this needs "msysgit" to give the git commands on windows - which also brings you "git bash" if you prefer the command line. "msysgit" could be installed standalone.
SSH under Windows is always Putty. Grab the newest release 0.63, it has security fixes. To work easily with git then, you need to setup the whole public key authentication with "pageant" running in the background. Putty does a bad job configuring it to convenient levels, you have to manually add it to autostart. Or you could either use KeePass with the KeeAgent plugin to get the same (I prefer it a lot: All authentication stuff in one location).
Executing composer is a question of having installed PHP >= 5.3. If PHP is installed, you execute the alternative install command (without curl) and are nearly ready to go. Having PHP and the composer.phar in the path or add their location to the path eases things a lot.
Caveat: I have no experience with Windows 8 so far, things might be different there. My suggestions are supposed to work on Win 7 at least.
The biggest drawback of Windows is that there is no decent shell support I'd like. Having a virtual machine still is a good idea, but you need your development tools within Windows as well.
I have installed the VisualSVN server on our Windows Server 2008 plus i did connect it with Dreamweaver on other client PC.
so Dreamweaver is ready to go.
But i also want to setup the PHPStorm on other Client PC with that visualSVN.
But i want PHPStorm to use TortoiseSVN to connect to VisualSVN.
I can't find its settings page, i am new to PHPStorm, Especially to this Subversion Control thingy.
I also searched for this over web, but i cant find specific PHPStorm Setup procedure with TortoiseSVN or connecting to VisualSVN Server.
Can anyone Guide me to the Right Path?
The accepted answer is not entirely accurate. It is possible to use TortoiseSVN through PHPStorm's External Tools configurations. This does not integrate into the project navigation directly, but does allow direct file manipulation (and allows for 'blame' support - something PHPStorm's subversion lacks).
Similar functionality is used in eclipse.
Example, paths/macros's might need to be altered:
Name: SVN View Log
Program: C:\Program Files\TortoiseSVN\bin\TortoiseProc.exe
Parameters: /command:log /path:"$FileName$"
Working Directory: $FileDir$
It's impossible to connect PhpStorm to TortoiseSVN as they are doing the same thing.
Then you have two choices :
Connect PhpStorm to your SVN server with his built-in feature.
Or use TortoiseSVN
I'll recommande using PhpStorm feature as it is directly in the IDE.
You can find documentation here : https://www.jetbrains.com/phpstorm/webhelp/using-subversion-integration.html
You can actually do this very easily and it will work inside PHP Storm 8. Install Tortoise SVN and make sure to include "Command Line Tools" as part of the installation. Then you can enable External client and select the "svn.exe" as the executable. This will enable SVN 1.8 format and still work within the IDE.
My solution:
Install TortoiseSVN
Install CollabNet Subversion with command-line binaries (32 or 64-bit)
Open phpStorm
File > Settings > Version Control > Subversion
Set path for your SVN command line client
e.g.
C:\Program Files\CollabNet\Subversion Client\svn.exe
Tortoise can be used as a GUI tool, whereas CollabNet Subversion command line tool can be used with phpStorm. Enjoy!
I use terminal from Mac OS X Leopard to connect to remote Linux machines and edit C++ code there using VI.
What determines that in some machines, using the same MACOSX terminal settings, the source code gets colorized and in other not?
Thanks
Have you used :syntax enable in vim on the remote machine? Just asking, since on the ones that are working it could be in .vimrc or similar.
Usually, the $TERM environment variable determines whether the terminal is capable of color.
$TERM is set upon connection to the remote terminal. From there, you can try export TERM='xterm-color' and see what happens.
Setting the .vimrc with
set term=xterm-color
worked for me in OS X tiger server. I put this at the top of the .vimrc. I also set the term app on OS X El capitan host to xterm in the preferences. I have syntax highlighting over ssh. Thanks again
In my case, these "remote linux machines" usually have a 'small' or 'tiny' version of vim installed which does not have syntax highlighting. When in vim, enter the command :version, and see if you have +syntax or -syntax in the feature list. If you don't have +syntax, then vim has been compiled without syntax support and you need to recompile vim on that machine.