On Sun, 27 Oct 2019 08:25:28 -0700
Kenneth Porter wrote:
> It's a missing ncurses feature in the older PuTTY that's trigged by
> an update to ncurses or terminfo in CentOS 8. PuTTY 0.72 added
> support for the REP (repeating character) command and the newer
> terminfo adds that as an xterm featur
It's a missing ncurses feature in the older PuTTY that's trigged by an
update to ncurses or terminfo in CentOS 8. PuTTY 0.72 added support for the
REP (repeating character) command and the newer terminfo adds that as an
xterm feature. The Epsilon author spotted it in the PuTTY changelog.
So an
It's a display bug in PuTTY+Epsilon, but a subtle one! I upgraded PuTTY
from 0.65 on one PC to 0.73 (latest) and the problem disappeared. I still
see it on another PC running PuTTY 0.70.
I'm still trying to characterize it but the output is correct and it's
because I'm using Epsilon to view th
It's not a ls bug. I've stepped through the code with gdb and it looks just
fine. At this point I think Epsilon (a 32-bit app) is corrupting the image
of its child process in a strange way. I'm working with the author at
Lugaru (who's very responsive) to track it down. He couldn't reproduce it
On Fri, 25 Oct 2019 at 20:14, Kenneth Porter wrote:
>
> Found it. It happens from the process buffer inside Lugaru Epsilon. I think
> ls thinks it's doing a DIRED output instead of a shell output. Now I need
> to figure out why it thinks that. This wasn't happening in CentOS 7.
>
Lugaru Epsilon?
--On Friday, October 25, 2019 6:39 PM -0700 Kenneth Porter
wrote:
I may have to pull the coreutils-8.30-6.el8.x86_64 sources to see how ls
makes these decisions.
I pulled the coreutils SRPM and it won't build because it wants texinfo and
dnf says it doesn't exist, using either the builddep
--On Friday, October 25, 2019 6:13 PM -0700 Kenneth Porter
wrote:
Found it. It happens from the process buffer inside Lugaru Epsilon. I
think ls thinks it's doing a DIRED output instead of a shell output. Now
I need to figure out why it thinks that. This wasn't happening in CentOS
7.
I'm puz
Found it. It happens from the process buffer inside Lugaru Epsilon. I think
ls thinks it's doing a DIRED output instead of a shell output. Now I need
to figure out why it thinks that. This wasn't happening in CentOS 7.
___
CentOS mailing list
CentOS@c
--On Saturday, October 26, 2019 1:07 AM +0200 Alexander Dalloz
wrote:
Not sure what you were doing.
An example:
[root@rocinante ~]# ls -al
total 76
dr-xr-x---. 8 root root 4096 Oct 25 14:37 .
dr-xr-xr-x. 18 root root 4096 Oct 21 09:36 ..
-rw-. 1 root root 1481 Oct 24 10:35 .bash_history
-
Am 25.10.2019 um 23:44 schrieb Kenneth Porter:
When I use "ls -al" on a directory, for files with only owner read/write
permission, the displayed attributes are "-rw-", not "-rw---". That
means the file names don't line up with other files in the directory,
which makes the listing harder to
When I use "ls -al" on a directory, for files with only owner read/write
permission, the displayed attributes are "-rw-", not "-rw---". That
means the file names don't line up with other files in the directory, which
makes the listing harder to read. What changed where and how do I fix that?
11 matches
Mail list logo
