seeseemelk/cool-retro-term
1
0
Fork 0
Code Issues 449 Pull Requests 12 Actions Packages Projects Releases 8 Wiki Activity

Auto scroll not working #301

New Issue
Open
opened 2016-07-06 22:12:17 +02:00 by ppamorim · 12 comments
ppamorim commented 2016-07-06 22:12:17 +02:00 (Migrated from github.com)
Copy Link

Hello.
The auto scroll of this terminal is not working, I installed the last version and build the source. I'm using the OSX 10.11.5 on a Macbook Pro Retina.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/35805001-auto-scroll-not-working?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github).
Hello. The auto scroll of this terminal is not working, I installed the last version and build the source. I'm using the OSX 10.11.5 on a Macbook Pro Retina. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/35805001-auto-scroll-not-working?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github). </bountysource-plugin>
👍 3
Skater101b commented 2016-07-14 23:40:43 +02:00 (Migrated from github.com)
Copy Link

I have the same problem. When I cat out info, I can not scroll up in the terminal. I can scroll up through commands, but having the ability to scroll up in the terminal is kind of a deal breaker for me. Which would be a bummer since this is a super cool terminal. I believe we are talking about the same thing.

I have the same problem. When I cat out info, I can not scroll up in the terminal. I can scroll up through commands, but having the ability to scroll up in the terminal is kind of a deal breaker for me. Which would be a bummer since this is a super cool terminal. I believe we are talking about the same thing.
Skater101b commented 2016-07-15 15:28:43 +02:00 (Migrated from github.com)
Copy Link

I started it today and the scrolling works like it should, perhaps it was related to a preference I had set, but now ctrl+C doesn't work to interrupt a command.

I started it today and the scrolling works like it should, perhaps it was related to a preference I had set, but now ctrl+C doesn't work to interrupt a command.
otherjoel commented 2016-07-26 19:39:00 +02:00 (Migrated from github.com)
Copy Link

If I do ls -l in a folder with lots of files, the terminal does not auto-scroll to the bottom of the listing; instead the listing continues right past the bottom of the screen. The command prompt is also off-screen at this point. You can't use your mouse to scroll down to see it either; in fact the only way to see your command prompt again is to type clear and hit Enter.

Further testing: if I do this in fullscreen mode on a 13″ Retina MacBook Pro:

clear; for i in {1..50}; do echo $i; done;

Then I see numbers 1–40 on the screen and the command prompt is invisible. I have to hit Enter 28 times before the display will scroll at all (it starts scrolling on the 29th keystroke), which to me says that the terminal thinks it has 68 rows to work with instead of only 40.

I believe this is the same auto-scrolling problem @ppamorim is describing. (@Skater101b seems to be talking about manually scrolling up in the terminal history, which is a different thing.)

If I do `ls -l` in a folder with lots of files, the terminal does not auto-scroll to the bottom of the listing; instead the listing continues right past the bottom of the screen. The command prompt is also off-screen at this point. You can't use your mouse to scroll down to see it either; in fact the only way to see your command prompt again is to type `clear` and hit Enter. Further testing: if I do this in fullscreen mode on a 13″ Retina MacBook Pro: ``` clear; for i in {1..50}; do echo $i; done; ``` Then I see numbers 1–40 on the screen and the command prompt is invisible. I have to hit Enter 28 times before the display will scroll at all (it starts scrolling on the 29th keystroke), which to me says that the terminal thinks it has 68 rows to work with instead of only 40. I believe this is the same auto-scrolling problem @ppamorim is describing. (@Skater101b seems to be talking about manually scrolling up in the terminal history, which is a different thing.)
Integralist commented 2016-08-24 18:32:57 +02:00 (Migrated from github.com)
Copy Link

Yeah so similar issue for me, whether it be ls -la or opening Vim and not being able to see the Ex bar at the bottom of the screen

Yeah so similar issue for me, whether it be `ls -la` or opening Vim and not being able to see the Ex bar at the bottom of the screen
mattstvartak commented 2016-09-06 20:05:56 +02:00 (Migrated from github.com)
Copy Link

Also having this problem. Typed "testing" and hit enter and it didn't appear for another 35 lines.

Also having this problem. Typed "testing" and hit enter and it didn't appear for another 35 lines.
davehouse commented 2016-09-27 22:36:17 +02:00 (Migrated from github.com)
Copy Link

I see this problem also on a macbookpro with retina screen. It looks like the column by row counts are scaled 2x of what is actually visible. Maybe the retina pixel density is affecting a size measurement but being applied twice.

I see this problem also on a macbookpro with retina screen. It looks like the column by row counts are scaled 2x of what is actually visible. Maybe the retina pixel density is affecting a size measurement but being applied twice.
izznogooood commented 2016-11-20 00:16:30 +01:00 (Migrated from github.com)
Copy Link

Same problem, osx.

Same problem, osx.
angelo commented 2016-12-01 16:54:23 +01:00 (Migrated from github.com)
Copy Link

Same issue here, OSX 10.10.5, 27" iMac. I've tried various screen scalings, doesn't have any impact on the issue.

Same issue here, OSX 10.10.5, 27" iMac. I've tried various screen scalings, doesn't have any impact on the issue.
davehouse commented 2016-12-01 18:37:18 +01:00 (Migrated from github.com)
Copy Link

The problem is fixed by turning off retina scaling (Set display to "Scaled" > "More Space" to scale the ui to actual/1x pixels in OSX). So it looks like a problem with the retina/hidpi scaling in the code.

The problem is fixed by turning off retina scaling (Set display to "Scaled" > "More Space" to scale the ui to actual/1x pixels in OSX). So it looks like a problem with the retina/hidpi scaling in the code.
singlerider commented 2016-12-21 20:56:09 +01:00 (Migrated from github.com)
Copy Link

The problem still persists for me on 15 inch Macbook Pro, even after adjusting scaling.

The problem still persists for me on 15 inch Macbook Pro, even after adjusting scaling.
davehouse commented 2017-01-27 21:53:24 +01:00 (Migrated from github.com)
Copy Link

This fixed the scaling problem for me to keep the terminal content in the crt display area (cols, lines being actual crt display area), https://bugreports.qt.io/browse/QTBUG-48972.

Setting the environment variable QT_SCALE_FACTOR=0.5 to un-scale from my 2x/retina setting in OSX:

$ QT_SCALE_FACTOR=0.5 cool-retro-term.app/Contents/MacOS/cool-retro-term

image
image

This fixed the scaling problem for me to keep the terminal content in the crt display area (cols, lines being actual crt display area), https://bugreports.qt.io/browse/QTBUG-48972. Setting the environment variable QT_SCALE_FACTOR=0.5 to un-scale from my 2x/retina setting in OSX: ``` $ QT_SCALE_FACTOR=0.5 cool-retro-term.app/Contents/MacOS/cool-retro-term ``` ![image](https://cloud.githubusercontent.com/assets/5540936/22387178/a2da5474-e497-11e6-806d-9fb903053263.png) ![image](https://cloud.githubusercontent.com/assets/5540936/22387226/cf23b778-e497-11e6-992c-e11a4e187321.png)
👍 1
hery84 commented 2017-10-30 02:59:31 +01:00 (Migrated from github.com)
Copy Link

QT_SCALE_FACTOR=0.5 open cool-retro-term.app

QT_SCALE_FACTOR=0.5 open cool-retro-term.app
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bounty
bug
duplicate
enhancement
help wanted
invalid
priority
high
priority
low
question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
seeseemelk
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#301
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?