Package: blackbox-terminal Version: 0.14.0-4 Severity: normal X-Debbugs-Cc: [email protected]
Dear Maintainer, I have run into several issues where nano is brought up even if my prefered editor is set to vim, I suspected the env var EDITOR had something to do with it as when I echoed it, it always reported nano. after configuring my .bashrc file to print the EDITOR variable as it was loaded, it reported it being vim the whole time, until I tested by echoing it myself, and it again reported back nano. testing with another terminal (gnome-terminal), it reports correctly that $EDITOR is correctly vim, spawning a new bash process after the one the terminal start also reports back vim. after uninstalling vim, programs calling the $EDITOR still try to launch nano (mutt, and reportbug). This is not critical, but I think it should be fixed whenever possible as this took me around an hour to figure out it was the terminal's fault, and not bashes or mine, it detracts from the user experience. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages blackbox-terminal depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4+b2 ii libadwaita-1-0 1.6.0-1 ii libc6 2.40-3 ii libcairo2 1.18.2-2 ii libgee-0.8-2 0.20.6-1+b1 ii libglib2.0-0t64 2.82.1-1 ii libgraphene-1.0-0 1.10.8-4 ii libgtk-4-1 4.16.3+ds-1 ii libjson-glib-1.0-0 1.10.0+ds-2 ii libpango-1.0-0 1.54.0+ds-2 ii libpqmarble2t64 1.3.0-6 ii librsvg2-2 2.59.1+dfsg-1 ii libvte-2.91-gtk4-0 0.78.0-1 ii libxml2 2.12.7+dfsg+really2.9.14-0.1 blackbox-terminal recommends no packages. blackbox-terminal suggests no packages. -- no debconf information
