10 ms·

VSCode/Atom are great, but for most folks on UNIX they are worthless, since you have to use something else when ssh-d into another machine. So folks build these

VSCode/Atom are great, but for most folks on UNIX they are worthless, since you have to use something else when ssh-d into another machine. So folks build these elaborate Vim and EMACS set-ups so that they could use the same editor and the same config on all of their machines, whether they're local or remote. Vim is an acquired taste, but once acquired, it's pretty awesome.

nwatson 10y ago
Why not just run PyCharm on your local box and tunnel-via-SSH-and-pydevd to remote-debug your programs on the target system? You get (a) a full IDE running on your local system (no need to install anything on target system); (b) full debugging and breakpoints; (c) your choice of any "real" or "virtualenv" Python deployment on the target machine. Downsides are that your own source code on the local and remote systems need to match (for your step-through-code to make sense), and you need to set up mappings between directories with source code on the local and remote systems -- but that's a low cost for full visibility into how your program runs on the target system.
- michaelmrose 10y ago
  You could mount the remote machines filesystem over ssh with sshfs. https://wiki.archlinux.org/index.php/SSHFS https://wiki.archlinux.org/index.php/SSHFS
semaphoreP 10y ago
I use supercomputers which only have a terminal interface. I found it was easier to do most of the development of the code on my machine with a GUI (e.g. Pycharm or VSCode) and then push code to the cluster for production runs. I use vim for minor adjustments, but it seemed way easier to just push code rather than configuring vim when something like VSCode is so much easier to get set up.
- general_ai 10y ago
  Thing is, you only need to configure Vim once, and then use your version controlled config everywhere for 10 years, very gradually improving it. I doubt VSCode will even exist in 10 years.
  - oblio 10y ago
    Are any of your plugins from 10 years ago still around? You can't compare naked Vim with VSCode. Also, Visual Studio has been around since 1997 and there's no reason to assume, out of hand, that VSCode won't last as long, being both popular and Open Source. I'm a Vim user, but cut the FUD.
    - falcolas 10y ago
      > Are any of your plugins from 10 years ago still around? Ctrlp, python (the filetype plugin), vimwiki... most of them honestly. > You can't compare naked Vim with VSCode. If you're doing C programming, it's probably close to equivalent out of the box. For Python development, you'll want to at least get the Python plugins; but you'll be doing that in most editors. IMO, VSCode is interesting, but it's not that spectacular if you've been using any form of IDE (or a decent text editor with plugins). That is, it doesn't offer any major advantages over the other editors.
    - general_ai 10y ago
      I'm pretty sure they'll still be around. They're all open source.
  - maccard 10y ago
    I don't even need to configure Visual Studio, and it's been around for 20 years.
therealmarv 10y ago
Well this is your use case. I use Linux every day but I never touch python code directly on remote systems (it's getting automatically or manually deployed). All my python code lives in virtualenv locally here. But I understand when people work for many projects they maybe want to encapsulate it more (vagrant etc.).
- general_ai 10y ago
  I prefer console in general, for everything. I've been doing this for 20+ years, and you can pry it from my cold, dead hands.
  - dotancohen 10y ago
    I've only been coding for 11 years professionally, but also as a hobby before that. Only in 2016 did I move most of my work out of VIM into an IDE: the Jetbrains family. That mostly started for better interactive debugging, but with IDEAVim handling 95% of my VIMisms I find that I'm simply coding in PyCharm and PhpStorm by default now. The base editor is open source but you can get the full PyCharm for $99 per year. Worth every cent.
    - Arizhel 10y ago
      I've used PyCharm. The editing feature is beyond useless to me, because it does not have vim key bindings. How am I supposed to cut and paste code when commands like "y}" don't work? You actually expect me to use a mouse to select things or move the cursor? Ridiculous. The only thing I've found PyCharm good for is doing other functions, like linting, not for the actual code editing. No IDE is any good for that. Luckily, PyCharm works just fine when the code it's working with changes on the filesystem below it because of the use of an external editor.
      - xbrother 10y ago
        There is VIM plug-in for Intellij family IDEs. It covers the great part of VIM functionality. It even supports some sort of VIM configs. "y}" works fine, as well as "yi{".
jhoechtl 10y ago
VSCode seems to be great, Atom is mediocre and that is polite.
- no_wizard 10y ago
  I know atom is easy to slow down with tons of plugins and extensions but why does it have a bad wrap? I am just curious because I've seen this sentiment but I find Atom has an amazing ecosystem of plugins it's not the editor for me mostly cause I came into it with Sublime that is what I personally like and now recently spacemacs but I'm curious
lqdc13 10y ago
Modern GNU/linux filemanagers support connecting to ssh server and browse and open and edit files just like they are local. You can do it in two seconds. In ubuntu it's file -> connect to server -> type in ssh://username@ip That's it you are done. You can now browse the files as if they are local and use sublime/gedit/VSCode/Pycharm/whatever you want
- therealmarv 10y ago
  I like this answer. For everyone who wants to do this by commandline: Search for sshfs and FUSE (also possible on Mac with osxfuse). Only be aware that a mac uses a different kind of utf-8 than unix. My command I use for sshfs on a mac: sshfs -o Ciphers=aes128-gcm@openssh.com -o Compression=no -o reconnect \ -o modules=iconv,from_code=utf-8,to_code=utf-8-mac \ myremote:/somedirectory/ /mylocalmountdir
  - Gorgor 10y ago
    I'm not familiar with Macs. How is their UTF-8 different from the normal one? How is such a thing even possible?
    - therealmarv 10y ago
      I also thought the same, you would not recognize it most of the time (even while transferring). But I'm german and I use sometimes Umlauts in filenames/directories. They did not showed up in my Samba share so I got aware of this issue. I think this issue is too hidden. If you want to read about this topic: rsync: http://askubuntu.com/questions/533690/rsync-with-special-character-files-not-working-between-mac-and-linux/540960 http://askubuntu.com/questions/533690/rsync-with-special-cha... sshfs: https://github.com/osxfuse/sshfs/issues/14 https://github.com/osxfuse/sshfs/issues/14
Bedon292 10y ago
Plugins like https://atom.io/packages/remote-edit https://atom.io/packages/remote-edit allow you to directly edit your remote code while still in the GUI. I still mostly use VIM, but its a nice alternative.
segmondy 10y ago
I have 20+ yrs of using vim. Tried numerous times to switch to emacs, I started using VSCode and love it. It's not useless, my vim skills is still handy. Logging in to servers to hotfix thing is no longer something to brag about. Cattle not pets. If I really need to login to a server to edit something, I don't need a fancy .vimrc. I don't code live on prod.

nwatson 10y ago

Why not just run PyCharm on your local box and tunnel-via-SSH-and-pydevd to remote-debug your programs on the target system? You get (a) a full IDE running on your local system (no need to install anything on target system); (b) full debugging and breakpoints; (c) your choice of any "real" or "virtualenv" Python deployment on the target machine. Downsides are that your own source code on the local and remote systems need to match (for your step-through-code to make sense), and you need to set up mappings between directories with source code on the local and remote systems -- but that's a low cost for full visibility into how your program runs on the target system.

michaelmrose 10y ago
You could mount the remote machines filesystem over ssh with sshfs. https://wiki.archlinux.org/index.php/SSHFS https://wiki.archlinux.org/index.php/SSHFS

semaphoreP 10y ago

I use supercomputers which only have a terminal interface. I found it was easier to do most of the development of the code on my machine with a GUI (e.g. Pycharm or VSCode) and then push code to the cluster for production runs. I use vim for minor adjustments, but it seemed way easier to just push code rather than configuring vim when something like VSCode is so much easier to get set up.

general_ai 10y ago
Thing is, you only need to configure Vim once, and then use your version controlled config everywhere for 10 years, very gradually improving it. I doubt VSCode will even exist in 10 years.
- oblio 10y ago
  Are any of your plugins from 10 years ago still around? You can't compare naked Vim with VSCode. Also, Visual Studio has been around since 1997 and there's no reason to assume, out of hand, that VSCode won't last as long, being both popular and Open Source. I'm a Vim user, but cut the FUD.
  - falcolas 10y ago
    > Are any of your plugins from 10 years ago still around? Ctrlp, python (the filetype plugin), vimwiki... most of them honestly. > You can't compare naked Vim with VSCode. If you're doing C programming, it's probably close to equivalent out of the box. For Python development, you'll want to at least get the Python plugins; but you'll be doing that in most editors. IMO, VSCode is interesting, but it's not that spectacular if you've been using any form of IDE (or a decent text editor with plugins). That is, it doesn't offer any major advantages over the other editors.
  - general_ai 10y ago
    I'm pretty sure they'll still be around. They're all open source.
- maccard 10y ago
  I don't even need to configure Visual Studio, and it's been around for 20 years.

therealmarv 10y ago

Well this is your use case. I use Linux every day but I never touch python code directly on remote systems (it's getting automatically or manually deployed). All my python code lives in virtualenv locally here. But I understand when people work for many projects they maybe want to encapsulate it more (vagrant etc.).

general_ai 10y ago
I prefer console in general, for everything. I've been doing this for 20+ years, and you can pry it from my cold, dead hands.
- dotancohen 10y ago
  I've only been coding for 11 years professionally, but also as a hobby before that. Only in 2016 did I move most of my work out of VIM into an IDE: the Jetbrains family. That mostly started for better interactive debugging, but with IDEAVim handling 95% of my VIMisms I find that I'm simply coding in PyCharm and PhpStorm by default now. The base editor is open source but you can get the full PyCharm for $99 per year. Worth every cent.
  - Arizhel 10y ago
    I've used PyCharm. The editing feature is beyond useless to me, because it does not have vim key bindings. How am I supposed to cut and paste code when commands like "y}" don't work? You actually expect me to use a mouse to select things or move the cursor? Ridiculous. The only thing I've found PyCharm good for is doing other functions, like linting, not for the actual code editing. No IDE is any good for that. Luckily, PyCharm works just fine when the code it's working with changes on the filesystem below it because of the use of an external editor.
    - xbrother 10y ago
      There is VIM plug-in for Intellij family IDEs. It covers the great part of VIM functionality. It even supports some sort of VIM configs. "y}" works fine, as well as "yi{".

jhoechtl 10y ago

VSCode seems to be great, Atom is mediocre and that is polite.

no_wizard 10y ago
I know atom is easy to slow down with tons of plugins and extensions but why does it have a bad wrap? I am just curious because I've seen this sentiment but I find Atom has an amazing ecosystem of plugins it's not the editor for me mostly cause I came into it with Sublime that is what I personally like and now recently spacemacs but I'm curious

lqdc13 10y ago

Modern GNU/linux filemanagers support connecting to ssh server and browse and open and edit files just like they are local. You can do it in two seconds. In ubuntu it's file -> connect to server -> type in ssh://username@ip That's it you are done. You can now browse the files as if they are local and use sublime/gedit/VSCode/Pycharm/whatever you want

therealmarv 10y ago
I like this answer. For everyone who wants to do this by commandline: Search for sshfs and FUSE (also possible on Mac with osxfuse). Only be aware that a mac uses a different kind of utf-8 than unix. My command I use for sshfs on a mac: sshfs -o Ciphers=aes128-gcm@openssh.com -o Compression=no -o reconnect \ -o modules=iconv,from_code=utf-8,to_code=utf-8-mac \ myremote:/somedirectory/ /mylocalmountdir
- Gorgor 10y ago
  I'm not familiar with Macs. How is their UTF-8 different from the normal one? How is such a thing even possible?
  - therealmarv 10y ago
    I also thought the same, you would not recognize it most of the time (even while transferring). But I'm german and I use sometimes Umlauts in filenames/directories. They did not showed up in my Samba share so I got aware of this issue. I think this issue is too hidden. If you want to read about this topic: rsync: http://askubuntu.com/questions/533690/rsync-with-special-character-files-not-working-between-mac-and-linux/540960 http://askubuntu.com/questions/533690/rsync-with-special-cha... sshfs: https://github.com/osxfuse/sshfs/issues/14 https://github.com/osxfuse/sshfs/issues/14

Bedon292 10y ago

Plugins like https://atom.io/packages/remote-edit https://atom.io/packages/remote-edit allow you to directly edit your remote code while still in the GUI. I still mostly use VIM, but its a nice alternative.

segmondy 10y ago

I have 20+ yrs of using vim. Tried numerous times to switch to emacs, I started using VSCode and love it. It's not useless, my vim skills is still handy. Logging in to servers to hotfix thing is no longer something to brag about. Cattle not pets. If I really need to login to a server to edit something, I don't need a fancy .vimrc. I don't code live on prod.