Giter Club home page Giter Club logo

neovim-vifm's Introduction

Vifm – Vim-like file manager

Vifm logo

      

Latest release is 0.13. This file last updated on 04 April 2023.

Brief Description

Vifm is a curses based Vim-like file manager extended with some useful ideas from mutt. If you use Vim, Vifm gives you complete keyboard control over your files without having to learn a new set of commands. It goes not just about Vim-like keybindings, but also about modes, options, registers, commands and other things you might already like in Vim.

Just like Vim, Vifm tries to adhere to the Unix philosophy. So instead of working solutions which are set in stone user is provided with a set of means for customization of Vifm to one's likings. Though builtin functionality should be enough for most of use cases.

Resources and Contacts

Usage Link
Website https://vifm.info/
Wiki https://wiki.vifm.info/
Q & A https://q2a.vifm.info/

Communication

Reason Channel
Bugs & Feature Requests GitHub, SourceForge or via email
Preferred place for asking usage questions Posting on the Q&A site
Read-only and very low traffic news mailing list vifm-announce

Other resources

Usage Where to find
Repositories GitHub and SourceForge
Vim Plugin Repository
Colorschemes (maintained) Repository and colorscheme-previews
Devicons/favicons [1], [2]
vifmimg (image preview) Repository (using überzug to display the images)
sixel image preview Repository (for Sixel-capable terminals)

Screenshots

Screenshot Screenshot

Getting Started

A good idea for quick start might be skimming over cheatsheet for the main mode (that is Normal mode), reading some sections on basic usage on the wiki and looking at sample configuration file (run :edit $MYVIFMC).

License

GNU General Public License, version 2 or later.

neovim-vifm's People

Contributors

rbong avatar xaizek avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

cs558i

neovim-vifm's Issues

Consider "single pane" mode for vifm within neovim

neovim is naturally working very well in single pane mode.

netrw is working in single pane mode only.

vifm excells in single pane mode as one can use registers to copy, paste files etc.

Currently the plugin starts vifm within neovim in dual pane mode mostly (without editing .vifm/vifmrc file it opens dual pane). Especially with :Vifm . the dual pane clutters the space and I found myself all the time switching to single pane.

My current workaround will be to keep within my ~.vifm/vifmrc file a line :only to open always in single pane.

For those who like dual pane outside of neovim and single pane in neovim would be an improvement any of:

  • always open in single pane mode
  • add an option into neovim configuration controlling the mode

docs and args

First, thank you for the great plugin. As a big fan of both vifm and vim (now neovim), I have always loved the integration between the two and I am very happy to see that this plugin is taking advantage of some of the advanced features of neovim.

I do have two suggestions:

The first is better documentation. There are no vimdocs and so we cannot use :help from inside of vim, but also, the readme file doesn't contain any mention of the variables and reading the source code, it appears that there are many variables available. Having them documented somewhere (docs best, but readme is fine) would help.

My second suggestion is to allow passing options to the vifm commands. I realize this can be a little tricky because you are trying to check for 'isDirectory' to ensure proper handling of ':edit ' commands, but maybe an option could be added (ie g:Vifm_options).

Thanks again, and I hope these suggestions help.

unable to rename multiple files

I have problems to use :rename on multiple files.

neovim version:

NVIM v0.2.1-dev
Build type: RelWithDebInfo
Compilation: /usr/bin/x86_64-linux-gnu-gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_MSGPACK_HAS_FLOAT32 -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -I/build/neovim-10058w/neovim-0.2.0ubuntu1+git201708261906+3618+26~ubuntu16.04.1/build/config -I/build/neovim-10058w/neovim-0.2.0ubuntu1+git201708261906+3618+26~ubuntu16.04.1/src -I/build/neovim-10058w/neovim-0.2.0ubuntu1+git201708261906+3618+26~ubuntu16.04.1/.deps/usr/include -I/build/neovim-10058w/neovim-0.2.0ubuntu1+git201708261906+3618+26~ubuntu16.04.1/.deps/usr/include -I/build/neovim-10058w/neovim-0.2.0ubuntu1+git201708261906+3618+26~ubuntu16.04.1/.deps/usr/include -I/build/neovim-10058w/neovim-0.2.0ubuntu1+git201708261906+3618+26~ubuntu16.04.1/.deps/usr/include -I/build/neovim-10058w/neovim-0.2.0ubuntu1+git201708261906+3618+26~ubuntu16.04.1/.deps/usr/include -I/build/neovim-10058w/neovim-0.2.0ubuntu1+git201708261906+3618+26~ubuntu16.04.1/.deps/usr/include -I/usr/include -I/build/neovim-10058w/neovim-0.2.0ubuntu1+git201708261906+3618+26~ubuntu16.04.1/build/src/nvim/auto -I/build/neovim-10058w/neovim-0.2.0ubuntu1+git201708261906+3618+26~ubuntu16.04.1/build/include
přeložil  root@lcy01-11

Features: +acl +iconv +jemalloc +tui 
See ":help feature-compile"

   systémový vimrc soubor: "$VIM/sysinit.vim"
  implicitní hodnota $VIM:"/usr/share/nvim"

vifm version:

$ vifm --version
Version: 0.9
Git info: built out of repository
Compiled at: Aug 27 2017 09:57:22

Support of extended keys is on
Parsing of .desktop files is enabled
With GTK+ library
Without magic library
With X11 library
With dynamic loading of X11 library
With file program
With -n option for cp and mv
With remote command execution

When I open neovim, start vifm from here (by :e .), select visually few files and call :rename, it prints:

Chyba při zpracování /usr/share/nvim/runtime/plugin/health.vim:
řádek    8:
E10: po \ by měl následovat /. ? nebo &
--- Automatické příkazy ---
Chyba při zpracování /usr/share/nvim/runtime/plugin/shada.vim:
řádek    9:
E10: po \ by měl následovat /. ? nebo &
řádek   10:
E10: po \ by měl následovat /. ? nebo &
řádek   11:
E10: po \ by m�ěl následovat /. ? nebo &[J
--- Automatické příkazy ---
řádek   13:
E10: po \ by měl následovat /. ? nebo &
řádek   14:
E10: po \ by měl následovat /. ? nebo &
--- Automatické příkazy ---
řádek   16:
E10: po \ by měl následovat /. ? nebo &
řádek   17:
E10: po \ by měl následovat /. ? nebo &
řádek   18:
E10: po \ by měl následovat /. ? nebo &
řádek   19:
E10: po \ by měl následovat /. ? nebo &
řádek   20:
E35: žádný předchozí regulární výraz
řádek   21:
E10: po \ by měl následovat /. ? nebo &
řádek   22:
E10: po \ by měl následovat /. ? nebo &
--- Automatické příkazy ---
řádek   24:
E10: po \ by měl následovat /. ? nebo &
řádek   25:
E10: po \ by měl následovat /. ? nebo &
řádek   26:
E10: po \ by měl následovat /. ? nebo &
řádek   27:
E10: po \ by měl následovat /. ? nebo &
řádek   28:
E10: po \ by měl následovat /. ? nebo &
řádek   29:
E10: po \ by měl následovat /. ? nebo &
--- Automatické příkazy ---
řádek   31:
E10: po \ by měl následovat /. ? nebo &
řádek   32:
E10: po \ by měl následovat /. ? nebo &
řádek   33:
E10: po \ by měl následovat /. ? nebo &
řádek   34:
E10: po \ by měl následovat /. ? nebo &
řádek   35:
E10: po \ by měl následovat /. ? nebo &
řádek   36:
E10: po \ by měl následovat /. ? nebo &
--- Automatické příkazy ---
řádek   38:
E10: po \ by měl následovat /. ? nebo &
Press ENTER or type command to continue

What translates (translation might not be precise) to:

Error processing /usr/share/nvim/runtime/plugin/health.vim:
line    8:
E10: after \ should follow /. ? or &
--- Automated commands ---
Error processing /usr/share/nvim/runtime/plugin/shada.vim:
line    9:
E10: after \ should follow /. ? or &
line   10:
E10: after \ should follow /. ? or &
line   11:
E10: after \ should folloe /. ? or &[J
--- Automated commands ---
line   13:
E10: after \ should follow /. ? or &
line   14:
E10: after \ should follow /. ? or &
--- Automated commands ---
line   16:
E10: after \ should follow /. ? or &
line   17:
E10: after \ should follow /. ? or &
line   18:
E10: after \ should follow /. ? or &
line   19:
E10: after \ should follow /. ? or &
line   20:
E35: no previous regular expression
line   21:
E10: after \ should follow /. ? or &
line   22:
E10: after \ should follow /. ? or &
--- Automated commands ---
line   24:
E10: after \ should follow /. ? or &
line   25:
E10: after \ should follow /. ? or &
line   26:
E10: after \ should follow /. ? or &
line   27:
E10: after \ should follow /. ? or &
line   28:
E10: after \ should follow /. ? or &
line   29:
E10: after \ should follow /. ? or &
--- Automated commands ---
line   31:
E10: after \ should follow /. ? or &
line   32:
E10: after \ should follow /. ? or &
line   33:
E10: after \ should follow /. ? or &
line   34:
E10: after \ should follow /. ? or &
line   35:
E10: after \ should follow /. ? or &
line   36:
E10: after \ should follow /. ? or &
--- Automated commands ---
line   38:
E10: after \ should follow /. ? or &
Press ENTER or type command to continue

and vifm opens editor window with the selected files. Neovim shows terminal mode.

After that, I am unable to complete the rename as neovim seems to be completely confused (neovim with terminal window running vifm and vim or neovim editor open from here).

The only sane method to procede is :cq.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.