I am getting the following when running :Make or :Dispatch bash about vim-dispatch HOT 11 CLOSED

You probably want :Start bash rather than :Dispatch bash, seeing as how it's an interactive command. Still, strange error. Do you have any mc references in your bash config?

from vim-dispatch.

None. Is there a way to turn on some sort of logging to tell exactly what command/args are being run?

By the way, I forgot to mention it before but your plugin is awesome / very useful.

from vim-dispatch.

The closest thing I have found is some env function midnight-commander seems to put into my env. I do not use midnight-commander, but it is installed on this system.

mc=() { . /usr/share/mc/bin/mc-wrapper.sh
}
_=/usr/bin/env

Found via: http://stackoverflow.com/questions/9306717/malformed-environment-variables-detection-in-python

Do you read in the environment variables then try to duplicate them in some way?

from vim-dispatch.

Could it potentially be in autoload/dispatch.vim

function! dispatch#isolate(...)
let command = ['cd ' . shellescape(getcwd())]
for line in split(system('env'), "\n")
let var = matchstr(line, '^\w+\ze=')
if !empty(var) && var !=# '_'
if &shell =~# 'csh'
let command += ['setenv '.var.' '.shellescape(eval('$'.var))]
else
let command += ['export '.var.'='.shellescape(eval('$'.var))]
endif
endif
endfor
let command += a:000
let temp = tempname()
call writefile(command, temp)
return 'env -i ' . &shell . ' ' . temp
endfunction

It looks like you are duplicate the environment vars and assuming they are all on one line. But for some reason this one is not, and valid I guess.

from vim-dispatch.

Also, after doing 'unset mc'. Everything works fine. So that must be the culprit.

from vim-dispatch.

Perhaps listing getting the list of environment vars with something similar to:
http://stackoverflow.com/questions/11175842/how-to-list-all-the-environment-variables-in-vim

Then looping over them one by one would allow you to handle multi-line ones easier?

from vim-dispatch.

I don't think the environment variable listing in particular is the problem, as we're only matching lines containing =, and getting the values directly from vim. What does :echo $mc report? How about :echo shellescape($mc)?

from vim-dispatch.

@tpope I've narrow this down to a problem with exported bash functions. I'm getting a similar issue with fzf which defines a bash function fzf and exports it:

fzf() {
  /usr/bin/ruby /Users/justin/.fzf/fzf "$@"       
} 
export -f fzf > /dev/null

Killing vim, then unset fzf, then restarting Vim, allows :Make to run without problems[1]. Non-exported functions aren't picked up by Vim's environment, so dispatch.vim doesn't have a problem with them.

I'm guessing that dispatch.vim's isolate() logic introduced in #9 may be related. (Or it's a coincidence that @krismalfettone reported this a few days later.)

What does :echo $mc report? How about :echo shellescape($mc)?

In my case, :echo $fzf gives:

() {  /usr/bin/ruby /Users/justin/.fzf/fzf "$@"
}

:echo shellescape($fzf) gives:

'() {  /usr/bin/ruby /Users/justin/.fzf/fzf "$@"\
}'

[1] For reference: there is discussion on vim_dev about adding the ability to unset env vars from within vim: https://groups.google.com/d/msg/vim_dev/IIrDqVvdpOo/Q2nuImgZEtEJ

from vim-dispatch.

I've seen this shell escaping issue before. The only mystery to me is what the hell this weird function as environment variable thing is. Doesn't happen in zsh so I assume it's some bash misfeature.

from vim-dispatch.

Thanks, but I'm still getting unexpected EOF. If I open the temp file, I think I see the issue: a NUL byte is being written instead of a newline:

export fzf='() {  /usr/bin/ruby /Users/justin/.fzf/fzf "$@"^@}'

from vim-dispatch.

It works. Thanks so much!

from vim-dispatch.