Package: reportbug
Version: 3.29.5
Severity: normal

Hi.

If someone installs "vim" (and please note that I said "vim", not "nvi"
or other vi clone), it's very likely that it really wants to use it,
specially in single user machines. But if someone sets the EDITOR
environment variable to "vim", it's almost 100% sure that this person
wants it as editor.

I've read the other bug reports and the manpage, and I agree with you
that maybe in a light installation of Debian, which IIRC, installs "nvi"
and "nano" by default, it's not a good idea to have "nvi" with more
priority than other editors. But if the user has customised the
installation setting EDITOR, and installing vim, its pretty annoying
forcing that user to either set a flag, a mode of operation, or adding
another configuration file to the system. It may not be if you use only
a computer, but certainly it is if you use 3 or 4, or you set up new
systems frequently.

So, my point is: if the user sets EDITOR, respect it and don't ask to
change alternatives, because it doesn't make any sense. Actually, nano
has more priority than vim.

Thanks in advance.

PS: Oh, and, in my very humble opinion, the editor question at start,
may be a good workaround for a vi clone having a high priority, but it
should be a temporal solution while the maintainers of that package fix
this.

-- Package-specific info:
** Environment settings:
EDITOR="vim"
DEBEMAIL="[EMAIL PROTECTED]"
DEBFULLNAME="Alejandro Exojo Piqueras"

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-amd64
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)

Versions of packages reportbug depends on:
ii  python                        2.4.3-11   An interactive high-level object-o
ii  python-central                0.5.5      register and build utility for Pyt

Versions of packages reportbug recommends:
pn  python-cjkcodecs | python-ico <none>     (no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to