Vimacs is an emacs emulation for vim. With it you can use emacs-like keybindings in insert mode. By default vimacs is disabled, unless vim is called as vimacs, vemacs, or vm in its name. Reproducible: Always Steps to Reproduce: Homepages: http://www.algorithm.com.au/code/vimacs/index.html This page is most descriptive. http://sigil.com.au/svn/trunk/Vimacs/ This contains the new and shiny svn repository for vimacs. The attached .tar.gz file is from revision 56 with all the .svn directories removed. http://www.vim.org/scripts/script.php?script_id=300 A bit out of date.
Created attachment 145607 [details] vimacs-56.ebuild
Created attachment 145608 [details] The sources from tarred from svn. All svn related stuff is removed.
Created attachment 145609 [details] The sources from tarred from svn. Stupid me, didn't give the directory the correct name... Now is correct.
Created attachment 145783 [details] svn ebuild
This rather belongs to category app-vim than app-editors. (Like vi emulations in emacs would go to app-(x)emacs, e.g. app-xemacs/viper.) Are there any releases? In general, we are reluctant to add live ebuilds to the Portage tree.
There is a release at: http://www.algorithm.com.au/code/vimacs/download/index.html Oh and by the way, this ebuild should not set those symlinks...it will overwrite all settings from eselect-vim.
Hi, thanks for your replies. When I have time (next week at the earliest) I will look into making an ebuild from a release. Andre Pang (the author) was also talking about making a 1.0 release soon. Christian, how do the symlinks conflict with eselect-vim? Doesn't eselect-vim only manage the /usr/bin/vi symlink? This ebuild sets /usr/bin/vimacs and /usr/bin/gvimacs symlinks and their vemacs counterparts. Btw., should the gvimacs symlink only be set if USE=gtk is set?
(In reply to comment #7) > Christian, how do the symlinks conflict with eselect-vim? Doesn't eselect-vim > only manage the /usr/bin/vi symlink? This ebuild sets /usr/bin/vimacs and > /usr/bin/gvimacs symlinks and their vemacs counterparts. Btw., should the > gvimacs symlink only be set if USE=gtk is set? I was wrong with eselect...it only conflicts with app-editors/vim and gvim, who provide /usr/bin/vim and /usr/bin/gvim. Or do I overlook something?
It doesn't conflict with app-editors/vim or gvim, it depends on them. In the end you will have something like this: lrwxrwxrwx 1 root root 4 2008-03-20 13:14 /usr/bin/gvemacs -> gvim lrwxrwxrwx 1 root root 4 2008-03-20 13:14 /usr/bin/gvimacs -> gvim lrwxrwxrwx 1 root root 3 2008-03-20 13:14 /usr/bin/vemacs -> vim lrwxrwxrwx 1 root root 3 2008-03-20 13:14 /usr/bin/vimacs -> vim Vimacs is a vim script which checks as what it was called, and decides whether to load by default or not. You can also enable it in your ~/.vimrc.
Looks like the 1.0 release has never materialised, with 0.95 - released in March 2008 - remaining the latest available version and only a couple of SVN commits (also from March 2008) afterwards. That said, in principle it should still work so if anyone is interested... Is there still user demand for including this into Portage?
