public inbox for
 help / color / mirror / Atom feed
From: Brian Inglis <>
Subject: Re: Issue displaying characters on interactive commands
Date: Fri, 20 Apr 2018 12:42:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2018-04-20 05:24, Peter Dilov via cygwin wrote:
> If i run 'aptitude' command when i try to exit the command i get this strange
> exit window like in the screenshot:
> I also have noticed this problem with other interactive commands like 'ncdu'. I
> am using Cygwin on Windows 7 x64.

As these are character terminal windows, you could just have copied (using mouse
drag-select then primary [normally left] mouse button) and pasted the *relevant*
displayed characters into your email, instead of snapping a full screen shot
image of a remote server and linking to it: you are not alone in this, as many
articles and ebooks are illustrated with full screen shots showing a couple of
lines of a tiny font lost in a mass of dark screen background colour.

You fail to mention this is using ssh to another system, where your issue is
that you are seeing other characters interspersed with box drawing characters,
probably because your remote system is using UTF-8, and your local Cygwin system
is using a (localized or default) Windows encoding.

Please ensure that your LANG/LC_ALL charset encoding settings are the same on
both systems e.g. "export LANG=en_US.UTF-8" (check by running "locale" on both
systems to see these settings), and respected by the remote system and package
you are using, or change your local setting to match your remote setting.

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

Problem reports:
Unsubscribe info:

      parent reply	other threads:[~2018-04-20 12:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 11:24 Peter Dilov via cygwin
2018-04-20 12:14 ` Thomas Wolff
2018-04-20 12:42 ` Brian Inglis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).