search

neowit / vim-force.com

Vim plugin for force.com
113 stars 25 forks source link

Input line is too long issue #14

Closed fred521 closed 9 years ago

fred521 commented 11 years ago

Actually, it was the question of how to run the plugin under windows OS. I tried, but failed, always got input line is too long error.

Please check my attachments, I was trying to run the command 'ApexDeploy'

the input line is too long log

neowit commented 11 years ago

@freddai, Thanks for the details. The plugin used to run on Windows without problem. I am not aware of any recent changes that might cause the issue you are having.

Let's see if I can replicate the problem using the information from the screenshot you provided.

neowit commented 11 years ago

Any idea why you have lots of ^ characters in the command line? This is not something the plugin does.

Also, when I run current version of the plugin on Win XP SP3 I do not get the command line enclosed in parentheses like your screenshot shows. Here is what proper command line shall look like (notice no parentheses or ^ characters)

C:\WINDOWS\system32\cmd.exe /c "ant -buildfile "C:\Documents and Settings\andrey\Vim\vim-force.com\apex-plugin\build.xml" -Ddest.org.name="vim-force.com" -Dproperties.path="C:\Documents and Settings\andrey\Vim\properties" -DpollWaitMillis=1000 -Dresult.file.path="c:\Documents and Settings\andrey\Vim\SFDC-Experiments\vim-force.com\.vim-force.com\describeMetadata-result.txt" describeMetadata 2>&1 |C:\bin\UnixUtils\usr\local\wbin\tee.exe "C:\temp\apex\gvim deployment\gvim-deployment-error.log""

Notice that in my example the actual command line is much longer than yours, but that does not cause any problems. So I think it has to be something related to those weird parentheses and ^ characters.

If you can not think of any reason for those extra characters then one thing you could try is to copy the whole command line generated on your machine, remove all ( ) ^ characters and try to execute it. This would prove if my theory about those erroneous characters is correct and perhaps give further ideas.

Unfortunately I do not have access to Windows 7 so can not debug it there.

The other think you could try is to downgrade your vim version to 7.3 and see if that makes any difference.

neowit commented 11 years ago

@freddai, Just a silly thought - is you Git configured properly in terms of CRLF conversion? When you cloned the repository did it convert plugin files to windows line endings? i.e. if you open plugin files (e.g. apexAnt.vim) with notepad do they look okay in terms of line endings, no ^ or anything weird at the end of each line?

fred521 commented 11 years ago

thank you for you quick response. what i found in the code of ApexAnt.vm, wherever the place using shellescape () function, it will generate additional ^.

Still working on it to figure it why that thing happen

On Tue, Aug 13, 2013 at 10:04 AM, Andrey Gavrikov notifications@github.comwrote:

@freddai https://github.com/freddai, Just a silly thought - is you Git configured properly in terms of CRLF conversion? When you cloned the repository did it convert plugin files to windows line endings? i.e. if you open plugin files (e.g. apexAnt.vim) with notepad do they look okay in terms of line endings, no ^ or anything weird at the end of each line?

— Reply to this email directly or view it on GitHubhttps://github.com/neowit/vim-force.com/issues/14#issuecomment-22580588 .

neowit commented 9 years ago

closed due to inactivity