Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vi shows no mapping found #1

Open
connectkushal opened this issue Jun 20, 2017 · 5 comments
Open

vi shows no mapping found #1

connectkushal opened this issue Jun 20, 2017 · 5 comments

Comments

@connectkushal
Copy link

connectkushal commented Jun 20, 2017

I installed this using the junegunn/vim-plug plugin and added these to the .vimrc

filetype on
filetype plugin on
au BufRead,BufNewFile *.pago set filetype=pago

I created a new file test.pago, but its not working...

@connectkushal connectkushal changed the title Thank you ! Its not working. Jun 20, 2017
@connectkushal connectkushal changed the title Its not working. vi shows no mapping found Jun 20, 2017
@zazaian
Copy link
Owner

zazaian commented Jun 20, 2017

Hi there @connectkushal: sounds like this might be an issue with vim-plug. This is specifically a filetype plugin, and so it should be installed in ~/.vim/ftplugin. If you're using Ubuntu or some similar linux distribution that uses this format then vim should find the plugin in that directory automatically.

@connectkushal
Copy link
Author

connectkushal commented Jun 22, 2017

thanx for replying @zazaian . I removed vim-plug and did what you suggested, also followed the readme. So i saved the pago.vim in the ~/.vim/ftplugin/ folder and added filetype etc to my .vimrc

But now when i try to open or create an new test.pago file, the vi editor closes instantly. I dont even see any error. This is my .vimrc file

filetype on 
filetype plugin on 
au BufRead,BufNewFile *.pago  set filetype=pago 

nmap ,ev :e ~/.vimrc<cr>
nmap ; : 
set nowrap

@connectkushal
Copy link
Author

vi is working fine for all other files, except those with .pago extention.

@zazaian
Copy link
Owner

zazaian commented Aug 9, 2017

Hi there @connectkushal - are you using vi or vim? I've never tested this on plain VI.

@connectkushal
Copy link
Author

Im using vim 7.4 with set nocompatibility

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants