[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#981511: marked as done (reportbug: Probably wrong terminal type)

Your message dated Tue, 2 Feb 2021 22:58:29 +0100
with message-id <130394ce-27c6-c9c1-f5a2-1ef367c589a9@mailbox.org>
and subject line Re: Bug#981511: reportbug: Probably wrong terminal type
has caused the Debian Bug report #981511,
regarding reportbug: Probably wrong terminal type
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
981511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981511
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: reportbug
Version: 7.9.0
Severity: important
X-Debbugs-Cc: dv@vollmann.ch

Dear Maintainer,

   * What led up to the situation?
My EDITOR is set to 'vi', but when launching the editor from inside
reportbug, it doesn't correctly clear lines on scrolling, so that
any text from a previous longer line is still visible.
This makes editing nearly impossible.
Unlike I wrote in the subject, the terminal type seems still to
be correct (at least when I start a shell from inside the editor
it shows the correct value 'xterm').

Actually I just found that after returning from the shell,
vi behaves fine, just the original vi invocation is wrong.
With this workaround it might just be 'minor'.

-- Package-specific info:
** Environment settings:
EDITOR="vi"
PAGER="less"
VISUAL="vi"
INTERFACE="text"

** /home/dv/.reportbugrc:
reportbug_version "7.9.0"
mode standard
ui text
email "dv@vollmann.ch"
no-cc
list-cc-me
smtphost reportbug.debian.org

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt                2.1.18
ii  python3            3.9.1-1
ii  python3-reportbug  7.9.0
ii  sensible-utils     0.0.14

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                                            <none>
pn  debconf-utils                                         <none>
pn  debsums                                               <none>
pn  default-mta | postfix | exim4 | mail-transport-agent  <none>
pn  dlocate                                               <none>
ii  emacs-bin-common                                      1:27.1+1-3
ii  file                                                  1:5.39-3
ii  gnupg                                                 2.2.20-1
pn  python3-urwid                                         <none>
pn  reportbug-gtk                                         <none>
ii  xdg-utils                                             1.1.3-4

Versions of packages python3-reportbug depends on:
ii  apt                2.1.18
ii  file               1:5.39-3
ii  python3            3.9.1-1
ii  python3-apt        2.1.7
ii  python3-debian     0.1.39
ii  python3-debianbts  3.1.0
ii  python3-requests   2.25.1+dfsg-2
ii  sensible-utils     0.0.14

python3-reportbug suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On 01.02.2021 00.30, Detlef Vollmann wrote:
>>> My EDITOR is set to 'vi', but when launching the editor from inside
>>> reportbug, it doesn't correctly clear lines on scrolling, so that
>>> any text from a previous longer line is still visible.
>>> This makes editing nearly impossible.

> If I use vi directly, or started by any other program (e.g.
> 'git commit'), I never have this problem.

A web search on this issue finds so many instances that I'm not
convinced this could be a bug in reportbug. E.g.:
https://stackoverflow.com/questions/46919687/vi-display-messed-up-in-remote-servers-using-xquartz
https://vi.stackexchange.com/questions/15424/vim-display-wont-refresh
https://invisible-island.net/xterm/xterm.faq.html#xterm_tite

It seems to depend on using specific combinations of terminals and
locale settings. Sorry for closing this bug too, but again I don't think
there is anything reportbug can do about it.

--- End Message ---
Reply to: