Error unable to start editor vi

GIT описание ошибок

В статье описываются типичные ошибки или уведомления, которые возникают в GIT при работе через консоль. Эта статья будет дополняться по мере того, как я буду встречать новые заголовки, для которых сочту, что нужны дополнительные пояснения.

Your branch is ahead of ‘origin/любая_ветка’ by 12 commits.

В гите локально хранится копия репозитория. И сначала изменения происходят в ней. Для этого используется команда commit.

Сообщение выше говорит о том, что изменения в локальной копии опережают изменение я удаленной на кол-во раз. И эти изменения не отправлены в удаленный репозиторий.

Для передачи этих изменений в удаленный репозиторий используется команда push. После чего все сделанные изменения будут доступны удаленно, в том числе и для других пользователей.

hint: Waiting for your editor to close the file… error: There was a problem with the editor ‘/usr/bin/vim’.

Ошибка появляется в PhpStorm после команды git merge.

Если никакие команды не позволяют исправить редактор VIM, то можно заменить его на другой. Скажем на редактор nano.

Установка на Mac OS через Homebrew

После установки Homebrew ввести команду:

А затем поменять в PhpStorm редактор на nano:

Если редактор не установлен, то при смене будет ошибка:

error: unable to start editor ‘“nano”’

Читайте также

У сайта нет цели самоокупаться, поэтому на сайте нет рекламы. Но если вам пригодилась информация, можете лайкнуть страницу, оставить комментарий или отправить мне подарок на чашечку кофе.

Комментарии к статье “ GIT описание ошибок ” (2)

добрый день, а если выдает такую ошибку:
git commit
hint: Waiting for your editor to close the file… [program]: [program]: command not found
error: There was a problem with the editor ‘[program]’.
Please supply the message using either -m or -F option.

Похоже на то что нужно выйти из редактора в консоли.

Источник

[GeomEditorTimeOut:DMAddin] Unable to start the geometry editor.

CFD Online Discussion Forums > General Forums > General Forums [GeomEditorTimeOut:DMAddin] Unable to start the geometry editor.

—>

we have been struggling with an error trying to open DesignModeller from the Workbench (via Static Structural) double clicking on the «Geometry» tab.
The machine runs on SL65 (identical to RHEL 65).
The following error message appear in the .ansys/. log-files
[GeomEditorTimeOutMAddin] Unable to start the geometry editor.
It takes about 5 minutes, until the error popps up.
We are in contact with ANSYS support which has redirected me to CADFEM without finding a solution. We have checked many possibilities regarding licensing issues. It works on Opensuse 13.1 and on Win7, so I don’t think it’s a license issue (which is administred organisation wide).
Did anyone experience the same error or issue? Any suggestions?
We have had this error on that machine as of Nov. 6 2014. Before (last working date Oct. 23), it worked fine. We newly installed 15.0.7 to no avail.
Something that is striking is that on Nov. 4th, more than 50 graphics-related packages had been updated (I can supply the lengthy list if needed).

Thanks for your pennies,
Christian

browsing through the ANSYS forums, we found the following hint, which works now:

Knowledge Resources: Solutions

#2037921
Problem Description: Any Mechanical application — Mechanical, Meshing, Design-Modeler & FEModeler will not run after a Red Hat 6.x update: RHSA-2014:1436. Starting Design Modeler from WorkBench simply hangs for two to three minutes and then presents an error: «Unable to start the geometry editor.» Mechanical also fails to start. Platform — Redhat6.x or derivatives

Product Family: Installation, Licensing & Systems
Product: ANSYS Mechanical
Version: 15.0
Area: Installation Process
SubArea: Other
Last Updated: Nov 14 2014

The fix is a simple rename of a folder. In the path below rename the X11 folder to Old-X11

Источник

ANSYS 13,14 or 14.5 unable to start mechanical editor

CFD Online Discussion Forums > Software User Forums > Software User Forums ANSYS 13,14 or 14.5 unable to start mechanical editor

—>

Hi Everybody,
I researched a lot of forums to solve this problem. But they don’t help me.
Ansys licences are works very well. Workbench is opened normally.
But if I want to start to geometry editor. Opss error: Ansyswbu.exe encountered a problem. I can not open the mechanical editor.

I tried below before installation;
-diasble antivirus
-Vga card update
-disable firewall
-delete old versions
-add «a system environment» ANS_OLD_ATTACH=1

I did not manage to solve it.
Please help

System: win7 64bit

We had the same situation (same symptoms, same attempts to remedy) and found that by doing a repair reinstall of Windows 7 (it rolls the Windows 7 files back to their original versions but keeps all your program info and data intact) the summary that displayed when it finished identified some core Windows files that had been changed, files that were associated with our VPN software client. It replaced these files and ANSYS then worked. This may not solve the issue for you but, as you found (and we also found), there aren’t a lot of solutions for this particular problem; this approach may reveal a problem and has the advantage of being simple to try and non-destructive.

There’s a useful summary of the possible Windows 7 repair reinstall options here:

I am having the same problem as fesat181. I have tried uninstalling/reinstalling ANSYS 14 and 14.5 to get rid of the problem, to no avail.

I have tried the following typically recommended fixes:

• ATI A.I. and 3D settings
• ANS_OLD_ATTACH = 1
• Disable firewall
• Renaming ANSYS folders in %temp% and %AppData%

Anyone have any suggestions other than a Win7 reinstall?

I’m running Win7 64-bit

How you ever checked your third party software. I have had the same problems. I had a laptop and pc and altough I installed on both of them one of them work correctly and the other one does not work As soon as I clicked on gemetry on laptop it told me unable to start geometry editor while it works well on pc.
It is worth mentioing that In installation on My PC I also did not disable firewall and antivirus but it works well. I thought it is third party software problem. I checked the program and features and I understand that by the help of installing Micorsoft Visual C++ 2005 to 2010 all of them which compatible with your windows (depends on 64 bit or 32 bit windows which you have) it will remove.Maybe your problem also be removed by the help of Installing whole the packeage of microsoftvisuial C++ redistributor from 2005 to 2010.

please tell me if it works or not. Maybe I have another suggestion for you guys.

Источник

Launching TextEdit from git #6

git is giving me an error when it tries to launch TextEdit, and I’m wondering if someone might be able to help me out with it:

First I tried the simple command that was in the walkthrough to make TextEdit the editor:
git config —global core.editor «TextEdit -w»

So I got a little more specific:

git config —global core.editor «/Applications/TextEdit.app -w»

and if I try a commit without a message, it returns the error message:

(As long as I include a message with -m , it doesn’t bother with TextEdit and everything works just fine)

On a whim, I tried without the -w , and got

And I think that’s where I’m at. any ideas?

Thanks in advance!

The text was updated successfully, but these errors were encountered:

That is definitely my bad! Try it all lowercase and let me know if that fixes it.

git config —global core.editor «textedit -w»

I’ll update the webpage now!

Unfortunately, still not working. What’s odd is that if I leave git out of it:
$ open «/Applications/TextEdit.app»
works fine.

with or without git, I get the «command not found» unless I specify to look in the /Applications folder.

$ open textedit or $ open textedit.app or $open TextEdit.app . or even just $ textedit all return command not found .

Updated 5:00pm: So, how deep down the rabbit hole do you want to go on here, and/or would it be easier to skip TextEdit entirely and remind myself how to use emacs?

If I’m very explicit:
git config —global core.editor «/Applications/TextEdit.app/Contents/MacOS/TextEdit -w»
I can get TextEdit to start up in the background, but it doesn’t actually give me a window to enter a commit message. Might need to play with more flags to make that happen.

I can get TextEdit to open and give me a window with: git config —global core.editor open (uses the default system application for plain text, which in my case is TextEdit). Success!

. but, as soon as TextEdit opens, before I have a chance to type and save a commit message, I get

because git isn’t waiting for it. If I try to add the -w flag, bash gets mad because open doesn’t accept that flag.

What happens when you include a commit message? E.g.,

By default, git requires a commit message to enforce best practices in using version control. Commit messages should be concise but meaningful; generally a brief explanation of why a change was made, rather than what was done since you can just look at the change directly.

The real test of whether the TextEdit business will work will be when we have to do a merge commit.

I like knowing about the core.editor open option! I’ll add that to the list.

As long as I give it a message, it works just fine- it’s just when it tries to open an external text editor to do a longer commit message.

It also works fine with emacs:

when I commit, launches emacs, where I can enter a message, save it, and quit emacs and come back to this:

Also, open works best for me if I use it with -W -n as options:

it seems to only give me trouble if I try to refer to text edit explicitly, which is weird, and I’d like to know what’s causing it. but I’m OK with either using open or emacs, so I think I’m good for now!

I wonder if this has something to do with opening a text editor external to the shell? This is why emacs or nano or somesuch works normally.

I was curious about that as well. but it does strike me as odd that it works with open but not with calling TextEdit explicitly, even if I use the -W -n flags.

What is TextEdit? Did I miss the class when this was covered? Oops.

I think we went over it pretty quickly. I wouldn’t worry about this too much for now, as long as you include a message in your commits ( git commit -m «I made my commit for some reason that I describe here» ).

But, if you’re curious: TextEdit is a simple, plain text editing program. The context of this issue is that git won’t let you make a commit without a message explaining why. If you don’t include one with the -m flag, you can tell git to open a small message file in a text editor, where you can leave a longer, more detailed message. TextEdit is the built-in text editor on Macs, which has a nice simple graphical user interface. There are lots of other alternatives that are on the command line, but those can be a bit trickier to use.

Источник

GIT описание ошибок

В статье описываются типичные ошибки или уведомления, которые возникают в GIT при работе через консоль. Эта статья будет дополняться по мере того, как я буду встречать новые заголовки, для которых сочту, что нужны дополнительные пояснения.

Your branch is ahead of ‘origin/любая_ветка’ by 12 commits.

В гите локально хранится копия репозитория. И сначала изменения происходят в ней. Для этого используется команда commit.

Сообщение выше говорит о том, что изменения в локальной копии опережают изменение я удаленной на кол-во раз. И эти изменения не отправлены в удаленный репозиторий.

Для передачи этих изменений в удаленный репозиторий используется команда push. После чего все сделанные изменения будут доступны удаленно, в том числе и для других пользователей.

hint: Waiting for your editor to close the file… error: There was a problem with the editor ‘/usr/bin/vim’.

Ошибка появляется в PhpStorm после команды git merge.

Если никакие команды не позволяют исправить редактор VIM, то можно заменить его на другой. Скажем на редактор nano.

Установка на Mac OS через Homebrew

После установки Homebrew ввести команду:

А затем поменять в PhpStorm редактор на nano:

Если редактор не установлен, то при смене будет ошибка:

error: unable to start editor ‘“nano”’

Читайте также

У сайта нет цели самоокупаться, поэтому на сайте нет рекламы. Но если вам пригодилась информация, можете лайкнуть страницу, оставить комментарий или отправить мне подарок на чашечку кофе.

Комментарии к статье “ GIT описание ошибок ” (2)

добрый день, а если выдает такую ошибку:
git commit
hint: Waiting for your editor to close the file… [program]: [program]: command not found
error: There was a problem with the editor ‘[program]’.
Please supply the message using either -m or -F option.

Похоже на то что нужно выйти из редактора в консоли.

Источник

Error launching editor: unable to launch the editor «vim» #7318

Comments

tasinet commented Jul 24, 2019 •

1. What kops version are you running? The command kops version , will display
this information.

Version 1.11.1 (git-cb8143c)
Installed via snap on a 5.1.16 kernel Ubuntu

2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.

Client: v1.15.1
Server: v1.9.3

3. What cloud provider are you using?

4. What commands did you run? What is the simplest way to reproduce this issue?

When I attempt to edit anything:

5. What happened after the commands executed?

6. What did you expect to happen?

7. Please provide your cluster manifest. Execute
kops get —name my.example.com -o yaml to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.

8. Please run the commands with most verbose logging by adding the -v 10 flag.
Paste the logs into this report, or in a gist and provide the gist link here.

9. Anything else do we need to know?

Fails with other $EDITOR values as well:

absolute paths in $EDITOR didn’t have any effect:

which vim and which nano return /usr/bin/vim and /bin/nano , which are in $PATH and executable.

Probably unrelated, but my own machine (not part of this or any cluster) is somewhy running Kubelet, which is in a spawn loop. Removed it; no change.

The text was updated successfully, but these errors were encountered:

Источник

Launching TextEdit from git #6

Comments

bseitz234 commented Sep 11, 2015

git is giving me an error when it tries to launch TextEdit, and I’m wondering if someone might be able to help me out with it:

First I tried the simple command that was in the walkthrough to make TextEdit the editor:
git config —global core.editor «TextEdit -w»

So I got a little more specific:

git config —global core.editor «/Applications/TextEdit.app -w»

and if I try a commit without a message, it returns the error message:

(As long as I include a message with -m , it doesn’t bother with TextEdit and everything works just fine)

On a whim, I tried without the -w , and got

And I think that’s where I’m at. any ideas?

Thanks in advance!

The text was updated successfully, but these errors were encountered:

jdunic commented Sep 11, 2015

That is definitely my bad! Try it all lowercase and let me know if that fixes it.

git config —global core.editor «textedit -w»

I’ll update the webpage now!

bseitz234 commented Sep 11, 2015

Unfortunately, still not working. What’s odd is that if I leave git out of it:
$ open «/Applications/TextEdit.app»
works fine.

with or without git, I get the «command not found» unless I specify to look in the /Applications folder.

$ open textedit or $ open textedit.app or $open TextEdit.app . or even just $ textedit all return command not found .

bseitz234 commented Sep 11, 2015

Updated 5:00pm: So, how deep down the rabbit hole do you want to go on here, and/or would it be easier to skip TextEdit entirely and remind myself how to use emacs?

If I’m very explicit:
git config —global core.editor «/Applications/TextEdit.app/Contents/MacOS/TextEdit -w»
I can get TextEdit to start up in the background, but it doesn’t actually give me a window to enter a commit message. Might need to play with more flags to make that happen.

I can get TextEdit to open and give me a window with: git config —global core.editor open (uses the default system application for plain text, which in my case is TextEdit). Success!

. but, as soon as TextEdit opens, before I have a chance to type and save a commit message, I get

because git isn’t waiting for it. If I try to add the -w flag, bash gets mad because open doesn’t accept that flag.

jdunic commented Sep 11, 2015

What happens when you include a commit message? E.g.,

By default, git requires a commit message to enforce best practices in using version control. Commit messages should be concise but meaningful; generally a brief explanation of why a change was made, rather than what was done since you can just look at the change directly.

The real test of whether the TextEdit business will work will be when we have to do a merge commit.

I like knowing about the core.editor open option! I’ll add that to the list.

bseitz234 commented Sep 11, 2015

As long as I give it a message, it works just fine- it’s just when it tries to open an external text editor to do a longer commit message.

It also works fine with emacs:

when I commit, launches emacs, where I can enter a message, save it, and quit emacs and come back to this:

Also, open works best for me if I use it with -W -n as options:

it seems to only give me trouble if I try to refer to text edit explicitly, which is weird, and I’d like to know what’s causing it. but I’m OK with either using open or emacs, so I think I’m good for now!

jebyrnes commented Sep 12, 2015

I wonder if this has something to do with opening a text editor external to the shell? This is why emacs or nano or somesuch works normally.

bseitz234 commented Sep 14, 2015

I was curious about that as well. but it does strike me as odd that it works with open but not with calling TextEdit explicitly, even if I use the -W -n flags.

klarraga commented Sep 16, 2015

What is TextEdit? Did I miss the class when this was covered? Oops.

bseitz234 commented Sep 16, 2015

I think we went over it pretty quickly. I wouldn’t worry about this too much for now, as long as you include a message in your commits ( git commit -m «I made my commit for some reason that I describe here» ).

But, if you’re curious: TextEdit is a simple, plain text editing program. The context of this issue is that git won’t let you make a commit without a message explaining why. If you don’t include one with the -m flag, you can tell git to open a small message file in a text editor, where you can leave a longer, more detailed message. TextEdit is the built-in text editor on Macs, which has a nice simple graphical user interface. There are lots of other alternatives that are on the command line, but those can be a bit trickier to use.

Источник

[GeomEditorTimeOut:DMAddin] Unable to start the geometry editor.

CFD Online Discussion Forums > General Forums > General Forums [GeomEditorTimeOut:DMAddin] Unable to start the geometry editor.

—>

we have been struggling with an error trying to open DesignModeller from the Workbench (via Static Structural) double clicking on the «Geometry» tab.
The machine runs on SL65 (identical to RHEL 65).
The following error message appear in the .ansys/. log-files
[GeomEditorTimeOutMAddin] Unable to start the geometry editor.
It takes about 5 minutes, until the error popps up.
We are in contact with ANSYS support which has redirected me to CADFEM without finding a solution. We have checked many possibilities regarding licensing issues. It works on Opensuse 13.1 and on Win7, so I don’t think it’s a license issue (which is administred organisation wide).
Did anyone experience the same error or issue? Any suggestions?
We have had this error on that machine as of Nov. 6 2014. Before (last working date Oct. 23), it worked fine. We newly installed 15.0.7 to no avail.
Something that is striking is that on Nov. 4th, more than 50 graphics-related packages had been updated (I can supply the lengthy list if needed).

Thanks for your pennies,
Christian

browsing through the ANSYS forums, we found the following hint, which works now:

Knowledge Resources: Solutions

#2037921
Problem Description: Any Mechanical application — Mechanical, Meshing, Design-Modeler & FEModeler will not run after a Red Hat 6.x update: RHSA-2014:1436. Starting Design Modeler from WorkBench simply hangs for two to three minutes and then presents an error: «Unable to start the geometry editor.» Mechanical also fails to start. Platform — Redhat6.x or derivatives

Product Family: Installation, Licensing & Systems
Product: ANSYS Mechanical
Version: 15.0
Area: Installation Process
SubArea: Other
Last Updated: Nov 14 2014

The fix is a simple rename of a folder. In the path below rename the X11 folder to Old-X11

Источник

Launching TextEdit from git #6

Comments

bseitz234 commented Sep 11, 2015

git is giving me an error when it tries to launch TextEdit, and I’m wondering if someone might be able to help me out with it:

First I tried the simple command that was in the walkthrough to make TextEdit the editor:
git config —global core.editor «TextEdit -w»

So I got a little more specific:

git config —global core.editor «/Applications/TextEdit.app -w»

and if I try a commit without a message, it returns the error message:

(As long as I include a message with -m , it doesn’t bother with TextEdit and everything works just fine)

On a whim, I tried without the -w , and got

And I think that’s where I’m at. any ideas?

Thanks in advance!

The text was updated successfully, but these errors were encountered:

jdunic commented Sep 11, 2015

That is definitely my bad! Try it all lowercase and let me know if that fixes it.

git config —global core.editor «textedit -w»

I’ll update the webpage now!

bseitz234 commented Sep 11, 2015

Unfortunately, still not working. What’s odd is that if I leave git out of it:
$ open «/Applications/TextEdit.app»
works fine.

with or without git, I get the «command not found» unless I specify to look in the /Applications folder.

$ open textedit or $ open textedit.app or $open TextEdit.app . or even just $ textedit all return command not found .

bseitz234 commented Sep 11, 2015

Updated 5:00pm: So, how deep down the rabbit hole do you want to go on here, and/or would it be easier to skip TextEdit entirely and remind myself how to use emacs?

If I’m very explicit:
git config —global core.editor «/Applications/TextEdit.app/Contents/MacOS/TextEdit -w»
I can get TextEdit to start up in the background, but it doesn’t actually give me a window to enter a commit message. Might need to play with more flags to make that happen.

I can get TextEdit to open and give me a window with: git config —global core.editor open (uses the default system application for plain text, which in my case is TextEdit). Success!

. but, as soon as TextEdit opens, before I have a chance to type and save a commit message, I get

because git isn’t waiting for it. If I try to add the -w flag, bash gets mad because open doesn’t accept that flag.

jdunic commented Sep 11, 2015

What happens when you include a commit message? E.g.,

By default, git requires a commit message to enforce best practices in using version control. Commit messages should be concise but meaningful; generally a brief explanation of why a change was made, rather than what was done since you can just look at the change directly.

The real test of whether the TextEdit business will work will be when we have to do a merge commit.

I like knowing about the core.editor open option! I’ll add that to the list.

bseitz234 commented Sep 11, 2015

As long as I give it a message, it works just fine- it’s just when it tries to open an external text editor to do a longer commit message.

It also works fine with emacs:

when I commit, launches emacs, where I can enter a message, save it, and quit emacs and come back to this:

Also, open works best for me if I use it with -W -n as options:

it seems to only give me trouble if I try to refer to text edit explicitly, which is weird, and I’d like to know what’s causing it. but I’m OK with either using open or emacs, so I think I’m good for now!

jebyrnes commented Sep 12, 2015

I wonder if this has something to do with opening a text editor external to the shell? This is why emacs or nano or somesuch works normally.

bseitz234 commented Sep 14, 2015

I was curious about that as well. but it does strike me as odd that it works with open but not with calling TextEdit explicitly, even if I use the -W -n flags.

klarraga commented Sep 16, 2015

What is TextEdit? Did I miss the class when this was covered? Oops.

bseitz234 commented Sep 16, 2015

I think we went over it pretty quickly. I wouldn’t worry about this too much for now, as long as you include a message in your commits ( git commit -m «I made my commit for some reason that I describe here» ).

But, if you’re curious: TextEdit is a simple, plain text editing program. The context of this issue is that git won’t let you make a commit without a message explaining why. If you don’t include one with the -m flag, you can tell git to open a small message file in a text editor, where you can leave a longer, more detailed message. TextEdit is the built-in text editor on Macs, which has a nice simple graphical user interface. There are lots of other alternatives that are on the command line, but those can be a bit trickier to use.

Источник

error: There was a problem with the editor 'vi'.
Please supply the message using either -m or -F option.

Ответы:

git config --global core.editor /usr/bin/vim

git config --global core.editor $(which vim)

Comments

Sometimes git puts this message:

> hint: Waiting for your editor to close the file...
> error: There was a problem with the editor 'vi'.

Just do this!

> Git Commit Problem: "error: There was a problem with the editor 'vi'"
> VundleVim/Vundle.vim#167