Earlier quoted context omitted.
Making home read-only can get there, and I can't find the project that forced using XDG paths. I think it used LD_PRELOAD or somesuch trick. edit: https://soc.me/standards/defending-home
Strange. Middle-clicking the link opens a HackerNews frontpage, but copypasting into a new tab shows the article. Presumably the server shoos away referer links? To reduce load maybe somehow? Or maybe something's weird in my own configuration idk.
Show HN: TUI for managing XDG default applications
41–50 of 50 posts
Re: Show HN: TUI for managing XDG default applications
#42Thank god it’s not another React, Solid, Typescript, what have you, web abomination inside the terminal (claude code, opencode, I’m looking at you). Bravo!
Could you elaborate? I mean, I get the usual criticism of web/Electron-based desktop applications (slow, includes a whole Chrome engine, non-native UI, …) but Claude Code isn't one of them?
Re: Show HN: TUI for managing XDG default applications
#43Earlier quoted context omitted.
Making home read-only can get there, and I can't find the project that forced using XDG paths. I think it used LD_PRELOAD or somesuch trick. edit: https://soc.me/standards/defending-home
Strange. Middle-clicking the link opens a HackerNews frontpage, but copypasting into a new tab shows the article. Presumably the server shoos away referer links? To reduce load maybe somehow? Or maybe something's weird in my own configuration idk.
Re: Show HN: TUI for managing XDG default applications
#44Thank god it’s not another React, Solid, Typescript, what have you, web abomination inside the terminal (claude code, opencode, I’m looking at you). Bravo!
> claude code, opencode, I’m looking at you Could you elaborate? I mean, I get the usual criticism of web/Electron-based desktop applications (slow, includes a whole Chrome engine, non-native UI, …) but Claude Code isn't one of them?
tldr; the ui you see in the terminal is react-based in claude code. As for opencode just see their repo on github.
Re: Show HN: TUI for managing XDG default applications
#45Thank god it’s not another React, Solid, Typescript, what have you, web abomination inside the terminal (claude code, opencode, I’m looking at you). Bravo!
> claude code, opencode, I’m looking at you Could you elaborate? I mean, I get the usual criticism of web/Electron-based desktop applications (slow, includes a whole Chrome engine, non-native UI, …) but Claude Code isn't one of them?
Re: Show HN: TUI for managing XDG default applications
#46Earlier quoted context omitted.
That's where codex-cli shines (rust) the startup time is crazy, you can start writing as soon as you hit the command (I don't use codex, just noticed that it's crazy fast)
Sadly the fast startup time is overshadowed by the slow response time of the codex agent
Let them cook as much as they can.
Re: Show HN: TUI for managing XDG default applications
#47Earlier quoted context omitted.
Sadly the fast startup time is overshadowed by the slow response time of the codex agent
I don't get it. Even in ChatGPT I always use Pro model with maxed-out thinking budget (selectors available only on web and windows). Let them cook as much as they can.
Re: Show HN: TUI for managing XDG default applications
#48Earlier quoted context omitted.
> No one on earth has so far managed to get xdg default apps work on Linux. I've only been using Linux for a few weeks but what am I missing here? I set a bunch of mime types in `~/.config/mimeapps.list` which are assigned to desktop apps and they all open perfectly with `xdg-open` or when I launch them through a file manager. It is documented in the XDG specification https://specifications.freedesktop.org/mime-apps/…
> what am I missing here? There are gotchas, for instance Chrom,{e,ium} insists on XDG_DESKTOP_DIR != XDG_DOWNLOAD_DIR. See this bug report from a confused user: https://issues.chromium.org/issues/41076564
Re: Show HN: TUI for managing XDG default applications
#49Re: Show HN: TUI for managing XDG default applications
#50Nice, but problem with all these AI coded TUI's is we will have hundreds of them, best to stick to the built in linux commands, add aliases/abbreviations (fish) if required, do you need a TUI for everything? Sometimes the answer to "Should I write this?" Is no
I absolutely fail to see the problem and I think the whole "best to stick to built in linux commands" is an utterly dinosaur-esque take that can, and will, and should, go extinct in the age of AI-assisted coding.