Re: Passing " &> " shell-command string to shell

On Tuesday, October 29, 2013 2:15:56 AM UTC-4, Gary Johnson wrote:
> On 2013-10-28, AlmostSurely wrote:
>
> > On Monday, October 28, 2013 3:15:33 PM UTC-4, Gary Johnson wrote:
>
> > > On 2013-10-28, AlmostSurely wrote:
>
> > > > On Monday, October 28, 2013 2:06:11 PM UTC-4, AlmostSurely wrote:
>
> > > > > Consider the following function,
>
> > > > >
>
> > > > > function! Compile()
>
> > > > > :cmd_string = "g++ -std=c++11 " . expand("%") . " &> " . expand("%:r") . ".log"
>
> > > > > :execute "silent !" . cmd_string
>
> > > > > endfunction
>
> > > > >
>
> > > > > The simple goal is to compile with g++, writing any compiler output to a log file.
>
> > > > > I'm having trouble passing the " &> " term to the shell.
>
> > > > > Suppose % expands to file.cpp, then adding the line,
>
> > > > >
>
> > > > > :execute "!echo " . cmd_string
>
> > > > >
>
> > > > > Produces:
>
> > > > >
>
> > > > > g++ -std=c++11 file.cpp
>
> > > > >
>
> > > > > So the " &> " doesn't even make it to the shell. Any help is much appreciated.
>
> > >
>
> > > :execute "!echo " . cmd_string
>
> > >
>
> > > evaluates to
>
> > >
>
> > > :!echo g++ -std=c++11 file.cpp &> file.log
>
> > >
>
> > > which echoes "g++ -std=c++11 file.cpp" to file.log.
>
> > >
>
> > > I verified that result using Vim 7.4.52 started as "vim -N -u NONE
>
> > > file.cpp" on a system running Fedora 11.
>
> > >
>
> > > So it works as expected for me.
>
> > >
>
> > > Regards,
>
> > > Gary
>
> >
>
> > Hi Gary, this is with Vim 7.4 with spf13, xterm-256color, on Ubuntu 13.10.
>
> >
>
> > I've been playing around with it and changing the function to:
>
> > ==========================================
>
> > function! Compile()
>
> > :let cmd_string = "g++ -std=c++11 " . expand("%") . ' \&\> ' . expand("%:r") . ".log"
>
> > :execute "!echo " . cmd_string
>
> > :execute "!" . cmd_string
>
> > endfunction
>
> > ==========================================
>
> >
>
> > Produces output:
>
> > ==========================================
>
> > g++ -std=c++11 file.cpp &> file.log
>
> >
>
> > Press ENTER or type command to continue
>
> > g++: error: &>: No such file or directory
>
> > g++: error: file.log: No such file or directory
>
> >
>
> > shell returned 1
>
> >
>
> > Press ENTER or type command to continue
>
> > ==========================================
>
> >
>
> > But using the function in the OP does not produce the &> file.log on my machine even... Any ideas?
>
>
>
> Quoting the &> as you did (\&\>) removes the special meaning of
>
> those characters to the shell, so the shell passes them to g++ which
>
> sees them as a file name. Also, without the &> redirection, the
>
> shell also sees file.log as an argument to be passed to g++ and g++
>
> can't find that file, either.
>
>
>
> If I remove that quoting from &> so that the :let command in that
>
> function becomes
>
>
>
> :let cmd_string = "g++ -std=c++11 " . expand("%") . ' &> ' . expand("%:r") . ".log"
>
>
>
> then create an empty file.cpp, open it in vim, source the Compile()
>
> function and execute
>
>
>
> :call Compile()
>
>
>
> I get an output of
>
>
>
> :!echo g++ -std=c++11 file.cpp &> file.log
>
> :!g++ -std=c++11 file.cpp &> file.log
>
>
>
> shell returned 1
>
>
>
> Press ENTER or type command to continue
>
>
>
> and file.log contains
>
>
>
> cc1plus: error: unrecognized command line option "-std=c++11"
>
>
>
> (I must have an old version of gcc.) If I use the function from the
>
> OP, with the added let, I get the same error message in file.log.
>
>
>
> Nothing is coming to mind as a reason for it behaving differently
>
> for you. You mentioned that you use spf13. Have you tried your
>
> function alone, without your ~/.vimrc or any plugins, that is,
>
> started as
>
>
>
> vim -N -u NONE
>
>
>
> ?
>
>
>
> Regards,
> NONE
> Gary

Good morning Gary. Yep, seems like it works when launched with,

$ vim -u NONE file.cpp

So the spf13's .vimrc seems to be conflicting somehow... Unfortunately though, it's 1100+ lines of code... Any ideas what kind of variables/commands I should investigate in the .vimrc? I'll start a bug report on Steve Francia's github (https://github.com/spf13/spf13-vim). Thanks!

--
--
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.