Live data from Hacker News

Unix as IDE (2012)

sanctum.geek.nz

61–70 of 106 posts

Re: Unix as IDE (2012)

#61
post #46

Earlier quoted context omitted.

I think tmux is overrated, at least when running locally. Tiling WM gets you the same efficient screen layout and keybind driven navigation, and it'll manage also graphical windows that you'll inevitably end up having (like browser). Also you'll avoid any tmux-in-tmux issues if you do connect to remote hosts, and all the terminal features (copypaste, urlgrab, scrolling, search etc) actually will work properly.

> I think tmux is overrated, at least when running locally. Tiling WM gets you the same efficient screen layout and keybind driven navigation Funnily, I have made the opposite path, moving from a tiling WM to tmux into a simple xterm. Tiling wm are overrated, since tmux gives you the same functionality, and you can detach your session easily. What I'm sorely missing is a way to "freeze" all my tmux processes so that…

Seems like a great idea. Lack of persistence bugs me about my i3 / tmux / emacs setup.

Google brings [1] but I haven't tried it yet.

1: https://github.com/tmux-plugins/tmux-resurrect

Re: Unix as IDE (2012)

#62
post #8

I've gotten made fun of because I've said my "IDE" is `tmux` in the past; my typical development environment is a tmux split, where an editor (usually NeoVim, sometimes Emacs) does editing, and the bottom half is a terminal running either a dev server or just the compiler command. It's not perfect, but I like how I can basically swap any component out (except tmux itself).

Compile mode on emacs is pretty sweet. You can bind it to a shell command for a particular major mode and compile from a couple keystrokes. The compile buffer can be interactive (for debugging) which is also pretty sweet ! And Ctrl-g makes the compilation buffer disappear so it's heaven :)

Re: Unix as IDE (2012)

#63

I'm a terminal jockey and an i3 junkie, and for a long time vim+extensions+Unix tools were my IDE too... but ultimately there is a difference between a powerful editor used like an IDE, and an actual IDE. there are lots of features which get first class.attention in an IDE, which were just kludgy hacks in my beloved vim... and some that simply weren't possible. For example, VSCode Remote container development. The ID…

I am this kind of guy, too - i3 + st + vim bindings almost everywhere. But it's a mixed bag, like I can use vim and do something complex in an instant, e.g. replacing a column of characters with something else, but I'm too used to the regular expression replace all mode of vscode. Or the file manager on large projects, I'm pretty much used to using one file at a time with vim. I feel no shame xD

What is `st`? :)

Re: Unix as IDE (2012)

#64

Earlier quoted context omitted.

I am this kind of guy, too - i3 + st + vim bindings almost everywhere. But it's a mixed bag, like I can use vim and do something complex in an instant, e.g. replacing a column of characters with something else, but I'm too used to the regular expression replace all mode of vscode. Or the file manager on large projects, I'm pretty much used to using one file at a time with vim. I feel no shame xD

What is `st`? :)

Probably meant sublime text?

Re: Unix as IDE (2012)

#65

Earlier quoted context omitted.

I am this kind of guy, too - i3 + st + vim bindings almost everywhere. But it's a mixed bag, like I can use vim and do something complex in an instant, e.g. replacing a column of characters with something else, but I'm too used to the regular expression replace all mode of vscode. Or the file manager on large projects, I'm pretty much used to using one file at a time with vim. I feel no shame xD

What is `st`? :)

Not GP, but I suspect they’re referring to this terminal emulator:

https://st.suckless.org/

Re: Unix as IDE (2012)

#66

Earlier quoted context omitted.

I am this kind of guy, too - i3 + st + vim bindings almost everywhere. But it's a mixed bag, like I can use vim and do something complex in an instant, e.g. replacing a column of characters with something else, but I'm too used to the regular expression replace all mode of vscode. Or the file manager on large projects, I'm pretty much used to using one file at a time with vim. I feel no shame xD

What is `st`? :)

terminal emulator by suckless https://st.suckless.org/

Re: Unix as IDE (2012)

#67

Earlier quoted context omitted.

> IntelliJ Editors just straight up not working on Wayland right now has driven me insane Maybe don't use Wayland then. Or, at least, suffer the slings and arrows of outrageous fortune with some grace. You chose to use Wayland, making you a minority (Wayland users) of a minority (Linux users). All power to you to make your own choices, but to paraphrase an old favourite - "Freedom may be mankind’s natural state, but…

If Firefox can pull it off so can Jetbrains. X does not work for mixed dpi and xrandr isn’t a solution. Wayland has been a thing for 15 years. If Apple released a new window system devs would support it why not Linux? Your view is essentially there are starving kids in Africa so you should starve too.

Because there are probably more developers using MacOS and it is officially supported by Apple. Wayland may have been available for 15 years but it isn't defacto (doesn't work with the nvidia driver).

Re: Unix as IDE (2012)

#68
post #46

Earlier quoted context omitted.

I think tmux is overrated, at least when running locally. Tiling WM gets you the same efficient screen layout and keybind driven navigation, and it'll manage also graphical windows that you'll inevitably end up having (like browser). Also you'll avoid any tmux-in-tmux issues if you do connect to remote hosts, and all the terminal features (copypaste, urlgrab, scrolling, search etc) actually will work properly.

> I think tmux is overrated, at least when running locally. Tiling WM gets you the same efficient screen layout and keybind driven navigation Funnily, I have made the opposite path, moving from a tiling WM to tmux into a simple xterm. Tiling wm are overrated, since tmux gives you the same functionality, and you can detach your session easily. What I'm sorely missing is a way to "freeze" all my tmux processes so that…

Rather than freeze them I have a tmuxinator[0] config per project that opens all of the panes and tools I tend to use. Usually something like: editor, extra (often my rails console or database prompt), git, tests, server, logs.

I know the numbers off by heart so can switch without looking.

[0] https://github.com/tmuxinator/tmuxinator

Re: Unix as IDE (2012)

#69

Earlier quoted context omitted.

> I think tmux is overrated, at least when running locally. Tiling WM gets you the same efficient screen layout and keybind driven navigation Funnily, I have made the opposite path, moving from a tiling WM to tmux into a simple xterm. Tiling wm are overrated, since tmux gives you the same functionality, and you can detach your session easily. What I'm sorely missing is a way to "freeze" all my tmux processes so that…

Seems like a great idea. Lack of persistence bugs me about my i3 / tmux / emacs setup. Google brings [1] but I haven't tried it yet. 1: https://github.com/tmux-plugins/tmux-resurrect

yes, but this is a mock-up of a real freeze. What I want is independent of tmux: a way to freeze a process and all its children and save it into a file. The file is then opened when rebooting, or even on a different computer. There was this:

    https://github.com/maaziz/cryopid

Re: Unix as IDE (2012)

#70

I'm a terminal jockey and an i3 junkie, and for a long time vim+extensions+Unix tools were my IDE too... but ultimately there is a difference between a powerful editor used like an IDE, and an actual IDE. there are lots of features which get first class.attention in an IDE, which were just kludgy hacks in my beloved vim... and some that simply weren't possible. For example, VSCode Remote container development. The ID…

I tried VSCode several times, but always came back to vim. I think there is a fundamental difference to a purely terminal based workflow.

Learning a new commandline tool has almost always been something that paid back for years: CLI cares much more about backwards compatibility than a GUI because it's used in shell scripts. And that's another advantage: you are only one step away from automating stuff. A homogeneousness set of keybindings over all applications are just the icing on the cake.

Post reply on HN