There are many gibberish, such as N^HNA, dispalayed on sreen when I use \hm command.
It happens to all the unix API name I tired.
e.g:
ASSERT(3) Linux Programmer’s Manual ASSERT(3)

N^HNA^HAM^HME^HE
assert - abort the program if assertion is false

S^HSY^HYN^HNO^HOP^HPS^HSI^HIS^HS
#^H#i^Hin^Hnc^Hcl^Hlu^Hud^Hde^He <^H<a^Has^Hss^Hse^Her^Hrt^Ht.^H.h^Hh>^H>

   v^Hvo^Hoi^Hid^Hd a^Has^Hss^Hse^Her^Hrt^Ht(^H(s^Hsc^Hca^Hal^Hla^Har^Hr _^He_^Hx_^Hp_^Hr_^He_^Hs_^Hs_^Hi_^Ho_^Hn)^H);^H;

D^HDE^HES^HSC^HCR^HRI^HIP^HPT^HTI^HIO^HON^HN
If the macro N^HND^HDE^HEB^HBU^HUG^HG was defined at the moment ^H<^Ha_^Hs_^Hs_^He_^Hr_^Ht_^H.^Hh^H> was last included, the macro a^Has^Hss^Hse^Her^Hrt^Ht() generates no code, and hence does noth-
ing at all. Otherwise, the macro a^Has^Hss^Hse^Her^Hrt^Ht() prints an error message to standard error and terminates the program by calling a^Hab^Hbo^Hor^Hrt^Ht(3) if
^He^Hx_^Hp_^Hr_^He_^Hs_^Hs_^Hi_^Ho_^Hn is false (i.e., compares equal to zero).

   The  purpose  of  this macro is to help the programmer find bugs in his program.  The message "assertion failed in file foo.c, function
   do_bar(), line 1287" is of no help at all to a user.

R^HRE^HET^HTU^HUR^HRN^HN V^HVA^HAL^HLU^HUE^HE
No value is returned.

C^HCO^HON^HNF^HFO^HOR^HRM^HMI^HIN^HNG^HG T^HTO^HO
POSIX.1-2001, C89, C99. In C89, ^He^Hx_^Hp_^Hr_^He_^Hs_^Hs_^Hi_^Ho_^Hn is required to be of type ^Hi^Hn_^Ht and undefined behavior results if it is not, but in C99 it
may have any scalar type.

B^HBU^HUG^HGS^HS
a^Has^Hss^Hse^Her^Hrt^Ht() is implemented as a macro; if the expression tested has side-effects, program behavior will be different depending on whether
N^HND^HDE^HEB^HBU^HUG^HG is defined. This may create Heisenbugs which go away when debugging is turned on.

S^HSE^HEE^HE A^HAL^HLS^HSO^HO
a^Hab^Hbo^Hor^Hrt^Ht(3), a^Has^Hss^Hse^Her^Hrt^Ht_^H_p^Hpe^Her^Hrr^Hro^Hor^Hr(3), e^Hex^Hxi^Hit^Ht(3)

C^HCO^HOL^HLO^HOP^HPH^HHO^HON^HN
This page is part of release 3.22 of the Linux ^Hm^Ha_^Hn_^H-^Hp^Ha_^Hg_^He_^Hs project. A description of the project, and information about reporting bugs,
can be found at http://www.kernel.org/doc/man-pages/.

@WolfgangMehner
Hello, I am wsdjeg, and I am author of SpaceVim, and the website is https://spacevim.org, SpaceVim is just something like spacemacs, but for vim, a user open an issue in my repo ask for lua support. I just find your vim-plugins. I want to use your plugins as lang#lua layer, what do you think? BTW, I hope you could join us.
wsdjeg
thanks.

Add Doxygen style comments for function, classes, methods, ...

I adjusted the c++ class template to the following

== C++.class == map:+c, shortcut:c ==
class |CLASSNAME| {
 public:
  |CLASSNAME| ();

 protected:

 private:

}; /* -----  end of class |CLASSNAME|  ----- */

When I now press \+c the template is inserted without asking for the CLASSNAME and the CLASSNAME results in an empty string.

Have you considered implementing custom syntax highlighting that changes for what functions you implement in your currently open project? I know it's already been done in ide, so it may not need much more than a cut-and-paste.

Thanks for your work -- I use your plugins every day!
--Matt

I am a Windows 10 user and have installed the c-support plugin. As advised in the link, to enable cmake and doxygen, i added the following lines to my _vimrc:

let g:C_UseTool_cmake = 'yes'
let g:C_UseTool_doxygen = 'yes'

