Error There Was A Problem With The Editor
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 593 Star 12,941 Fork 1,564 VundleVim/Vundle.vim Code Issues 90 Pull requests 42 Projects 0 Wiki Pulse Graphs New error there was a problem with the editor 'vi' git issue Git Commit Problem: "error: There was a problem with the editor 'vi'"
Error There Was A Problem With The Editor 'vi'
#167 Closed codyaray opened this Issue Apr 22, 2012 · 23 comments Projects None yet Labels None yet git commit error there was a problem with the editor 'vi' Milestone No milestone Assignees No one assigned 22 participants and others codyaray commented Apr 22, 2012 I'm just starting to use Vundle and I'm running into an error when editing git commit there was a problem with the editor 'vi' a Git message using the .vimrc setup from the README. When I try to save any git message in vim, I get the following error. $ git commit error: There was a problem with the editor 'vi'. Please supply the message using either -m or -F option. I've tracked this down to the initial filetype off directive (marked as required in the README). I
Not Committing Merge; Use 'git Commit' To Complete The Merge.
don't understand why its causing this issue, but after commenting out the line, but this re-enabled Git commit editing in vim. Can you shed some light on why its "required" to disable filetype detection before using vundler? And then to re-enable it (using filetype plugin indent on) later on? FWIW, my vim version: $ vim --version VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jun 24 2011 20:00:09) Compiled by root@apple.com Normal version without GUI. Features included (+) or not (-): -arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset +cindent -clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments -conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path +find_in_path +float +folding -footer +fork() -gettext -hangul_input +iconv +insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent +listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape -mouse_dec -mouse_gpm -mouse_jsbterm -mouse_netterm -mouse_sysmouse +mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra -perl +persistent_undo +postscript +printer -profile -python -python3 +quickfix +reltime -rightleft -ruby +scrollbind +signs +smartindent -sniff +startuptime +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp -x
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about git vi editor Stack Overflow the company Business Learn more about hiring developers or posting ads with git commit error please tell me who you are us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is
Git Vi Commands
a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Git Commit Error terminal with the editor up vote 1 down vote favorite I'm https://github.com/VundleVim/Vundle.vim/issues/167 having some troubles with the command git commit. I did a git commit but unfortunately I've pressed Ctrl+Z instead of Ctrl+X to close, so now when I git commit again, it gives me this error: error: editor died of signal 11 error: There was a problem with the editor 'editor'. `Please, specific the message using option -m or -F. ` Actually I don't know how to fix this error. The operating http://stackoverflow.com/questions/36012976/git-commit-error-terminal-with-the-editor system that I'm running is Ubuntu 15.10. git git-commit share|improve this question asked Mar 15 at 13:40 Luke Smith 298 add a comment| 5 Answers 5 active oldest votes up vote 0 down vote accepted It seems like you're using the nano editor. When you hit Ctrl+Z you suspended the editor something that seems to happen. Now git tells you that your editor is broken. Try to wake up nano by entering fg or kill the process with killall nano. share|improve this answer answered Mar 15 at 13:53 Johannes Thorn 516110 any nano process was found (i've used killall nano) and fg did nothing and the bash told me that fg is inexistent. So how can I recover it? i've already restarded the PC twice and still giving me that error using only git commit command instead of git commit -m
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us http://stackoverflow.com/questions/1799891/why-do-i-get-a-warning-after-i-say-git-commit Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Why do I get a warning after I say there was “git commit .” up vote 8 down vote favorite 4 I get the error below after I run "git commit ." CSApprox needs gui support - not loading. See :help |csapprox-+gui| for possible workarounds. Error detected while processing /Users/{username}/.vim/plugin/syntastic.vim: line 94: E319: Sorry, the command is not available in this version: sign define SyntasticError text=>> texthl=error line 95: E319: Sorry, the command is not available in this there was a version: sign define SyntasticWarning text=>> texthl=todo Press ENTER or type command to continue error: There was a problem with the editor 'vi'. Please supply the message using either -m or -F option. Any ideas why this might be happening? I am on a mac. Thanks for your help. git osx share|improve this question asked Nov 25 '09 at 20:57 iJK 1,83054674 add a comment| 5 Answers 5 active oldest votes up vote 11 down vote accepted It looks like your git editor is not set and vi has a messed up plugin or something on your mac. Try using the -m "comment here" paramter on your commit. I would suggest mv ~/.vim ~/.vimbak and try running vi again. share|improve this answer edited Nov 25 '09 at 21:42 answered Nov 25 '09 at 21:00 Courtney Faulkner 1,1541014 Yes, an issue with a plugin. I was totally confused why it was trying to launch an editor, but now I understand. The switch "-m" totally worked... I guess I should read up on all the available switches –iJK Nov 25 '09 at 21:33 add a comment| up vote 19 down vote This will solve this problem: $ git config --global core.editor /usr/bin/