gmane.editors.vim

Re: How to deal with multiple compiler error formats, possibly from a single make invocation?

Sam Roberts — 2013-05-24T04:51:43

Can you give me more of a hint?

Somehow, I'd have to create a macro that ran make, then called
compiler X, caddfile, compiler Y, caddfile, etc....?

Sam

Re: Vundle vs Pathogen

Donie Leigh — 2013-05-24T03:33:00

< at >Marc Thanks for your recommendation, it seems VAM gives consideration
to both statibility and radicalism. I will give it try.

2013/5/24 Gary Johnson <garyjohn< at >spocom.com>:

Re: How to deal with multiple compiler error formats, possibly from a single make invocation?

Ben Fritz — 2013-05-24T01:32:50

Maybe instead you could use :caddfile, :caddbuffer, or :caddexpr to build a list using one format at a time?

Re: Implementing nested braces for syntax folding

Ben Fritz — 2013-05-24T01:29:46

I've wanted for a while to get Perl folding to work based on open-close brace only, instead of relying on indent.

Since you are already messing with the syntax folding, what are the chances of getting that working as part of your updates? I got it working once before it went to github, but I wasn't able to get it working again the last time I tried.

How to deal with multiple compiler error formats, possibly from a single make invocation?

Sam Roberts — 2013-05-23T21:46:05

Hi, using node, mocha, and jshint, when I run my unit tests with make,
I can get output from any of the above. All with different error
formats. Note that I can run lint seperate from mocha, but mocha is a
test runner, it WILL have node error stacks in its output, and I want
to be able to :cn through them.

I can see how I might combine all their error formats by hand into one
massive "javascript" error format, by cutting and pasting, but I don't
see how I could do this in anything like a nice way.

I'd like something like:

after/javascript.vim:
compiler jshint
compiler +node
compiler +mocha

Baring that, is there some way I could map \\ to make, \j to [set
makeprg=npm run lint, \\], \n to [set makeprg=node %, \\], etc...

Suggestions, please?


