Welcome to Vifm Q&A, where you can ask questions about using Vifm. Registration is optional, anonymous posts are moderated. E-mail and GitHub logins are enabled.
0 votes
in vifm by

So there is screen! to enable tmux integration, and %s/%v command macros to change behavior of user commands.

However, they don't seem to work for the editor:

set vicmd=vim\ %v " this starts argv[0]="vim", argv[1]="%v" in a new tmux window

Likewise for :help, which is super annoying.

Any way I can make vifm start the editor in a tmux pane (bonus points for auto-hiding the opposite pane, such that the width of the active pane stays unchanged)?

1 Answer

0 votes
by

That's correct, 'vicmd'/'vixcmd' don't process macros because they specify commands used in many different contexts. There are probably very few macros that make sense there like %s/%v and even they would need to be suppressed on :rename.

You can work around this by using Vim via editor plugin (how to install) where you might add %s/%v where you want them by editing the file because vifm.run() works like :!.

by

I see. Would there perhaps be interest in introducing a general family of command wrappers similar to Vim's :botright, :topleft &c. (and perhaps not too different from Vifm's own :keepsel) for influencing the tmux spawn decisions?

by

Maybe because I tend to keep Vifm in its own tab I probably never thought of using command modifiers in the context of integration with a terminal multiplexer, but it might be useful. Mind that unlike changes to 'vicmd', this won't apply uniformly: to keys like l or when opening something from a menu (e.g., :grep).

If you would like to make a bug report or feature request consider using GitHub, SourceForge or e-mail. Posting such things here is acceptable, but this is not a perfect place for them.
...