[plug] ls in colour & terminal size

David White tadewhite at optusnet.com.au
Thu Jun 27 16:48:34 WST 2002


I should proberly have explained the terminal part better. I want my tty 
terminal bigger.
At 20:40 26/06/2002 +0800, you wrote:
>>Details are in 'man X'
>or you can be lazy with most window managers and set them up to remember 
>your usual terminal size.
>
>If that's not an option, most apps accept an arg like "-geometry 120x60" 
>(for a 120x60 col term) though syntax may vary app2app like
>         --geometry=COLSxROWS
>         -g COLSxROWS
>         -geometry=COLSxROWS
>         --geometry COLSxROWS
>et etc, see app's -help/-h/--help/-help (*sigh*) for details and/or "man app"
>
>As for framebuffer, VESAfb is easy to set up but many (most?) cards have 
>buggy VESA support (because windows doesn't have VESA drivers you see 
>*sigh* only VGA and vendor) so you may or may not find it OK, and it can 
>sometimes confuse or be confused by an Xserver. Of course some of the 
>vendor-specific fb modules are worse.
>
>If you use a custom kernel, just compile in the appropriate fb options 
>under the console config, and for vesafb read the docs in 
>kernelsrc/Documentation/fb/vesafb.txt for setup info, it isn't hard.
>
>With frame buffer support your virtual consoles can be run at acceptable 
>resolutions too. Especially important if you have a 19" monitor (mine 
>draws 640x480 console with each row of pixels separated by 1/2mm or so - 
>very annoying).
>
>--
>Craig Ringer
>GPG Key Fingerprint: AF1C ABFE 7E64 E9C8 FC27  C16E D3CE CDC0 0E93 380D
>         -- if it ain't broke, add features 'till it is. (or:)
>         while (! broken) { feature ++ ; }
>



More information about the plug mailing list