goodbye sfm, hello vifm
I’ve been a long time user of the sfm. sfm is an extremely lightweight, vi key binding inspired, text mode file manager that is configured by editing its config.h file. The binary is only 60kb, it is really the best file manager for my software minimum fetishism.
Sfm has not been the most stable program, there is always a random crash here and there. Since the latest OpenBSD patch, I keep getting pledge error. So I went on a search for a possible replacement.
From a UX perspective, vifm is very similar to sfm, however, there is a config file where I can name handlers for file type:
filetype {*.mp3,*.ogg} st -e mplayer
well, this is less then ideal, but at least I don’t have to touch xdg-open!
Mar 10 · 8 weeks ago
4 Comments ↓
Questions:
- what is pledge error?
- why is config file less than ideal? is xdg not supported at all?
Otherwise an config file override of xdg sounds ideal to me...
I should take a look at it, 60kb is my cuppa (and should be fixable).
😎 decant [OP] · Mar 11 at 02:03:
yo stack, I. As far as I know, on OpenBSD, a programer can pledge at the source code level that the program will only access a certain subset of API. Once the program is running, the size of this subset can only decrease. the system will kill the program and emit a pledge error. So it could be OpenBSD fixed some pledge enforcement bug. II. A run time config file means the program have to parse a file making it more complex. For such a small program, recompile took 2sec so there is little point on having a run time config file
😎 decant [OP] · Mar 11 at 02:09:
*if a access violation should happen, the system will kill the program and emit a pledge error.
Interesting, I had no idea.
I like suckless configuration for small applications, agreed