Hi Meo
10x20 works perfect in aterm for me.
I disagree so this is the last time I attempt to convince you to re-consider your options.
please look at 2 screenshots, in the one link, taking on RPi just now I attempt to explain what you are seeing in case you can not read the font etc.
https://imgur.com/a/kbYGza7The top image shows aterm open with a CERTAIN font and size showing my currect screen scale or resolution of
1920x1080....for a monitor not a TV.
Top image shows I launch aterm with a command
aterm -fn 12x24 &
and that is the terminal on the right.
Compare the font sizes please....hehheh.
I stole the font and size from a TC forum post but it had slight change in syntax so here is the Xdefaults line
Aterm*font:*-*-fixed-medium-r-normal--*-280-*-*-*-*-iso8859-1
IMAGE2 below is a screenshot where live, I forced the largest menu scaling I could out of monitor hardware etc.
For me that is 720x400
Focus on the size of the menu.....and the RELATIVE size of the aterm font.
I agree....up close the font looks kind of ugly....a bit like me
But you will be looking from a long way and I think it might suit you.
Only if you agree.....I need your xrandr result please.
@Rich....or anyone interested on FLWM
Instead of using a file in .X.d ....for Meo's desktop I had to edit .xsession to include line before the
setbackground line. But as I did the rescaling LIVE I am not showing wbar etc
If Meo agrees to change her opinion, add a bootcode for waitusb for her usb kb dongle,
test various rescales.....I will then ask her to modify her .xsession file so it reads (replacing formula)
export WM_PID=$!
xrandr -s <wxh>
[ -x $HOME/.setbackground ] && $HOME/.setbackground
and if she has no persistent home....needs to add that file to her backup