When I view the length and width of my terminal emulator with stty size then it is 271 characters long and 71 lines tall. When I log into another server over SSH and execute stty size, then it is also 271 characters long and 71 lines tall. I can even log into some Cisco IOS device and terminal is still 271 characters long and 71 lines tall:
What are “scrollback” and “scrollback buffer” in programs like bash and screen, and how do they relate to the tty, the programs being run, and stdin/ stdout/ stderr?
I’m writing a script which shows the git log for a directory when I cd into it. Such a log can be overwhelming, containing hundreds of lines. So far I have been limiting that to a hard-coded 20 lines (... | head -n 20), which is fine on the screen at work, but too much on the smaller MacBook screen at home.
I would like to open a terminal, split it to lets say 9 parts (3×3) and execute some bash script. But for each terminal part different script.
I have a file with ANSI colors.
What is the file with the ~ at the end of the filename for? $ ls # aliased to add flags -rwxrwxr-x 1 durrantm 2741 May 16 09:28 strip_out_rspec_prep_cmds.sh~* drwxrwxr-x 13 durrantm 4096 May 16 14:21 ../ -rwxrwxr-x 1 durrantm 2221 May 16 14:58 strip_out_rspec_prep_cmds.sh* This is not the same as .swp files which are … Read more
I currently have the following line in my .zshrc:
I have tried using pipes and redirections to have (C program or scripts) output end up on the input buffer, the way printf "33[6n" does, but no positive results.
In people’s ‘.*rc‘ files I see online or in various code, I tend to see a lot of people who manually use ANSI escape sequences instead of using tput.
I have the following piece of code.