Live data from Hacker News

Superfile – A fancy, pretty terminal file manager

github.com

171–180 of 219 posts

Re: Superfile – A fancy, pretty terminal file manager

#171
post #65
post #56

Earlier quoted context omitted.

Is it though? I can run Windows programs from 20 years ago on my Windows machine just fine. Issues with Linux binary distribution meanwhile are ubiquitous, with glibc probably being the single biggest offender. What's worse is that you can't even really statically link it without herculean effort. I've spent an inordinate amount of my life trying to wrangle third-party binaries on Linux libraries and it's just a sorr…

You are talking about backward compatibility, the parent thread is about forward compatibility. You won't have much luck running a modern executable on XP unless the vendor went out of their way to make that happen. > What's worse is that you can't even really statically link it without herculean effort. The program we are discussing happens to be written in Go so it's trivial to build a statically linked executable.

Are you sure you want glibc statically linked into your go executable ?

Re: Superfile – A fancy, pretty terminal file manager

#172

Earlier quoted context omitted.

Nerd Fonts contain glyphs that allow things like the git strip you see at the bottom of code editors ("powerline"), along with ligatures (e.g. if you type https://www.nerdfonts.com/ And here's an example of ligatures (see the image on the right - you type what's on the left, and the right image is what shows in your editor): https://hilton.org.uk/blog/fira-code I think but am not sure as I haven't looked in a while,…

Are there any terminals that ship with nerd fonts, or is it always something that has to be at the OS level? Is there any technical reason the font can't be shipped in the binary and installed automatically?

On Linux you can just chuck fonts in .local/share/fonts in your home directory. You can keep them in folders in there so just unzip the whole nerdfont archive there.

Re: Superfile – A fancy, pretty terminal file manager

#173

superfile looks great, we have this listed on the trove (1) for other package managers, we love what's been done recently in the terminal / tui space. I encourage also supporting the author as well on their ko-fi page for a new laptop. (2) 1. https://terminaltrove.com/superfile/ 2. https://ko-fi.com/night_cat

Thanks for the terminal trove tip ! Subscribed.

I feel the market is ripe for a terminal ide again. Anything interesting going in in that space?

Re: Superfile – A fancy, pretty terminal file manager

#174
post #77

Earlier quoted context omitted.

[flagged]

GUIs aren’t composable with other tools easily. Like, you can pipe CLIs together, and some TUIs accept a command and exit, allowing you to chain things together. On the web, your best bet might be playwright, but that’s about it. Imagine having GTK and QT applications able to be chained and exit automatically. On MacOS/iOS it’s not much better, even if Apple Shortcuts can feel ok sometimes, assuming the devs thought…

Shortcuts is trash but Automator was and still is amazing.

Re: Superfile – A fancy, pretty terminal file manager

#175

"You can go to the latest release and download the binary file. Once it is downloaded please excrate the file after that enter the following in your terminal:" Is excrate some new jargon meaning to take something out of a crate? Or just a boring typo for extract?

Typo for "execrate" meaning "invoke a curse on". If you find the right spell to cast in your terminal, it will reveal its contents to you.

Re: Superfile – A fancy, pretty terminal file manager

#176
post #167

Earlier quoted context omitted.

The point I'm arguing with is your made up benefit of TUIs re. keybinds

TUIs, in general, are more amenable to keyboard navigation than GUIs are; id est, even if GUIs offer keyboard navigation, they are simply not, on average, as good as those of TUIs. I'm not sure how that is controversial in the slightest.

It's not controversial, just wrong and different from what you were arguing for before about some innate TUI benefit ("mandatory"), which simply doesn't exist.

Now, "on average" does all the talking here, like, even putting the cli vs tui categorization aside (otherwise the "average" would support no nav, just some text flags), you can't really pick a small niche of TUI apps and compare it to the whole GUI, pick the same niche, and then you'd get categorically comparable keyboard support

Re: Superfile – A fancy, pretty terminal file manager

#177

Earlier quoted context omitted.

Fairly commonplace for TUIs that use icon. Tons of vim plugins rely on NerdFonts (A regular monospace font that also includes tons of icons)

Is there any technical reason the font can't be shipped in the binary and installed automatically?

Which font? What license? Which one does the user want?

Where does it get installed? Will the user consent?

I did not use a Nerd Font until I tried superfile out today. It was not hard to build my own nerd font version of Berkeley Mono with font forge.

Re: Superfile – A fancy, pretty terminal file manager

#178
post #56

Earlier quoted context omitted.

An operating system from 2018 which is no longer maintained by its vendor? https://www.linuxmint.com/rel_tara_cinnamon_whatsnew.php I think it's somewhat unreasonable to expect software released today will necessarily work on your environment without some legwork.

Is it though? I can run Windows programs from 20 years ago on my Windows machine just fine. Issues with Linux binary distribution meanwhile are ubiquitous, with glibc probably being the single biggest offender. What's worse is that you can't even really statically link it without herculean effort. I've spent an inordinate amount of my life trying to wrangle third-party binaries on Linux libraries and it's just a sorr…

It's an interesting comparison. I agree that five years is well within the expected period of viability of an operating system. Some points to consider:

- any given release of a Linux distro will probably work on hardware released five years earlier -- one factor that reduces the cost of upgrading the OS (there are many more obvious factors)

- Microsoft is highly motivated to get customers to upgrade to the new Windows at the time. The legacy support is well-known as a "bone" (or: "a factor that reduces the cost of upgrading the OS")

- binary backwards/forwards compatibility is less of an issue in an environment that doesn't treat source code as a secret

- why run old versions of software? In other words: xterm is older than Windows and also as new as Windows

Also, I've always found it amusing that I have much less trouble running old windows software on a Linux (wine) than on new versions of windows.

Re: Superfile – A fancy, pretty terminal file manager

#179
post #176

Earlier quoted context omitted.

TUIs, in general, are more amenable to keyboard navigation than GUIs are; id est, even if GUIs offer keyboard navigation, they are simply not, on average, as good as those of TUIs. I'm not sure how that is controversial in the slightest.

It's not controversial, just wrong and different from what you were arguing for before about some innate TUI benefit ("mandatory"), which simply doesn't exist. Now, "on average" does all the talking here, like, even putting the cli vs tui categorization aside (otherwise the "average" would support no nav, just some text flags), you can't really pick a small niche of TUI apps and compare it to the whole GUI, pick the…

No, on average, GUIs are simply better for most people than TUIs. Now if you cannot accept that elementary fact, there is nothing more to discuss with you, as we have wholly different world experiences. Having accepted that, TUIs are better than GUIs by some margin. Now, I can empirically show that there is a better benefit to TUIs than GUIS such that if you don't believe it, (wherever you seem to be in the Islamic world, I pity you) thank you, and have a good day. I am not even Muslim and even still I understand a-salamu alaykum.

Re: Superfile – A fancy, pretty terminal file manager

#180

brew install superfile (ok) superfile (not found) find superfile (not sound) cd /usr/local/Cellar/superfile/1.1.2/bin ls spf This is mentioned in the tutorial but it's probably worth mentioning in the install section to save people 5-10 minutes of confusion. Once I found the filename I loved it.

Or even provide superfile as an alias which prints a message saying "you can also call it as spf", once a day. People don't read install sections.
Post reply on HN