[SOLVED] Upgrading to Slackware Current breaks dir colours in terminal and vim scroll down

dalacor · 02-22-2019, 08:22 AM

I needed to upgrade to Slackware Current to address a problem caused by an older version of some of the Slackware software.

When I upgrade coreutils to the latest version in current from Slack 14.2 - I lose the colours in terminal view(folders, executables, files etc view) when I type dir. ls -a still shows the colours. Using the old or new config file seems to make no difference to showing the colours unless I am missing a config file.

Anyone have any idea how to fix this?

When I upgrade vim to the latest version in Current from Slack 14.2 - I can no longer scroll down in config files using vim. I can scroll up, but not down?

However, this is relevant to when I use putty and ssh to connect to the computer. If I am logging onto the actual computer using attached mouse and keyboard, I cannot scroll at all (in slack 14.2 or current) using vim in a config file. If anyone has any idea why scrolling does not work when I am physically logged onto the machine, but does work in remote putty mode, that would be great. I setup my mouse as usb mouse in slackware install setup.

As I very rarely need to logon to the actual machine, it's not something that I want to spend time on troubleshooting, but if its a quick fix.

In addition, I am happy to not upgrade coreutils and vim and just use the old version and upgrade everything else if its going to take a lot of time to find out why the new versions are broken in slackware current. I can wait till slackware 15 tbh.

Thank you

Paulo2 · 02-22-2019, 09:02 AM

I think 'dir' doesn't show any colours because of this in -current.

Code:

Wed Nov 29 08:15:09 UTC 2017
a/coreutils-8.28-x86_64-2.txz:  Rebuilt.
  Removed ancient (1992) aliases "dir, vdir, d, v" from the profile scripts.

I can scroll files in vim with ctrl+f and 'j' in -current, maybe you have some
configuration in .vimrc for the old vim version.

montagdude · 02-22-2019, 09:06 AM

It's not clear to me from your post. Did you upgrade the entire system to Slackware -current, or just a few packages?

dalacor · 02-22-2019, 10:28 AM

Quote:

Originally Posted by Paulo2

I think 'dir' doesn't show any colours because of this in -current.

Code:

Wed Nov 29 08:15:09 UTC 2017
a/coreutils-8.28-x86_64-2.txz:  Rebuilt.
  Removed ancient (1992) aliases "dir, vdir, d, v" from the profile scripts.

I can scroll files in vim with ctrl+f and 'j' in -current, maybe you have some
configuration in .vimrc for the old vim version.

I will have a look at the profile scripts for coreutils then. Thank you.

Sorry I should have been more clear - the MOUSE scroll button will scroll up in latest vim, but will not scroll down. I have not tried using the keyboard to scroll.

dalacor · 02-22-2019, 10:30 AM

Quote:

Originally Posted by montagdude

It's not clear to me from your post. Did you upgrade the entire system to Slackware -current, or just a few packages?

I have upgraded everything (including Kernels) to latest of the greatest. Everything works except coreutils and vim as described.

I think it's unwise to only upgrade some packages as this is more likely to break dependencies etc. So everything has been upgraded bar those two packages.

montagdude · 02-22-2019, 10:37 AM

Quote:

Originally Posted by dalacor

I have upgraded everything (including Kernels) to latest of the greatest. Everything works except coreutils and vim as described.

I think it's unwise to only upgrade some packages as this is more likely to break dependencies etc. So everything has been upgraded bar those two packages.

Okay, that's what I thought you meant. vim probably wouldn't even work at all if you just directly upgraded it in 14.2 using the binary package from -current.

dalacor · 02-22-2019, 10:59 AM

I have upgraded coreutils to the latest and inspected the coreutils-dircolors files in etc/profile.d and discovered the aliases there in the old version over new version. I now understand that dir is effectively an alias pointing to ls and it just makes sense get into the habit of using ls otherwise I will have this issue everytime I upgrade and using ls does exactly what dir does. I am just used to dir from windows.

So I just have to solve the mouse not scrolling down problem in putty, but also see if I can find out why mouse scroll does not work at all when logged onto the physical machine. Thanks

bassmadrigal · 02-22-2019, 12:03 PM

Quote:

Originally Posted by dalacor

I have upgraded coreutils to the latest and inspected the coreutils-dircolors files in etc/profile.d and discovered the aliases there in the old version over new version. I now understand that dir is effectively an alias pointing to ls and it just makes sense get into the habit of using ls otherwise I will have this issue everytime I upgrade and using ls does exactly what dir does. I am just used to dir from windows.

