editor paths containing spaces are not parsed correctly
Bug #220331 reported by
Tom X. Tobin
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Martin Pool |
Bug Description
In bzr's commit message editor support, editor paths containing spaces are incorrectly parsed; there is no way to work around this (e.g., by escaping spaces with backslashes).
This behavior is due to bzrlib.
(Discovered in bzr 1.4rc2)
Related branches
lp:~mbp/bzr/220331-editor-path
- Vincent Ladeuil: Approve
- Martin Pool: Pending requested
-
Diff: 117 lines (+40/-10)4 files modifiedbzrlib/cmdline.py (+6/-2)
bzrlib/msgeditor.py (+3/-2)
bzrlib/tests/test_msgeditor.py (+17/-6)
doc/en/user-guide/configuring_bazaar.txt (+14/-0)
description: | updated |
description: | updated |
Changed in bzr: | |
assignee: | nobody → korpios |
status: | Triaged → In Progress |
Changed in bzr: | |
assignee: | Tom X. Tobin (tomxtobin) → Martin Pool (mbp) |
Changed in bzr: | |
milestone: | none → 2.4b1 |
status: | In Progress → Fix Released |
To post a comment you must log in.
Seems like we could use "shlex.split()" or something else that would let you quote the path with spaces.
We need to *allow* for arguments, because sometimes you have to run the editor with flags. (For example, you need to run 'gvim -f' so that it doesn't disconnect from the calling process, so we know when you are finished editing.)