On 14-May-2008, Sander Marechal wrote:
> The default editor for reportbug (vi? vim?)
There is no "default editor for reportbug" except Debian's default
editor, 'sensible-editor(1)'. This is used by 'reportbug' only if
there is no specific setting of the 'EDITOR' environment variable.
If you want to select a default editor for yourself, set your 'EDITOR'
environment variable, which will be obeyed by most programs (including
'reportbug') in preference to 'sensible-editor'.
> does not work properly inside reportbug. When I attempt to edit the
> bugreport the vi(m) statusline is repeated at the bottom and my
> keystrokes are shown. The bugreport itself is not editable.
Can you please try a few things, and see which ones cause the same
symptoms:
* echo $EDITOR
* echo $VISUAL
* run 'sensible-editor' explicitly, and try editing a few files. Check
what editor is actually running when you do this.
* run your choice of editor (e.g. nano) explicitly.
* 'export EDITOR=nano' and then try running 'reportbug' again.
> It sounds a bit strange but the attached reportbug-screen.txt should
> hopefully make it clearer. It shows the contents of my terminal
> after I pressen a couple of cursor keys.
> I have also attached my reportbug configurations, so you can see
> that I have not changed the default editor.
Places to look where your EDITOR environment variable has been set
include:
* /etc/profile, $HOME/.profile
* /etc/bash_profile, $HOME/.bash_profile
* /etc/bash.bashrc, $HOME/.bashrc
> The workaround is easy: I set a different editor (like nano)
A better workaround is to set your EDITOR variable for all sessions
and programs.
> but reportbug should work out-of-the-box of course :-)
True.
--
\ "I went to a garage sale. 'How much for the garage?' 'It's not |
`\ for sale.'" -- Steven Wright |
_o__) |
Ben Finney <b...@benfinney.id.au>