So I just have to solve the mouse not scrolling down problem in putty, but also see if I can find out why mouse scroll does not work at all when logged onto the physical machine. Thanks

When I first started using Linux, I had to set up an alias for cd.. to point to "cd .." because of dos habits as well. Eventually, I determined it was just much easier to force myself to learn the linux equivalent commands so I didn't have to worry about aliases being set up or running into issues when using someone else's system.

dalacor · 02-23-2019, 02:50 PM

Quote:

Originally Posted by bassmadrigal

When I first started using Linux, I had to set up an alias for cd.. to point to "cd .." because of dos habits as well. Eventually, I determined it was just much easier to force myself to learn the linux equivalent commands so I didn't have to worry about aliases being set up or running into issues when using someone else's system.

Yes I agree, which is why I will stop using dir and move to ls. In my defence I did not realise until now that dir was not actually a Linux command as it has worked for years!

After much hunting around, I have found no solution to the vim mouse scroll down problem in latest vim version and can't find any posts, google or otherwise regarding mouse scroll when logged onto actual machine. So I will leave the question open, but I am not worried as I will just wait till Slackware 15 and see if mouse scrolling issues are resolved then.

kjhambrick · 02-23-2019, 03:37 PM

Quote:

Originally Posted by dalacor

I have upgraded coreutils to the latest and inspected the coreutils-dircolors files in etc/profile.d and discovered the aliases there in the old version over new version. I now understand that dir is effectively an alias pointing to ls and it just makes sense get into the habit of using ls otherwise I will have this issue everytime I upgrade and using ls does exactly what dir does. I am just used to dir from windows.

So I just have to solve the mouse not scrolling down problem in putty, but also see if I can find out why mouse scroll does not work at all when logged onto the physical machine. Thanks

dalacor --

I can't provide a solution but one place to start ...

Which Putty TERM are you using ?

The two relevant Putty Settings Screens are [Terminal]->[Keyboard] and [Connection]->[Data]

See the Attachments ...

The Terminal Types have to match exactly or FunKeys won't work in our Legacy App ...

HTH

-- kjh

dalacor · 02-23-2019, 04:40 PM

Unless I am misunderstanding you, the issue is not the keyboard. The issue is the mouse unless changing the keyboard settings affects the mouse when upgrading vim etc?

For the moment I am going to have to leave the mouse issues as I have to get started on setting up the filtering system which was the whole reason I upgraded Slackware to current. So I will come back to the mouse scroll issue in a couple of weeks as I need vim a lot in the next couple of weeks.

I use putty on windows. But I have not changed any settings in putty and never had problems with slackware 14.2 - problems only started with current. But interesting knowing about the settings for keyboard there. My keyboard is set at default - Esc, not linux. But it's been like that for the last 5 years!

kjhambrick · 02-24-2019, 04:02 AM

dalacor --

1. Some Terminals don't support a Mouse ( VT100, SCO, WYSE60 ) so I was wondering if maybe the new vim 'fixed' something for you by ignoring mouse events for Terminals without mice

2. The Putty Connection Data Field MAY ( should ) affect the TERM environment Variable for your Linux Login Session ( it does set TERM for SSH Sessions ).

You can check it on the Linux side: echo $TERM

We've had issues for years where Users set up mismatched Keyboard -and- Putty Connection Data Settings -- Function Keys may not work with some combinations.

Like I said ... I don't have a solution, just a place to start looking ...

-- kjh

dalacor · 02-24-2019, 10:32 AM

It's a relevant point. I will investigate this when I get back to playing with vim. I am working on e2guardian at the moment. Thanks

dalacor · 02-21-2020, 11:38 AM

I am closing this question because I am now using ls command which works perfectly. As for the mouse scroll up down issue - this seems to have been resolved after another round of Slackware updates. Presumably there was some issue with the Vim version that I upgraded to last year which has now been resolved in the latest vim release?

However, this only works for putty sessions. Logging on to the actual machine - the mouse scroll still does not work. However this is not an issue as I never logon to the actual physical machine.

Thanks for the help on this question.

garpu · 02-21-2020, 12:10 PM

Vim and gvim are working fine for me and also with correct syntax highlighting. Do you have some old config somewhere that's corrupting things?