Now, when I start up gvim, I get an error dialog box with the message:

Could not load the tool "cmake" (Vim(let):E117: Unknown function: mmtoolbox#make#Interface)- occurred at C:\Users\Satyendra\Vim\vimfiles\autoload\mmtoolbox\cmake.vim, line 219

If I do not add these lines to the _vimrc, I do not get the error message.

I have installed c.vim on both Ubuntu gVim and Windows gVim. When I run a program on Ubuntu, the output is displayed at the bottom. If the program takes user input, it can be entered at the bottom. But in Windows, the output is always displayed in a new cmd called "vimrun"? Is there any way that gVim can show output in gVim itself?

Add "description after the member" for Doxygen similar to Comments/end-of-line comment (\cl):
int size; /*!< \brief Size of the ... */

• Should support ranges, which is important for documenting enums or structs.
• Should work within the framework of set/adjust end-of-line comment.

:cn and :cp does not work in vim, though they do work in gvim.

At first, errors are indicated correctly by the arrows in the side bar. But pressing Enter on an error line in the Quickfix list does not take me to the corresponding position in the source file. Moreover, if I switch to the source file window from the Quickfix window, the arrows disappears forever, as indicated by the following picture:

I am new to vim, thus the above may not be enough to be useful. Feel free to contact me if you need any more information.

PS: thanks for the excellent plugin

When try to run "perl" from inside vim (or gvim) on Windows 7 the error message "(possibly default) Perl Interpreter 'c:\Perl\bin\perl.exe' not executable."

However the Perl executable is in "C:\Perl64\bin\perl.EXE", how do I force Vim-Perl to find it. A side note: the vim script perl.vim does find the proper library directories.

I know that this a newbie thing. My apologies if I have missed something int he documentation.

Also I am running Active State Perl: (v5.14.4)

c-support plug-in undefined function (e.g. mmtemplates#wizard#setupwizard)
In c-support/makedist.sh file to add to package file list:
./autoload/mmtemplates/config.vim
./autoload/mmtemplates/wizard.vim

Please forgive my poor English. I hope that you can understand what i mean

I'm trying to edit the c.idioms.template file that I have sourced. I can make changes and see them applied, except for the return statement. It always gets pushed further in than the previous indent. I would like to make it align. I can't find it in the source code.

This is a fresh copy on a new machine.
I have perltidy installed, no user config defined at the mo.

Typing \ry leads to

Error detected while processing function Perl_Perltidy..Perl_Input:
line 6:
E180: Invalid complete value:

Please advise

I remapped many standard vim keys. Since c-support use "map" instead of "noremap" in a lot of places, it triggers my custom mappings instead, making it unusable. Notably I cannot insert any template. Would you consider fixing it please?

Hi, I have remapped some keys.

let g:BASH_Ctrl_j = 'off'                                                                                                          
nnoremap <C-J> <C-W><C-J>                                                                                                          
nnoremap <C-K> <C-W><C-K>                                                                                                          
nnoremap <C-L> <C-W><C-L>                                                                                                          
nnoremap <C-H> <C-W><C-H>    

Problem is that on .sh files <C-J> doesn't move to the buffer below, but go to the next )}]" and insert mode

So inside vim I do:

:let g:BASH_Ctrl_j
g:BASH_Ctrl_j          off

:map <C-J>
n  <NL>        *@i<C-R>=BASH_JumpForward()<CR>
n  <NL>        * <C-W><NL>
Press ENTER or type command to continue

:unmap <C-J>

:map <C-J>
n  <NL>        *@i<C-R>=BASH_JumpForward()<CR>

:unmap <C-J>
E31: No such mapping

:nnoremap <C-J> <C-W><C-J>

:map <C-J>
n  <NL>        *@i<C-R>=BASH_JumpForward()<CR>
n  <NL>        * <C-W><NL>
Press ENTER or type command to continue

But nothing change

$ vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Apr 26 2017 07:50:37)
Included patches: 1-586
Compiled by Arch Linux
Huge version without GUI.  Features included (+) or not (-):
+acl             +file_in_path    +mouse_sgr       +tag_old_static
+arabic          +find_in_path    -mouse_sysmouse  -tag_any_white
+autocmd         +float           +mouse_urxvt     +tcl/dyn
-balloon_eval    +folding         +mouse_xterm     +termguicolors
-browse          -footer          +multi_byte      +terminfo
++builtin_terms  +fork()          +multi_lang      +termresponse
+byte_offset     +gettext         -mzscheme        +textobjects
+channel         -hangul_input    +netbeans_intg   +timers
+cindent         +iconv           +num64           +title
-clientserver    +insert_expand   +packages        -toolbar
-clipboard       +job             +path_extra      +user_commands
+cmdline_compl   +jumplist        +perl/dyn        +vertsplit
+cmdline_hist    +keymap          +persistent_undo +virtualedit
+cmdline_info    +lambda          +postscript      +visual
+comments        +langmap         +printer         +visualextra
+conceal         +libcall         +profile         +viminfo
+cryptv          +linebreak       +python/dyn      +vreplace
+cscope          +lispindent      +python3/dyn     +wildignore
+cursorbind      +listcmds        +quickfix        +wildmenu
+cursorshape     +localmap        +reltime         +windows
+dialog_con      +lua/dyn         +rightleft       +writebackup
+diff            +menu            +ruby/dyn        -X11
+digraphs        +mksession       +scrollbind      -xfontset
-dnd             +modify_fname    +signs           -xim
-ebcdic          +mouse           +smartindent     -xpm
+emacs_tags      -mouseshape      +startuptime     -xsmp
+eval            +mouse_dec       +statusline      -xterm_clipboard
+ex_extra        +mouse_gpm       -sun_workshop    -xterm_save
+extra_search    -mouse_jsbterm   +syntax          
+farsi           +mouse_netterm   +tag_binary      
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -D_FORTIFY_SOURCE=2  -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1       
Linking: gcc   -L. -Wl,-O1,--sort-common,--as-needed,-z,relro -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-rpath,/usr/lib/perl5/core_perl/CORE  -Wl,-O1,--sort-common,--as-needed,-z,relro -L/usr/local/lib -Wl,--as-needed -o vim        -lm -lncurses -lelf -lnsl    -lacl -lattr -lgpm -ldl   -Wl,-E -Wl,-rpath,/usr/lib/perl5/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro -fstack-protector-strong -L/usr/local/lib  -L/usr/lib/perl5/core_perl/CORE -lperl -lpthread -lnsl -ldl -lm -lcrypt -lutil -lc   -L/usr/lib -ltclstub8.6 -ldl -lz -lpthread -lieee -lm  

Thanks.

This is actually a suggestion for improvement.

While using Perlbrew, it would be much better to have the following code in the .vimrc:

" Enable perlbrew path
if has("gui_running") && filereadable($HOME . "/perl5/perlbrew/etc/bashrc")
  let $PATH=system("source " . $HOME . "/perl5/perlbrew/etc/bashrc; echo -n PATH")
endif

This will allow the plugin to identify the correct version of perl as defined by the Perlbrew configuration and, of course, correct identify issues and a syntax check is carried, since different Perlbrew instances may have different Perl modules installed.

I have the following c++ class template

== C++.class == map:+c, shortcut:c ==
class |?CLASSNAME:c| {
 public:
  |CLASSNAME| ();

 protected:

 private:

}; /* -----  end of class |CLASSNAME|  ----- */

When I now press \+c the template with the entered class name is inserted but the spacing is not as in the template. See an example below.

class Test {
  public:
    Test();

     

  protected:

  private:

}; /* -----  end of class Test  ----- */

The inserted template has two blanks before public (instead of one blank) and four blanks before the constructor (instead of two blanks). Somehow it feels like the spacing is dictated by the "global" vim indent settings but I am not sure.

I have recently started using both Perl-Support and BASH-Support plugins, and enjoy them a lot.
I noticed, though, that the shortcuts worked in BASH-Support, but not in Perl-Support, so I did some investigation. I have found that Perl-Support and BASH-Support act differently in case the .vimrc contains both a homemade mapleader and a "set hidden". I have tested this to be the case in Vim 7.3.547 (GVim) under Linux, as well as Vim 7.3 (MacVim) under OSX.

Below you see three .vimrc files which together illustrate the problem.

" With this .vimrc, \sf works for both BASH and Perl
set nocompatible
filetype plugin on
set hidden

" With this .vimrc, [space]-sf works for both BASH and Perl
set nocompatible
filetype plugin on
let mapleader=" "
let g:mapleader = " "
let g:Perl_MapLeader = " "
let g:BASH_MapLeader=" "

" With this .vimrc, [space]-sf works for BASH but not Perl
set nocompatible
filetype plugin on
set hidden
let mapleader=" "
let g:mapleader = " "
let g:Perl_MapLeader = " "
let g:BASH_MapLeader=" "

Thanks for great plugins!

Hello,

thank you for the nice plugin! It's really helpful!

One little thing to improve would be to set the cursor to the last line of the file after inserting the header.

Dear Wolfgang,

How about including some of the more general items in POD?
For example, I prefer to include the following at the start of my programs:

=head2 SYNOPSIS

PACKAGE NAME:

AUTHOR: Juan Lorenzo

DATE:

DESCRIPTION:
Version:

=head2 USE

=head3 NOTES

=head4 Examples

=head2 SYNOPSIS

=head3 SEISMIC UNIX NOTES

=head2 CHANGES and their DATES

=cut

THANKYOU!

Just upgraded to version 6.0 from using 5.19. Observed slow start-up time of vim after the upgrade. Ran vim --startuptime for both versions. Now version 5.19 has a start up of 35ms, while 6.0 has a start up of close to 800ms.

Using pathogen to handle the various plugins.

Now is there any known issue regarding this problem - am I maybe missing something installed on my system that can impact the start up time (I installed splint and cppcheck just to see if there was any difference, and there were none).

C.vim and vcscommand.vim are all quite popular plugin and frequently downloaded from vim.org.
C.vim is for c support and vcscommand is for version control system support, both are highly possible to work together.
While there's a kep mapping conflict as the title when opening a c source file. I also get the output of :verbose map cd

v \cd *@:call mmtemplates#core#InsertTemplate(g:C_Templates,"Comments.date")
Last set from /media/sf_env_share_folder/home/.vim.yann/autoload/mmtemplates/core.vim
n \cd VCSDiff
Last set from /media/sf_env_share_folder/home/.vim.yann/plugin/vcscommand.vim

Currently, is there any method to mask the \cd from c.vim? Or will this mapping be changed later on?

Hi,
i have two questions.

1. Gvim related - it's possible to bind any key to open Bash support menu? Have been searching for two days and alt+b doesn't work.
2. Is there any way to use tests without typing whole line from tests.templates? e.g. \tft, than 'readable, -r', I know i can edit tests.templates and remove 'readable' part.

Hey,

No matter what I do, I can't seem to get the libraries I specify to be linked in when compiling using \rc.

Here's the settings I've set the variables to in my vimrc:

" c.vim settings
let g:C_CCompiler='clang'
" strict compiler settings
let g:C_CFlags='-Weverything -Wno-unused-parameter -std=c99 -g -O0 -v'
" libraries
let g:C_Libs='-lcs50 -lm'

Despite specifying the libraries I want in g:C_Libs, it doesn't show up in the command output, and the build fails at the mention of a function in libcs50:

FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: i386-unknown-freebsd10.0
Thread model: posix
 "/usr/bin/clang" -cc1 -triple i386-unknown-freebsd10.0 -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -main-file-name calcdumb2.c -mrelocation-model static -mdisable-fp-elim -masm-verbose -mconstructor-aliases -target-cpu i486 -v -g -resource-dir /usr/bin/../lib/clang/3.3 -c-isystem /usr/local/include/ -c-isystem . -O0 -Weverything -Wno-unused-parameter -std=c99 -fdebug-compilation-dir /home/matt/MyProjects/Challenges/Mine -ferror-limit 19 -fmessage-length 0 -mstackrealign -fobjc-runtime=gnustep -fobjc-default-synthesize-properties -fdiagnostics-show-option -backend-option -vectorize-loops -o /tmp/calcdumb2-oheZiR.o -x c /usr/home/matt/MyProjects/Challenges/Mine/calcdumb2.c
clang -cc1 version 3.3 based upon LLVM 3.3 default target i386-unknown-freebsd10.0
ignoring nonexistent directory "/usr/bin/../lib/clang/3.3/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/include
 .
 /usr/include/clang/3.3
 /usr/include
End of search list.
 "/usr/bin/ld" --eh-frame-hdr -dynamic-linker /libexec/ld-elf.so.1 --hash-style=both --enable-new-dtags -m elf_i386_fbsd -o /usr/home/matt/MyProjects/Challenges/Mine/calcdumb2.o /usr/lib/crt1.o /usr/lib/crti.o /usr/lib/crtbegin.o -L/usr/lib /tmp/calcdumb2-oheZiR.o -L/usr/local/lib -L. -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/crtend.o /usr/lib/crtn.o
/tmp/calcdumb2-oheZiR.o: In function `main':
/usr/home/matt/MyProjects/Challenges/Mine/calcdumb2.c:29: undefined reference to `GetInt'
/usr/home/matt/MyProjects/Challenges/Mine/calcdumb2.c:31: undefined reference to `GetInt'
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Press ENTER or type command to continue

If I made a misconfiguration somewhere along the line, I can't see where it is. This also occurs with gcc.

Compiling the program with a manually crafted clang string works fine, such as:

clang -Weverything -Wno-unused-parameter -std=c99 calcdumb2.c -lcs50 -lm -o calcdumb2.o

I feel bad making a post when I'm a noob and the fault could be from me, but as far as I can tell, it's a bug, as there's no reason I can see for c.vim to not specify the libraries. What's going on here?

Thanks,
Matt

Hi,
I like this project a lot. I am just wondering can I use c-support as a vim plugin and add that to my existing vim config?

Hi,
getting a list of function calls, with possibility to jump to any, would be extremely useful.
I didn't find any software capable of doing this.
Is it even exists, and can we implement it if not?
I tried GLOBAL, but it's Pygments parser fetches variable references but not calls.

Thanks for Bash-Support!

@WolfgangMehner @FritzMehner

It's more a question, not an issue.
Let's say i want add header quards autmoatically to every new .h file. I added new template to c.preprocessor.template, but i failed to figure out how to make it add to every new file, like it does with comment.file-description-header from c.comments.template.

Of coures I can just add it to file-description-header template, but it just looks wrong. What is the right way? Or point me to the documentation describing this case. Thanks.

When I create a new cpp file I would expect the implementation comment from cpp.comments.template to be inserted at the top. On the other hand when I create a hpp file I would expect the header comment to appear the top of the file - since my last update (unfortunately I don't remember when I did it or from what version to what version I moved) the wrong comments get inserted - the header comments appear in the implementation file and the implementation comments appear in the header file. Before this update everything worked (like a charm - like everything else still does).
I can workaround the issue by placing the content of the header file beneath:

== Comments.file description impl == map:cfdi, shortcut:c, start, noindent ==

and the comments for the implementation file beneath:

== Comments.file description header == map:cfdh, shortcut:h, start, noindent ==

At this opportunity I would like to express my gratitude for this outstanding plugin that has for multiple years boosted my productivity in C/C++ programming to a great extent. Thank you very much!

hy all,

i'm trying to use bash-support through vundle.
i used the BundleInstall command to install bash-support

everything seems to have gone good, but if i try : vi test.sh
nothing works as expected :( no headers , no hotkeys working :(

btw i'm using Bundle that comes with spf13 vim plugins.

anyone maybe has a clue about that ?

Edit: i found how to activate bash-support (i'm dumb), but hotkeys still not working :(

Hi,

Is there a way to expand a macro to a specific size? Right now macros expand and much all of the characters after it like so:

Suppose NAME is 'Morgan Stanley' then the macro will expand like this ->

/*-------------------------------------------------*/
/*   name:   |NAME|         <-- COOL NAME          */

After expansion

/*-------------------------------------------------*/
/*   name:   Morgan Stanley         <-- COOL NAME          */

I though it would be really nice if a macro expansion could specify a maximum size to which it could expand and fill the non expanded space with spaces. For example above the ending comments don't line up anymore.

So is there something like the following?

Eg.

/*-------------------------------------------------------*/
/*   name:   |NAME------|         <-- COOL NAME          */

After expansion

/*--------------------------------------------------------*/
/*   name:   Morgan Stanl         <-- COOL NAME           */

Thanks,

PS: If there isn't something like that, it would be awesome if someone could give me a hint on where in the mmtemplates I could modify this to do it.

Please help me to disable one and for all this message.
I've compiled the data required, but this continues to popup.
I need this to go away forever. I don't need any header.
thanks

vim 8.0124
windows 81

The personal details (name, mail, ...) are not set in the template library.
They are used to generate comments, ...
To set them, start the setup wizard using:

• use the menu entry "Vim -> Snippets -> template setup wizard"
• use the map "\ntw" inside a Vim buffer

In the following file:

#!/usr/bin/env bash
echo "${x/ --/}" && echo hello

bash syntax highlighting is broken after that last /

The Perl support crashes in my vim giving below error, I have tried installing the way metioned in the website as well as using Vundle for Vim. The error is:

Error detected while processing ~/.vim/bundle/perl-support/ftplugin/perl.vim:
line 37:
E117: Unknown function: Perl_SetMapLeader
line 52:
E117: Unknown function: Perl_ResetMapLeader

Am I doing anything wrong during installation?

Thanks,
Dileep.

When try to run "perl" from inside vim (or gvim) on Windows 8.1 I get the error message "(possibly default) Perl Interpreter 'c:\Perl\bin\perl.exe' not executable."

Perl executable is in "d:\sbin\perl\perl\bin\perl.exe", how do I force Vim-Perl to find it.

I've already put in my vimrc this statement
let g:Perl_Perl = 'd:\sbin\perl\perl\bin\perl.exe'

I have installed this plugin (5.5alpha) with vim-plug plugin manager. My vim version is 8.1.2130. The operating system is AIX. The perl version is 5.14.2. When I open a Perl module I am getting the Errors

Error detected while processing function Perl_InitializePerlInterface:
line    7:
E488: Trailing characters: ^I^I^I# ---------------------------------------------------------------
line    8:
E488: Trailing characters: ^I^I^I# find out the version of the Perl interface
line    9:
E488: Trailing characters: ^I^I^I# ---------------------------------------------------------------
line   13:
E488: Trailing characters: ^I^I^I# ---------------------------------------------------------------
line   14:
E488: Trailing characters: ^I^I^I# Perl_RegexExplain (function)
line   15:
E488: Trailing characters: ^I^I^I# try to load the regex analyzer module; report failure
line   16:
E488: Trailing characters: ^I^I^I# ---------------------------------------------------------------
line   24:
E171: Missing :endif

Any help to fix this is very much appreciated.

For my case, I install the cvim plugin to another personal .vim.myself folder(my purpose is to share the vim configuration among virtual machines and remote hosts), then make a symbol link $HOME/.vim pointing to /xx/xx/.vim.myself.
For me, I expect this to be a user installation, and I could maintain all relevant files within my .vim.myself folder, while seems cvim will follow the symbol link to find the /xx/xx/.vim.myself then regards this as a system installation (because .vim.myself not in my home folder) and output "Please set your personal details in file /home/myname/.vim/c-support/templates/Templates".

I'm using ubuntu 14.04
vim --startuptime vim.log
times in msec
clock self+sourced self: sourced script
clock elapsed: other lines

000.006 000.006: --- VIM STARTING ---
000.126 000.120: Allocated generic buffers
000.251 000.125: locale set
000.258 000.007: window checked
000.881 000.623: inits 1
000.889 000.008: parsing arguments
000.890 000.001: expanding arguments
000.906 000.016: shell init
001.283 000.377: Termcap init
001.326 000.043: inits 2
001.495 000.169: init highlight
002.006 000.348 000.348: sourcing /usr/share/vim/vim74/debian.vim
002.629 000.341 000.341: sourcing /usr/share/vim/vim74/syntax/syncolor.vim
002.836 000.643 000.302: sourcing /usr/share/vim/vim74/syntax/synload.vim
020.788 017.865 017.865: sourcing /usr/share/vim/vim74/filetype.vim
020.829 018.734 000.226: sourcing /usr/share/vim/vim74/syntax/syntax.vim
020.851 019.294 000.212: sourcing $VIM/vimrc
020.894 000.011 000.011: sourcing $HOME/.vimrc
020.899 000.099: sourcing vimrc file(s)
023.176 000.238 000.238: sourcing /home/lf/.vim/autoload/mmtoolbox/tools.vim
023.690 000.259 000.259: sourcing /home/lf/.vim/autoload/mmtoolbox/make.vim
024.045 000.046 000.046: sourcing /home/lf/.vim/autoload/mmtemplates/core.vim
026.198 002.085 002.085: sourcing /home/lf/.vim/autoload/mmtemplates/core.vim
026.247 002.342 000.211: sourcing /home/lf/.vim/autoload/mmtemplates/core.vim
328.182 307.226 304.387: sourcing /home/lf/.vim/plugin/c.vim
328.458 000.084 000.084: sourcing /usr/share/vim/vim74/plugin/getscriptPlugin.vim
328.663 000.185 000.185: sourcing /usr/share/vim/vim74/plugin/gzip.vim
328.852 000.169 000.169: sourcing /usr/share/vim/vim74/plugin/matchparen.vim
329.329 000.457 000.457: sourcing /usr/share/vim/vim74/plugin/netrwPlugin.vim
329.370 000.011 000.011: sourcing /usr/share/vim/vim74/plugin/rrhelper.vim
329.419 000.027 000.027: sourcing /usr/share/vim/vim74/plugin/spellfile.vim
329.590 000.149 000.149: sourcing /usr/share/vim/vim74/plugin/tarPlugin.vim
329.700 000.085 000.085: sourcing /usr/share/vim/vim74/plugin/tohtml.vim
329.865 000.143 000.143: sourcing /usr/share/vim/vim74/plugin/vimballPlugin.vim
330.069 000.173 000.173: sourcing /usr/share/vim/vim74/plugin/zipPlugin.vim
330.120 000.512: loading plugins
330.127 000.007: inits 3
330.279 000.152: reading viminfo
330.287 000.008: setting raw mode
330.299 000.012: start termcap
330.327 000.028: clearing screen
330.609 000.282: opening buffers
330.637 000.028: BufEnter autocommands
330.639 000.002: editing files in windows
330.697 000.058: VimEnter autocommands
330.698 000.001: before starting main loop
331.066 000.368: first screen update

331.067 000.001: --- VIM STARTED ---

vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan 2 2014 19:39:32)
Included patches: 1-52
Modified by [email protected]
Compiled by buildd@
Huge version without GUI. Features included (+) or not (-):
+acl +farsi +mouse_netterm +syntax
+arabic +file_in_path +mouse_sgr +tag_binary
+autocmd +find_in_path -mouse_sysmouse +tag_old_static
-balloon_eval +float +mouse_urxvt -tag_any_white
-browse +folding +mouse_xterm -tcl
++builtin_terms -footer +multi_byte +terminfo
+byte_offset +fork() +multi_lang +termresponse
+cindent +gettext -mzscheme +textobjects
-clientserver -hangul_input +netbeans_intg +title
-clipboard +iconv +path_extra -toolbar
+cmdline_compl +insert_expand -perl +user_commands
+cmdline_hist +jumplist +persistent_undo +vertsplit
+cmdline_info +keymap +postscript +virtualedit
+comments +langmap +printer +visual
+conceal +libcall +profile +visualextra
+cryptv +linebreak +python +viminfo
+cscope +lispindent -python3 +vreplace
+cursorbind +listcmds +quickfix +wildignore
+cursorshape +localmap +reltime +wildmenu
+dialog_con -lua +rightleft +windows
+diff +menu -ruby +writebackup
+digraphs +mksession +scrollbind -X11
-dnd +modify_fname +signs -xfontset
-ebcdic +mouse +smartindent -xim
+emacs_tags -mouseshape -sniff -xsmp
+eval +mouse_dec +startuptime -xterm_clipboard
+ex_extra +mouse_gpm +statusline -xterm_save
+extra_search -mouse_jsbterm -sun_workshop -xpm
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -o vim -lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl -L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions

We already can jump to error place in the script.
But it would be fine if we could have also call stack in QuickFix window. That way we could jump on the stack even without debugger.
The call stack can be traced out with caller builtin, using trap on error.
We just need to tune 'errorformat' to parse it properly.

Hello,
I'm using for buffers navigation. Was looking for a way to re-map c.vim's functionality but it seems that it can be only turned off.
Though, setting let g:C_Ctrl_j = 'off' in my .vimrc does nothing.
I can see it as "off" from vim, also the placeholders are not working but the keybindin is still acting like c.vim's one (jumps after the '}' or ')' etc)

Since I updated to perl-support version 5.3.2 I get lots of spurious warnings from some used modules when running the perl-support syntax check:

Pairwise.pm|26| Useless use of a variable in void context
Pairwise.pm|27| Useless use of a variable in void context
/home/benct/perl5/perlbrew/perls/perl-5.20.2/lib/site_perl/5.20.2/Fatal.pm|535| Name "main::setsockopt" used only once: possible typo
/home/benct/perl5/perlbrew/perls/perl-5.20.2/lib/site_perl/5.20.2/Fatal.pm|535| Name "main::flock" used only once: possible typo

I get no such warnings when actually running the scripts or using perl -cw from the commandline.

Not only does this make actual errors hard to spot, what's more the module files in question are opened in the window where my script was, polluting my buffer list and forcing me to switch buffers, which is very annoying!

Patch for plugin/perl-support.vim:

@@ -2741,7 +2741,7 @@

                        use if defined $ENV{PERL_LOCAL_INSTALLATION}, lib =>    $ENV{PERL_LOCAL_INSTALLATION};

-                       eval { require Perl::Tags };
+                       eval { require Perl::Tags::Naive };
                        if ( $@ ) {
                                # Perl::Tags not loadable
                                VIM::DoCommand("let g:Perl_PerlTags = 'off'" );

The require before only tests for (and loads) Perl::Tags, but not Perl::Tags::Naive.

Vim version 7.4 on rhel6
perl-support version 5.4
perl version 5.16.3

[stbaldwin@audev04 framework][1]☢ head -1 bin/rjx.plx
#!/usr/bin/env perl
[stbaldwin@audev04 framework][1]☢ gvim bin/rjx.plx
[stbaldwin@audev04 framework][1]☢ Vim: Caught deadly signal SEGV
Vim: Finished.
[stbaldwin@audev04 framework][1]☢ tail -2 ~/.vimrc
filetype plugin on
let g:Perl_DirectRun = 'yes'

The SEGV occurs when I choose Perl, Run, update. check syntax

running perltidy seems to work ok.

I'm not sure where to start looking for the problem.

Thanks,

Steve

Hello
I've got installed perl-support by Vundle in ~/.vim/bundle/perl-support.vim. I've added to the ~/.vim/bundle/perl-support.vim/plugin/perl-support.vim:

  " ==========  Linux/Unix  ======================================================
    "
    let g:Perl_PluginDir = expand("<sfile>:p:h:h")
    "
    if match( expand("<sfile>"), resolve( expand("$HOME") ) ) == 0
        " USER INSTALLATION ASSUMED
        if match( expand("<sfile>"), g:VIMFILESDIR.'bundle' ) == 0
      " BUNDLE INSTALLATION ASSUMED
      let g:Perl_Installation               = 'bundle'
      let s:Perl_LocalTemplateFile  = g:VIMFILESDIR.'/perl-support/templates/Templates'
      let s:Perl_ToolboxDir              += [ g:Perl_PluginDir.'/autoload/mmtoolbox/' ]
    else
      let g:Perl_Installation               = 'local'
      let s:Perl_LocalTemplateFile  = g:Perl_PluginDir.'/perl-support/templates/Templates'
      let s:Perl_ToolboxDir              += [ g:Perl_PluginDir.'/autoload/mmtoolbox/' ]
    endif
    else
        " SYSTEM WIDE INSTALLATION

and currently it works with my templates from ~/.vim/perl-support/templates.
Could you check it out and possibly put in the next release?

It would be nice to have each of these plugins in their own repos.

Reasoning: I tend to clone a vim-plugin into .vim/bundle and let pathogen handle loading the plugin. In fact, I have my .vim file structure as a repo and each plugin is including as a submodule. This makes updating and backing up my configuration quite easy.

Also, contributing to your plugins would be much easier, since I am sure there are people like me who may only be interested in one or two particle plugins.

In Ubuntu 16.04, the plugin will cause the other plugins raising UnicodeDecodeError when the plugins execute python code vim.eval(g:) and other similar codes.

There are some compatibility in the pugin. If vim with python3 support loading the plugin, try the command python3 vim.eval('extend(g:, {})') in vim ex mode, it will raise the following error:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc2 in position 0: unexpected end of data

And python support has the same problem.

[dein] Vim(helptags):E154: Duplicate tag ":CMake" in file /home/solaraquarion/.cache/vim/dein/.cache/init.vim/.dein/doc/tool
boxcmake.txt

Good morning Wolfgang,

a quick question for you ...

When running a script located in "'I:/texte/_source_code/Perl/playground.p" from within VIM I get the following error message (Windows 7, gvim 7.4 patch 1-712)

C:\Windows\system32\cmd.exe /c (C:\Perl\bin\perl.EXE 'I:/texte/_source_code/Perl
/playground.pl')
ConEmuC build 141208 x64. (c) 2009-2014, [email protected]
Starting attach autorun (NewWnd=NO)
Can't open perl script "'I:/texte/_source_code/Perl/playground.pl'": Invalid argument
shell returned 22

Running the script from the command line works perfectly fine; the same is true for running it in Eclipse/EPIC.

I was just wondering if it had anything to do with the single and double quotation marks (" ' ... ' ") in :

Can't open perl script "'I:/texte/_source_code/Perl/playground.pl'"

Using the following on the Windows command line would envoke the same issue:

perl -w 'I:/texte/_source_code/Perl/playground.pl'

while the following alternatives on Windows work fine:

perl -w I:/texte/_source_code/Perl/playground.pl
perl -w "I:/texte/_source_code/Perl/playground.pl"

It is worth noting that using cygwin on Windows alows for all 3 alternatives (no quotes, single OR double quotes).

I guess my question would be how I could change the single quote to a double quote when passing a script-name from VIM to the command.

Many thanks in advance,

Oli

With a clean install of Perl-Support 5.3.1, and no .vimrc file, using MacVim 7.4.258 (Snapshot 73) under MacOSX 10.8.5, I can reproduce the bug by opening an empty perl-file, made with 'touch hat.pl'. This results in MacVim closing the window (and the file not being opened), though the MacVim application is still loaded and a new window can be opened.
The problem is the same if the file is not empty.
If I do the same with an empty Bash file there is no problem (I have Bash-Support too).

If I repeat the same with MacVim 7.3 (53), the perl-file can easily be opened.

The problem also occurs using the older version of Perl-Support I have: version 5.2pre.