xaizek / vifm (License: GPLv2+) (since 2018-12-07)
Vifm is a file manager with curses interface, which provides Vi[m]-like environment for managing objects within file systems, extended with some useful ideas from mutt.
Clone URLs: https://code.reversed.top/user/xaizek/vifm ssh://rocketgit@code.reversed.top/user/xaizek/vifm
v0.13 v0.13-beta master
Commit bd2b0cb7eea0c6fa1d9d2b0993698108a144934a

Improved documentation on :file[x]type commands
Thanks to Stas Malavin.
Author: xaizek
Author date (UTC): 2014-05-15 18:37
Committer name: xaizek
Committer date (UTC): 2014-05-15 18:37
Parent(s): 02b9d19ebadf96ebe1d436778abaaf98808438b9
Signing key:
Tree: e3490d3a4ed05fa1b78b3393c0b81952aaa2d2ae
File Lines added Lines deleted
ChangeLog 2 0
data/vifm.1 44 0
data/vim/doc/vifm.txt 41 0
File ChangeLog changed (mode: 100644) (index 1b467ccc1..4680a671b)
1 1 0.7.7-beta to current 0.7.7-beta to current
2 2
3 Improved documentation on :file[x]type commands. Thanks to Stas Malavin.
4
3 5 Fixed drawing "*" mark for cursor in inactive pane. Thanks to Svyatoslav Fixed drawing "*" mark for cursor in inactive pane. Thanks to Svyatoslav
4 6 Mishyn, a.k.a. juef. Mishyn, a.k.a. juef.
5 7
File data/vifm.1 changed (mode: 100644) (index a04c428d1..eb51357fe)
... ... actions:
1352 1352 same as :filetype, but vifm will ignore this command if it's not running in X. same as :filetype, but vifm will ignore this command if it's not running in X.
1353 1353 In X :filextype is equal to :filetype. See "Globs" section below for pattern In X :filextype is equal to :filetype. See "Globs" section below for pattern
1354 1354 definition. See also "Automatic FUSE mounts" section below. definition. See also "Automatic FUSE mounts" section below.
1355
1356 For example, consider the following settings (the order might seem strange,
1357 but it's for the demonstration purpose):
1358
1359 .EE
1360 filetype *.html,*.htm
1361 \ {View in lynx}
1362 \ lynx
1363 filextype *.html,*.htm
1364 \ {Open with dwb}
1365 \ dwb %f %i &,
1366 filetype *.html,*.htm
1367 \ {View in links}
1368 \ links
1369 filextype *.html,*.htm
1370 \ {Open with firefox}
1371 \ firefox %f &,
1372 \ {Open with uzbl}
1373 \ uzbl-browser %f %i &,
1374 .EX
1375
1376 If you're using vifm inside a terminal emulator that is running in graphical
1377 environment (when X is used on *nix; always on Windows), vifm will attempt to
1378 run application in this order:
1379
1380 1. lynx
1381 2. dwb
1382 3. links
1383 4. firefox
1384 5. uzbl
1385
1386 If there is no graphical environment (checked presence of $DISPLAY
1387 environment variable on *nix; never happens on Windows), the list will look
1388 like:
1389
1390 1. lynx
1391 2. links
1392
1393 Just as if all :filextype commands were not there.
1394
1395 The purpose of such differentiation is to allow comfortable use of vifm
1396 with same settings in desktop environment/through remote connection (SSH)/
1397 in native console.
1398
1355 1399 .TP .TP
1356 1400 .BI ":filev[iewer] pat1,pat2,... command" .BI ":filev[iewer] pat1,pat2,... command"
1357 1401 will associate given command as a viewer to each of the patterns. Viewer is a will associate given command as a viewer to each of the patterns. Viewer is a
File data/vim/doc/vifm.txt changed (mode: 100644) (index b92679d0a..e847ce735)
... ... The builtin commands are:
1214 1214 In X :filextype is equal to :filetype. See |vifm-globs| for pattern In X :filextype is equal to :filetype. See |vifm-globs| for pattern
1215 1215 definition. See also |vifm-fuse|. definition. See also |vifm-fuse|.
1216 1216
1217 For example, consider the following settings (the order might seem
1218 strange, but it's for the demonstration purpose): >
1219
1220 filetype *.html,*.htm
1221 \ {View in lynx}
1222 \ lynx
1223 filextype *.html,*.htm
1224 \ {Open with dwb}
1225 \ dwb %f %i &,
1226 filetype *.html,*.htm
1227 \ {View in links}
1228 \ links
1229 filextype *.html,*.htm
1230 \ {Open with firefox}
1231 \ firefox %f &,
1232 \ {Open with uzbl}
1233 \ uzbl-browser %f %i &,
1234 <
1235 If you're using vifm inside a terminal emulator that is running in
1236 graphical environment (when X is used on *nix; always on Windows), vifm
1237 will attempt to run application in this order:
1238
1239 1. lynx
1240 2. dwb
1241 3. links
1242 4. firefox
1243 5. uzbl
1244
1245 If there is no graphical environment (checked presence of $DISPLAY
1246 environment variable on *nix; never happens on Windows), the list will
1247 look like:
1248
1249 1. lynx
1250 2. links
1251
1252 Just as if all :filextype commands were not there.
1253
1254 The purpose of such differentiation is to allow comfortable use of vifm
1255 with same settings in desktop environment/through remote connection (SSH)/
1256 in native console.
1257
1217 1258 *vifm-:fileviewer* *vifm-:filev* *vifm-:fileviewer* *vifm-:filev*
1218 1259 :filev[iewer] pat1,pat2,... command - will associate given command as a :filev[iewer] pat1,pat2,... command - will associate given command as a
1219 1260 viewer to each of the patterns. Viewer is a command which output is viewer to each of the patterns. Viewer is a command which output is
Hints
Before first commit, do not forget to setup your git environment:
git config --global user.name "your_name_here"
git config --global user.email "your@email_here"

Clone this repository using HTTP(S):
git clone https://code.reversed.top/user/xaizek/vifm

Clone this repository using ssh (do not forget to upload a key first):
git clone ssh://rocketgit@code.reversed.top/user/xaizek/vifm

You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a pull request:
... clone the repository ...
... make some changes and some commits ...
git push origin master