WolfgangMehner
Bash Support 4.1: QuickFix List does not work without GUI
: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
@PengZheng I assume you are talking about the syntax check mechanism? Because we just found an error there. Are you sure it it works in gVim? Because the error we found should affect both Vim and gVim.
On 12/27/2013 07:27 PM, Wolfgang Mehner wrote:
@PengZheng https://github.com/PengZheng
- Do you use WIndows/Linux, 32/64bit, Vim 7.3/7.4 (:version on the Vim command line)? (I only ask for this much information since we had problems with Win/64bit recently.)
Linux 32bit, vim 7.4
- Does this problem appear only in combination with a feature of Bash support? If so, which feature?
Run a bash script with several errors within vim using \rr. All errors are indicated correctly by red arrows, but I just cannot use QuickFix List (or :cn :cp commands) to navigate around the source file.
- Do you use another plug-in which uses the quickfix mechanism? Do it work there?
No, I have not tried other plug-ins yet. Bash-Support is actually the second plug-in I installed for my vim, while eclim is the first one.
I noticed QuickFix List does works in the following simple scenario:
- compile a problematic c source file using :make
- open the quickfix window using :cwindow
- everything works as expected
— Reply to this email directly or view it on GitHub https://github.com/WolfgangMehner/vim-plugins/issues/5#issuecomment-31257133.
Peng
You can download the following file and use it to replace plugin/bash-support.vim: https://raw.github.com/WolfgangMehner/vim-plugins/622f1c7823cd1b62e73d44e84e14702e87579197/plugin/bash-support.vim Please let us know whether this resolves the issue.
On 12/28/2013 04:44 AM, Wolfgang Mehner wrote:
You can download the following file and use it to replace plugin/bash-support.vim: https://raw.github.com/WolfgangMehner/vim-plugins/622f1c7823cd1b62e73d44e84e14702e87579197/plugin/bash-support.vim Please let us know whether this resolves the issue.
— Reply to this email directly or view it on GitHub https://github.com/WolfgangMehner/vim-plugins/issues/5#issuecomment-31279342.
No, the problem is still there. I just updated the problem description with a picture attached.
Peng
We just realized that different versions of sh/bash have different error formats. Could you send us the output of: bash < our script > on the command line.
Sorry, wrong formating on my last post, I meant to say: bash < our script >
On 12/28/2013 06:34 PM, Wolfgang Mehner wrote:
Sorry, wrong formating on my last post, I meant to say: bash < our script >
— Reply to this email directly or view it on GitHub https://github.com/WolfgangMehner/vim-plugins/issues/5#issuecomment-31294097.
peng@peng-laptop:~/Desktop$ bash test1.sh test1.sh: line 22: func1: command not found
peng@peng-laptop:~/Desktop$ bash --version GNU bash, version 4.2.45(1)-release (i686-pc-linux-gnu)
Peng
Please contact me directly using
mehner at fh-swf.de
Regards, F. Mehner
