Excerpts from Ed Kostas's message of Fri Nov 29 12:29:33 +0100 2013:
> Let us examine the specific questions, as suggested by mfid. To make a
> long story short, I may recommend my friends to stick to emacs/evil,
[..] that's what we were silently suggesting because you depend on so
many Emacs specific features.
> flymake
Traditional:
:set makeprg=gcc
:make
:cope
:cnext :cfirst :cprevious :colder
Alternatives:
There are tons of plugins at vim.org, I wrote vim-addon-actions which
lets you bind actions (1st set error format 2snd run compiler) to keys
or bufwrite events.
Some presets can be found in :e $VIMRUNTIME/compilers/* or such.
You use them by :compiler gcc
Howver its not modular enough which is why eg I started
github.com/MarcWeber/vim-addon-errorformats so that I can mix multiple
error format descriptions (eg ruby build system building ocaml, so I
need to recognize ruby and ocaml error messages).
Marc Weber
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment