Request for new port: vifm

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Request for new port: vifm

Andreas Bihlmaier-2
Hello ports@,

I would really like to see "vifm" [1] in the ports tree, because it is a really
nice and comfortable file manager (like mc), but with vi key bindings.

I basically downloaded the source, untared it, fixed all the symlinks in the
vifm directory and had to comment out one line in vimfm/src/ui.c
I don't know where the symlinks SHOULD go, I just linked it against files I
found with the same name (yeah it worked somehow :)

This is not a fix of course, but it enabled me to compile it and it runs just
fine. I'm sure somenone here (having much more C/ncurses knowledge) could fix
it quickly.


#------------------------------- dirty_hack -----------------------------------#
--- vifm/src/ui.c       Sun Jul 17 23:51:28 2005
+++ vifm2/src/ui.c      Thu Nov 24 07:57:51 2005
@@ -324,7 +324,7 @@
 
        ioctl(0, TIOCGWINSZ, &ws);
 
-       resize_term(ws.ws_row, ws.ws_col);
+/*     resize_term(ws.ws_row, ws.ws_col); */
 
        getmaxyx(stdscr, screen_y, screen_x);
#------------------------------------------------------------------------------#


Since I'm sure many developers/ports-maintainers are using vi[m] as well, would
it be possible to make a port and include it?

[1] http://vifm.sourceforge.net/

Regards,
ahb

Please CC me, otherwise I have to read it in the archives (no problem either).

Reply | Threaded
Open this post in threaded view
|

Re: Request for new port: vifm

Andreas Bihlmaier-2
Hello ports@ again,

sorry for answering my own mail, but I did some more research:

To make vifm compile you just have to install automake >1.7 (I used 1.9) change
the links in vifm/ to point to
/usr/local/share/automake-1.9/{depcomp,install-sh,missing,mkinstalldirs}

The "patch" I posted before has to be used (still don't know why, older version
of ncurses on openbsd?).

I found about about more niffty features, one is that you can define default
programs for every file type, so vifm will use those programms to open them.

As I said EVERYBODY working with VI[M] and many files should have a look at it,
the ease of use is just impressive.

Since I didn't get any reply so far what could I do to get it adopted as an
official port?

Btw, it works (at least) on:
i386
amd64
(not on hppa and vax (there is no new enough autoconf :))


Regards,
ahb

Reply | Threaded
Open this post in threaded view
|

Re: Request for new port: vifm

Andreas Bihlmaier-2
In reply to this post by Andreas Bihlmaier-2
I have to correct myself,
it DOES also work on (just had to copy over parts of a newer automake):
hppa
(don't know about vax, can't get the ethernet to work right now, still 3.5 on
it, long time since I switched it on)

Regards,
ahb