The errformats lying around the web for the above are all poorly
constructed, instead of being constructed as a compiler, they are
hard-coded into javascript.vim file types, often with the authors
idiosyncratic makeprg preferences, as well, so I'm reconstructing them
as compiler definitions. :-(

If anybody has a decent vim setup for node.js development, I'd love to
hear about it.

Sam

Re: To all syntax file maintainers: examples needed

Bram Moolenaar — 2013-05-23T21:03:46

Rob Hoelz wrote:


I'm only testing with the actual syntax highlighting.
If you see a particular pattern that's not working, please make an
example in this form:

   echo matchlist("t", '\%#=1ú\Z')
   echo matchlist("t", '\%#=2ú\Z')

Implementing nested braces for syntax folding

Rob Hoelz — 2013-05-23T19:08:16

Hi all,

I'm working on bringing the Perl runtime files up to speed for the upcoming 7.4 release, but I've encountered an interesting bug and seek the community's help.  Attached is an example Perl file.  When using the HEAD of vim-perl (https://github.com/vim-perl/vim-perl), the three subroutines fold properly with the default settings.  However, with perl_fold_anonymous_subs set to 1, the folding for the third subroutine (which has attributes, which seems to trigger this odd behavior), the fold is not properly ended and continues until the end of the file.  The opening brace of the subroutine seems to be counted as an inner brace (see the perlBraces rule), even though it's present in the perlSubFold rule (according to synstack), and that's messing up the folding.  I understand not everyone has time to look through a complicated several hundred line syntax file, so I've included a minimal syntax file that demonstrates this behavior as well (although min.vim messes up *all* the folds; the problem is the same, though).  Could any syntax gurus or Vim developers help me figure out what I'm doing wrong?

By the way, I'm using Vim 7.3, patch level 1004.  If you're testing with a Vim where the patch level is < 970, you'll need to comment out the line setting the regexpengine.

Thanks,
Rob

Re: How to get Allman style while typing and templated C++ code in Vim 7.3

Gary Johnson — 2013-05-23T17:51:02



The 'formatprg' option does not do automatic formatting unless the
'a' flag of 'formatoptions' is set, which I would not recommend in
this case.  Further, the = command uses 'equalprg', not 'formatprg'.

So, to format your code using astyle as the 'formatprg', you will
need to manually reformat sections as you go with gq, not =.

Alternatively, you could set 'equalprg' to astyle, then use the =
command.

I think the behavior may be different between using astyle as the
'formatprg' vs. the 'equalprg', but I don't know what it is off the
top of my head.

Regards,
Gary

Re: Vundle vs Pathogen

Gary Johnson — 2013-05-23T17:24:54

OCD - Obsessive-Compulsive Disorder - an anxiety disorder
characterized by intrusive thoughts that produce uneasiness,
apprehension, fear, or worry; by repetitive behaviors aimed at
reducing the associated anxiety; or by a combination of such
obsessions and compulsions.

http://en.wikipedia.org/wiki/Obsessive%E2%80%93compulsive_disorder

Regards,
Gary

Re: Vundle vs Pathogen

Phil Dobbin — 2013-05-23T17:21:12


For further reinforcement of what Christian's saying, refer to the first
law of system administration: if it's working correctly unless you have
a *really* good reason to, don't just upgrade for the sake of it.

Cheers,

  Phil...

Re: how to debug file type recognition

Matteo Cavalleri — 2013-05-23T16:36:19

looking back at my dotfiles git log i found that to be my first attempt to fix this issue, and that clearly shows that i didn't understand at all vim plugins/filetypes ^__^ at least i should have learned something new.

btw, after some tries i was able to fix the problem by removing that line from ftplugin/ and putting it inside ~/.vim/after/ftdetect/smarty.vim, ~/.vim/ftdetect/ wasn't enough to get my settings win over the other plugin ftdetect

regarding my multiple loads i won't be at office till next monday, so i'll be unable to test this. i can try to replicate the issue here at home on my mac though. supposing os / system performance don't matter, i should be able to get the same result i have on my linux box

thanks again for the help

Re: Vundle vs Pathogen

Christian Brabandt — 2013-05-23T15:19:19

I don't know what an OCD patient is, but I don't understand, why
you "cannot tolerate old versions of vim scripts"? If they work well
for you, why bother?

regards,
Christian

Re: Vundle vs Pathogen

Marc Weber — 2013-05-23T14:50:00

Excerpts from Donie Leigh's message of Thu May 23 14:38:54 +0200 2013:

Contribute your findings to this document:
http://vim-wiki.mawercer.de/wiki/topic/vim%20plugin%20managment.html


Yes - and how "biased" this view is can be seen that vim-addon-manager
is seldomly listed, even though its the most powerful one IMHO.

Where did you look for a reply before doing this research?
Trying to understand how to improve this for the community,
because this happens often, that people get something done,
then later see that they did the wrong thing (comparing 2 solutions
only, ignoring a third, which should not have been missed).

Marc Weber

Re: How to get Allman style while typing and templated C++ code in Vim 7.3

Reid Thompson — 2013-05-23T14:46:12

forgot the vim.org page
http://www.vim.org/scripts/script.php?script_id=213

Re: How to get Allman style while typing and templated C++ code in Vim 7.3

Reid Thompson — 2013-05-23T14:44:57

it supports both c and c++

http://www.vim.org/scripts/script.php?script_id=213 --> The key mappings of this plugin (PDF) : http://lug.fh-swf.de/vim/vim-c/c-hotkeys.pdf 

The help file online :   http://lug.fh-swf.de/vim/vim-c/csupport.html

The solution to make YouCompleteMe compatible with UltiSnips

Donie Leigh — 2013-05-23T12:52:42

Hi all,

I have a solution on the compatibility problem between YouCompleteMe
and UltiSnips, hope to help someone.

First, change the default key-binding of YCM to <C-TAB> and <C-S-TAB>:

let g:ycm_key_list_select_completion = [‘<C-TAB>’, ‘<Down>’]
let g:ycm_key_list_previous_completion = [‘<C-S-TAB>’, ‘<Up>’]

Then set the default action of SuperTab to triggering <C-TAB>:

let g:SuperTabDefaultCompletionType = ‘<C-Tab>’

For more information, refer to my blog post:
http://0x3f.org/blog/make-youcompleteme-ultisnips-compatible/

Vundle vs Pathogen

Donie Leigh — 2013-05-23T12:38:54

Hi all,

I've made a study about vundle and pathogen, I want to hear opinions
of others, how do you think about it ?

I have been using Pathogen for a long time and I am happy with it. But
it seems that more and more Vim scripts are recommending to use Vundle
in their install references. So I made a study today, the conclusion
is, although almost all the articles I found from Google have a
positive attitude on Vundle, I still prefer Pathogen.

Most supporters of Vundle praise it for one reason, that is, it can
install and update scripts automatically, which is lacked by Pathogen.
Yes, since Vundle leverages the vim-scripts repository on GitHub, it
is really easier to do so than Pathogen. But the disadvantage is as
good as the advantage. I found that the vim-scripts repo is not
updated in time, the latest activity was carried out a month ago ! As
an OCD patient of updating, I cannot tolerate old versions of vim
scripts. Although that Vundle supports using scripts’ git repos of
their own (either on GitHub or other places), there is still a
problem, what if authors commit broken code to the master brunch ?

Moreover, not all scripts are deposited in public git repos. How can I
organize those scripts in ~/.vim/bundle/ and prevent :BundleClean from
deleting them at the same time ?

Pathogen only handles the organization job that puts scripts in
individual folders under ~/.vim/bundle/, so there is without the above
problem. For updating issues, GetLatestVimScripts.vim is a good
choice, it fetches the latest stable updates from vim.org, so I don’t
have to worry about careless commits. The only problem is, when
GetLatestVimScripts.vim downloads all packages, I should install them
manually. But since most scripts rarely update, I think this is not a
hard work to do.

My blog post: http://0x3f.org/blog/vundle-vs-pathogen/

Re: Why does Vim not distinguish right and left CTRL, SHIFT, ALT keys ?

Donie Leigh — 2013-05-23T12:45:33

< at >John Thanks for your answer, yes, xmodmap is a work around.

2013/5/23 John Little <John.B.Little< at >gmail.com>:

Why does Vim not distinguish right and left CTRL, SHIFT, ALT keys ?

John Little — 2013-05-23T12:34:03

Hi

"Why" is a long story, mostly ancient (in computer terms) history. It has been recognized as a weakness in vim and much discussed, but no one has taken on the task of improving the key handling AFAIK. 

However, at a lower level one can do a lot. I use xmodmap when I'm on X (linux and unix) to make windows keys usable with vim. There's hot key utilities for windows. 


Regards, John Little

Re: Why does Vim not distinguish right and left CTRL, SHIFT, ALT keys ?

Donie Leigh — 2013-05-23T12:32:24

Thanks Ben, very clear and helpful.

2013/5/23 Ben Fritz <fritzophrenic< at >gmail.com>:

Re: Why does Vim not distinguish right and left CTRL, SHIFT, ALT keys ?

Ben Fritz — 2013-05-23T11:41:46

Very few programs can actually do that. Vim is worse because it's designed to also work in old terminals that only send a single byte for a CTRL combined with a keypress according to the ASCII standard. Vim works with what it is given.