-
Notifications
You must be signed in to change notification settings - Fork 331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong number of column #718
Comments
I believe the relevant change in your system is the latest |
@gokcehan I'm still experiencing this issue, can you reproduce the fact that |
@BachoSeven Sorry I thought your previous response was a solution. I didn't read it carefully. I can reproduce this on my machine as well. I'm marking this as a bug. An easy workaround is to use
It might also be possible to export a variable with the number of columns before launching |
@gokcehan Thanks very much for the workaround; will update the wiki example for now since it might be an issue or change of behaviour with If I got your final comment correctly, what you're saying is that since we don't use the async
|
Currently, the example fails confusingly for newer versions of `tput`. See gokcehan#718.
…fix) (#975) * When clicking on file preview, only open files on right-click Currently, when mouse is on, I often click on the preview accidentally since it's such a large target. Moreover, there is very little space I can click without having the `lf` state change drastically (since I must click on the current file for the preview to stay the same). This commit prevents that. * (Minor): Change example in docs to work around a bug Currently, the example fails confusingly for newer versions of `tput`. See #718.
I have now added
Closing this issue now. Feel free to report if there's an issue. |
problem
I use this setting to set ratio of lf automatically.
But after upgrading my system yesterday, the column always be 80.
The command I type in lf
%tput cols
always get 80. No matter how I resize my terminal.System version
OS: 5.15.2-arch1-1
bash: 5.1.8
The text was updated successfully, but these errors were encountered: