51–59 of 59 posts
Earlier quoted context omitted.
Aside from its well-known features, such as displaying images directly in the terminal over ssh, I use it to create TUI applications. The application is a saved Kitty session, with a defined arrangement of windows. Each window runs a specified program, and communicates with the other windows over a Unix socket. Kitty has a convenient tool to create these sessions. Once created, I can start the session-application lik…
Does session management really belong in the terminal emulator?
if you are thinking of tmux then the problem here is that tmux is in itself a terminal.
to get session management away from the terminal it would need to be done in such a way that when the session tool connects the session it merely acts as a proxy or less, but does not interpret and then translate the signals that come from the session like tmux does.
this is not trivial, at least with the current way terminals work.
we need to entirely rethink the terminal protocol: https://news.ycombinator.com/item?id=47941354
Earlier quoted context omitted.
Can't we just normalise publishing whatever you put into the LLM instead? I'm sure the author typed things into their favourite AI assistant that regurgitated that long form, LLM-speak style version. I'm sure the original prompt has all the relevant content and was a lot more pleasant to read. Can't wait for this style of prose to become an incredibly embarrassing faux-pas.
I think if we want to combat slop we have to be honest about why it happens, and the honest truth is that a blog post whose whole content was "I was only using the terminal and Claude code for a couple hours and it drained my whole battery wtf write me an article about this" would not be gaining traction. Some amount of polish and effort is needed, but we can still avoid the most annoying tropes.
Fucking AI slop
Let me do that now: hmm, this article seems to be a complaint about applications that waste energy.
Earlier quoted context omitted.
> tab-complete, history Those would be handled by your shell, not your terminal, right? > multiplexing If you have a good window manager, then there is no reason to have a bespoke multiplexing implementation in your terminal. I can stack my terminals and _any other window I want_ with tabs and switch between them using the same hotkeys/interface that I use for my whole system, rather than each app implementing their…
Some people frequently or exclusively work on remote systems over ssh. Multiple windows is not an alternative to a multiplexer. They have some overlap in use cases. But it's not 1-1.
Earlier quoted context omitted.
I like what you need to know a bazillion ways to disable all this unnecessary cruft. And people would be angry if you even note what you don't need it. I propose we should have some global switch to on/off these type of things, something like kern.fidget.widget=off or $VANILLA_PUMPKIN_LATTE=BROYEETSURE
kern.fidget.user-has-an-acutal-job-to-get-done
Earlier quoted context omitted.
I think if we want to combat slop we have to be honest about why it happens, and the honest truth is that a blog post whose whole content was "I was only using the terminal and Claude code for a couple hours and it drained my whole battery wtf write me an article about this" would not be gaining traction. Some amount of polish and effort is needed, but we can still avoid the most annoying tropes.
Sounds like a viral Tweet. Why wouldn't it be able to gain traction?
So, my terminal, while it could perhaps improve in its battery usage, does not behave like this.