Live data from Hacker News

A terminal-based workflow for research, writing, and programming

jacobzelko.com

121–125 of 125 posts

Re: A terminal-based workflow for research, writing, and programming

#121
post #99

Earlier quoted context omitted.

> It just takes time but it's worth it in my humble opinion. But why? Because I have a better scripting language? Are there more benefits beyond having lisp?

That's really gonna come down to your workflow and use cases. For me, the Lisp is a bit more welcoming than VimScript for me. It's much easier to test out a small snippet of something in-buffer which might grow into something else. But, putting Lisp aside, going through the growing pains was worth it for me because of org-mode. I'm certain Vim might have something similar but the proper `org` package is definitely on…

You can use lua with neovim for init.lua https://github.com/neovim/neovim/issues/7895#issuecomment-73...

Re: A terminal-based workflow for research, writing, and programming

#122
post #81
post #73

Earlier quoted context omitted.

Tmux is great for persistence. It’s also basically required for working remotely. Allows you to, across sessions, to reconnect to the same flow. I have it set up to have multiple views of the same set of windows, so I can scroll through them independently. I’d say it is one of the best utilities I use.

Mosh supports roaming. Or are you referring to something else about reconnecting?

Tmux allows you to set up several windows and programs in a session (or multiple tmux sessions at once, like virtual desktops), detach from tmux, disconnect SSH, and when you SSH back in a week later, just "tmux attach" to get back to where you were. Also works if your connection drops in the middle of something.

Re: A terminal-based workflow for research, writing, and programming

#123

At risk of being /that guy/, I find that emacs gives me a nice & consistent "one-stop-shop" for text-based apps instead of having to kludge together a bunch disparate terminal programs. Also, +1 for Julia.

To "kludge together a bunch of disparate terminal programs" is not conceptually different than "kludge together a bunch of disparate elisp functions". Some of us live inside the command line, some of us live inside emacs, most of us live inside a web browser.

I was referring to the consistency of the user interface and other behaviours. For example, themes and key bindings can be made consistent across emacs modes. They share the same config.

Re: A terminal-based workflow for research, writing, and programming

#124

There's a lot of really good stuff in here about quick access to things. I feel sad that we're all still doing this stuff in teletype emulators, though. Why can't we have this and nice GUIs, too?

You don't have to use the terminal for fast workflows.

- Many programs offer intuitive quick-action- or quick-search-fields. For example: double-shift in IntelliJ or CMD-Shift-O in many Mac apps like Fork, Things and IA-Writer. - System wide search tools like Alfred and Launchbar will allow you to quickly access Files and execute Workflows - _Every_ Menubar in MacOS is searchable. Just press a shortcut and type what you want to do. - ...and let's not forget that keyboard shortcuts exist.

The great thing is that you get all the power of a keyboard workflow, without losing the accessibility of a GUI.

Re: A terminal-based workflow for research, writing, and programming

#125

Having a terminal-based workflow is a lifesaver in the era of work from home. When using a terminal based workflow I cannot tell the difference between working locally and working on a machine I have SSH'ed into located at my office (10ms round trip ping). Even when I VPN into work, ssh into a box at work, then ssh to a jumpbox in AWS, and then ssh from the jumpbox to an EC2 server the experience is still flawless.

It also makes development using a mobile phone possible. The Termux environment on my Android phone is identical to what I have on my work laptop.
Post reply on HN