Hey All, What's wrong with midnight commander? It's an oldy but a goody. Two pane file interface, has a boatload of features. Is it the "bloat" of these other features that you're trying to avoid?
Personally, I don't use a file manager. A straight bash prompt with cd, ls, tree etc is fine for day to day use. Instead of the binary tree program, I found this bash-oneliner replacement: find . -print | sed -e 's;[^/]*/;|____;g;s;____|; |;g' It's about the same speed as the regular program and more suckless then a dedicated binary.(IMO) -- Ian Daniher On Sat, Dec 27, 2008 at 10:54 AM, Jack Woehr <j...@well.com> wrote: > Ricardo Catalinas Jiménez wrote: > >> I tried it after vifm but what I really wanted was a very minimal >> filesystem viewer with vim-like commands, that's why I wrote fm. >> >> > > Cute, from screenshot and description, fm reminds me of FULIST on z/VM. > > But it doesn't build on OpenBSD: > > $ gmake CC=gcc > ctags fm.c fs.c ui.c cmd.c fm.h > gcc -g -Wall -pedantic -ansi $(pkg-config --cflags glib-2.0) -c -o > fm.o fm.c > fm.c: In function `set_sighandlers': > fm.c:60: error: `SIGWINCH' undeclared (first use in this function) > fm.c:60: error: (Each undeclared identifier is reported only once > fm.c:60: error: for each function it appears in.) > fm.c: In function `unset_sighandlers': > fm.c:73: error: `SIGWINCH' undeclared (first use in this function) > gmake: *** [fm.o] Error 1 > > which is kind of weird because even if I specifically #include > <sys/signal.h> > in which `SIGWINCH' is declared it doesn't find it. Haven't had time yet > to dig in deep. > > -- > Jack J. Woehr # I run for public office from time to time. It's > like > http://www.well.com/~jax <http://www.well.com/%7Ejax> # working out at the > gym, you sweat a lot, don't get > http://www.softwoehr.com # anywhere, and you fall asleep easily > afterwards. >