Date: Sat, 6 Jan 2024 08:06:41 +0100 (CET) From: freebsd@oldach.net (Helge Oldach) To: pmc@citylink.dinoex.sub.org (Peter) Cc: freebsd-stable@freebsd.org, bapt@freebsd.org, alfix86@gmail.com, asiciliano@freebsd.org Subject: Re: ports-mgmt/portconfig surprize Message-ID: <202401060706.40676fN6057546@nuc.oldach.net> In-Reply-To: <ZZdAz2EM2htYzfX9@disp.intra.daemon.contact> from Peter at "5 Jan 2024 00:35:43"
next in thread | previous in thread | raw e-mail | index | archive | help
Peter wrote on Fri, 05 Jan 2024 00:35:43 +0100 (CET): > Folks, > > somebody got the idea to replace the dialog4ports options > configuring interface by something named 'ports-mgmt/portconfig'. > (And they did not even find it worth mentioning this in the > UPGRADING file.) > > Now this one looks terrible, the screen is garbled, and it is > quite unintellegible which line is currently entered. > See pictures here (old and new): > https://forums.freebsd.org/threads/2024q1-portbuild-trouble.91770/post-636816 > > What is happening: > I am starting a shell script. That fires up a bhyve. In the bhyve 'make' > is run with stdio connected to the second COM. > In the script on the host, bhyve is put in background, 'cu' is started > and connected to that second COM. There the dialog appears. > Since the script on the host is run from remote, it is run within > tmux. > Point is: it did work before. I suspect that this has to do with the fact that Mk/Scripts/dialog4ports.sh *enforces* the C.UTF-8 locale even if the terminal doesn't support it well, or not at all. (Note that also your first screenshot shows artifacts left to the '[' character.) That is PR 275364? Kind regards Helge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202401060706.40676fN6057546>