quickly edit fails if EDITOR=vim

Bug #418351 reported by John C Barstow
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Quickly
Fix Released
Medium
Unassigned

Bug Description

quickly 0.1

If the default editor is set to "vim", the command fails. I would expect to see the files opened in buffers or tabs.

jbowtie@ponga-two:~/dev/nyx$ quickly edit
jbowtie@ponga-two:~/dev/nyx$ 4 files to edit
Vim: Error reading input, exiting...
Vim: Finished.

Related branches

Changed in quickly:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Rick Spencer (rick-rickspencer3) wrote :

This is working for me in the current 0.2 build. I suspect that this will start working in a couple of days when we push that release.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Indeed, I fixed it for 0.2 a couple of weeks ago. I'll add it to the changelog.

Changed in quickly:
status: Triaged → Fix Committed
milestone: none → 0.2
Revision history for this message
John C Barstow (jbowtie) wrote :

Well, it's an improvement - vim actually launches, but it doesn't seem to be editable.

The cursor is on the first line after the string "1;2005;0c"
Attempting to do anything results in vim quitting and showing the following message:

Vim: Error reading input, exiting...
Vim: Finished.

Let me know if I need to provide any more details about my setup.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Ok, I'm reputting this on the backlog for next release.
In the meanwhile, you can use gedit in unsetting EDITOR :)

Changed in quickly:
status: Fix Committed → Confirmed
milestone: 0.2 → none
status: Confirmed → Triaged
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Fixed in trunk, it now also support used sensible-editor change.

Will be released in 0.2.1

Changed in quickly:
milestone: none → 0.2.1
status: Triaged → Fix Committed
Changed in quickly:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.