You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Small suggestion, but perhaps you could have pxltrm ask users if they'd like to create images of their open terminal's size, or prompt for a height and width in pixels, and the terminal act as a viewport.
Said viewport could be scrolled the whole size of the "image" resolution, and pixels not be allowed to be placed past the resolution size. Essentially the idea is that pxltrm acts slightly more like an image editing software. Not entirely certain that I explained my suggestion in any meaningful way, so I can expand on some ideas if need be.
The text was updated successfully, but these errors were encountered:
This doesn't sound like such a bad idea given that even though I can full-screen my terminal in 1080p, that doesn't mean it will render correctly if someone else tries to open it with a maximized terminal. Differences in terminals and font sizes could be an issue. However, instead of pixels, you would use a column width. I think the standard is either 80 or 100 before wrapping to the next line. And if you're not in X and are using Debian/Ubuntu, you can set your TTY/console's column settings using 'sudo dpkg-reconfigure console-setup.'
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Small suggestion, but perhaps you could have pxltrm ask users if they'd like to create images of their open terminal's size, or prompt for a height and width in pixels, and the terminal act as a viewport.
Said viewport could be scrolled the whole size of the "image" resolution, and pixels not be allowed to be placed past the resolution size. Essentially the idea is that pxltrm acts slightly more like an image editing software. Not entirely certain that I explained my suggestion in any meaningful way, so I can expand on some ideas if need be.
The text was updated successfully, but these errors were encountered: