Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

codi from shell wrapper with filename not allowing input #63

Open
rbowden91 opened this issue Mar 1, 2017 · 5 comments
Open

codi from shell wrapper with filename not allowing input #63

rbowden91 opened this issue Mar 1, 2017 · 5 comments
Labels

Comments

@rbowden91
Copy link

I'm on OS X, with a compiled-from-source vim 8. Basically my entire vimrc, minus Vundle stuff for codi, is commented out. When I try opening with a filename, I can't type anything. If the filename happens to be an existing file, I can type, but nothing shows up in the codi righthand side (this isn't shown in the screencast).

https://asciinema.org/a/0s5bg7nndgc5cn96s01dbrrwk

Script:
BSD December 4, 2013 BSD

Vim version: http://pastebin.com/pcQ34Nba
Codi log (for the error case): http://pastebin.com/i2xZuEh9

@metakirby5
Copy link
Owner

Would you mind pasting your shell wrapper code? It's possible that you're using an old revision of it which had a bug.

@rbowden91
Copy link
Author

Yeah, I think I'm using the most recent version in the README. Thanks for your help!!

# Codi
# Usage: codi [filetype] [filename]
codi() {
  local syntax="${1:-python}"
  shift
  vim -c \
    "let g:startify_disable_at_vimenter = 1 |\
    set bt=nofile ls=0 noru nonu nornu |\
    hi ColorColumn ctermbg=NONE |\
    hi VertSplit ctermbg=NONE |\
    hi NonText ctermfg=0 |\
    Codi $syntax" "$@"
}

@metakirby5 metakirby5 added the bug label Mar 6, 2017
@metakirby5
Copy link
Owner

Unfortunately, I can't seem to reproduce this :( To narrow down what might be causing the problem, could you try reproducing this with the synchronous flag set?

@rbowden91
Copy link
Author

That didn't fix things for me. However, if I remove the "set buftype=nofile" from the shell command, then things seem to work perfectly fine. Is that supposed to prevent quit warnings on that right-side buffer??

@rbowden91
Copy link
Author

Sorry, "bt=nofile"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants