gets confused when editor is killed
Bug #176350 reported by
Dato Simó
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned | ||
bzr (Debian) |
Fix Released
|
Unknown
|
Bug Description
(This comes from http://
-8<-
With cvs or svn, when you want to cancel a commit when the editor is
already open, you can kill the editor (SIGTERM). This works in bzr
as well, but it prints out
bzr: ERROR: Could not start any editor.
Please specify one with:
- $BZR_EDITOR
- editor=/some/path in /home/pei/
- $VISUAL
- $EDITOR
It could be a little smarter to distinguish the case between an editor
not being able to start and and editor exiting with a nonzero exit status.
->8-
affects /products/bzr
Changed in bzr: | |
assignee: | nobody → jelmer |
status: | New → Triaged |
assignee: | jelmer → nobody |
importance: | Undecided → Low |
Changed in bzr: | |
status: | Triaged → Confirmed |
Changed in bzr (Debian): | |
status: | Unknown → Confirmed |
Changed in bzr (Debian): | |
status: | Confirmed → Fix Released |
tags: | added: check-for-breezy |
To post a comment you must log in.