You are not logged in.
The default terminal about broke my eyes the first time I started it up, mainly due to the small font. Since I -like- using xterm, I wanted to fix things.
First, I needed a readable font. With the mouse pointer in the window, press Ctrl-right-click and hold the click to get a menu that includes different font sizes. Selecting 'Medium' or 'Large' produces a more readable font size--though with Large you'll need to slide the taskbar off to the right to see the bottom of the window. Release the mouse button when the pointer is over the menu item you want to select.
Next was to set the defaults for this application under X-Windows so that I could have it be decent-looking every time I fired it up. The X server on the default Xandros looks for a file called .Xresources in the user's home directory when X-Windows starts up a session and merges it with the system's X-Windows settings. So I could put all my customizations into a this file and have them across reboots and restarts of the application.
The X-Windows options specific to xterm are documented in the xterm manpage, but not in a way that makes sense to the uninitiated, unfortunately. The X-Window User HOWTO gives a good introduction to using X resources to configure how your applications look and behave at:
http://tldp.org/HOWTO/XWindow-User-HOWT … onfig.html
In my case, I wanted mostly to set the font, but I also wanted some window history (for times like when 'ls' overflows the window and I don't feel like looking at things a page at a time by piping it into less) and a scrollbar to move through that history.
Here's what I put in my .Xresources file (in my home directory,
xterm*Font: -adobe-*-medium-r-*-*-*-*-*-*-m-90-*-*
xterm*foreground: LawnGreen
xterm*background: black
xterm*cursorColor: PaleGoldenrod
xterm*scrollBar: true
xterm*saveLines: 500
xterm*rightScrollBar: true
xterm*scrollbar.Background: SlateGray
xterm*scrollbar.Foreground: CadetBlue1
xterm*scrollbar.thickness: 6
Now, that font line looks like a mess to type, but I have to admit I cheated. There's a program called xfontsel that lets you look at fonts and pick the one you want, and it gives you the proper string for it. To give it a whirl, go to your terminal and type:
xfontsel &
You'll get a very crude GUI app that lets you select different properties of a font in very techie terms, and see what the prospective font looks like. It's not a super-friendly app, but it does the job. One quirk is that if you've selected options that put you in a corner on fonts, in order to get previously available options to re-appear you need to select the * on that particular drop-down list, release the mouse to let the menu close, then re-open it to see the options available again. Un-selecting options by shifting each item back to a * progressively opens your options back up again.
Now, you don't need to select every item about your font. You can leave some or most of the items as a *. Also, the font displayed will change as you change the different item selections. If you're getting a non-Latin character set, you can see if there's a Latin character set by selecting an encoding option (the last item) like setting it to 1 and seeing if a Latin font appears.
Once you've found a font that'll do, click on the Select button. This will put the font selection string into your mouse's cut-and-paste buffer. Go to where you're editing your .Xresources file and press the middle mouse button to put the string into the current insertion point (press both mouse buttons simultaneously if you're using a two-button mouse--it may take a couple of tries to get the timing right. If it doesn't paste properly, see if Select is still highlighted in the xfontsel window. If not, something else got put into the mouse buffer by accident. Click Select and try again.) If the mouse buffer doesn't work for you, run xfontsel like this:
xfontsel -print
Then, once you have your font, click the Quit button in xfontsel. It'll quit, and print out the font string for you in the terminal window. If you want it to write it to a file instead, you can do something like:
xfontsel -print >>fontsIlike.txt
to have it print the font selected when you press the quit button to a file, where it will append another font name each time you run xfontsel this way.
Now you may wonder where I'm getting color names like "LawnGreen" and "CadetBlue1". They're in a text file:
/usr/share/X11/rgb.txt
Take a look at it and pick your own colors. Put them into your .Xresources file. To see changes you've made to the file since X has started up, you need to get X to 'read them in' using the following command:
xrdb -merge .Xresources
Then you can start up a new xterm and see how it looks:
xterm
If you want to open it up and still be able to type in your original xterm window while it's open, use:
xterm &
The '&' tells the shell to start your command in a new process, then return to the prompt. If you want the other window to hang around after you've closed the first xterm window, use:
nohup xterm &
nohup means "no hang-up" meaning that when the parent process (your original xterm window) terminates, it doesn't send a hang-up signal to the new process, which would command it to quit along with the parent. Nohup lets it keep running even when the parent dies.
You can define how you want other X-Windows applications to look using this same file. You can also define mouse and keyboard behaviors. For some examples of what you can do, take a look at the files in /etc/X11/app-defaults.
Enjoy!
Offline
Why not switch to the much nicer and already installed KDE Konsole?
Offline
Yes, or you will be back to square one after a reset ![]()
However, it is good to know that you can turn around with the Xresources
Last edited by o2smartphone (2007-12-14 6:28:20 am)
Offline
Actually, the .Xresources file gets merged at the start of each X session, so the changes in it are permanent. I'm not back to square one after a reset, that's the whole point. You need to do the xrdb update while you're tinkering to see the effects of your changes immediately without restarting X, so you can try out one font or another or different color combinations on the fly.
Personally, I don't care for Konsole as much as xterm. My biggest hangup was determining what filename this version of X uses for local resources (.Xresources rather than .Xdefaults), and whether I'd have to change a setting to make X merge those resources automatically (answer: no, the default as installed on the Eee is to merge user settings.) The biggest hindrance here was finding out where they'd hidden the manpage for X so that I could find all that out (it's under Xsession, with further pages referred to there.)
I spent more time playing with xfontsel than anything else. ![]()
Also, part of the idea here is to let folks know they can use the same process to control a lot more than just xterm. xterm makes a good case in point, particularly as it is what's immediately available to a new user.
Last edited by saundby (2007-12-14 11:37:07 pm)
Offline
A before/after screenshot might be good for this thread, as it's a "visual thing".....?
Offline
saundby
Many thanks for taking the time and trouble to share this info, very detailed and informative, I will look into playing with this!
Offline
Doesnt Konsole use up more system resource? I believe I read that somewhere on here.
Offline
saundby wrote:
Actually, the .Xresources file gets merged at the start of each X session, so the changes in it are permanent. I'm not back to square one after a reset, that's the whole point. You need to do the xrdb update while you're tinkering to see the effects of your changes immediately without restarting X, so you can try out one font or another or different color combinations on the fly.
Personally, I don't care for Konsole as much as xterm. My biggest hangup was determining what filename this version of X uses for local resources (.Xresources rather than .Xdefaults), and whether I'd have to change a setting to make X merge those resources automatically (answer: no, the default as installed on the Eee is to merge user settings.) The biggest hindrance here was finding out where they'd hidden the manpage for X so that I could find all that out (it's under Xsession, with further pages referred to there.)
I spent more time playing with xfontsel than anything else.
Also, part of the idea here is to let folks know they can use the same process to control a lot more than just xterm. xterm makes a good case in point, particularly as it is what's immediately available to a new user.
What I meant is a F9 or USB reset and not a simple reboot ![]()
Offline
o2smartphone wrote:
What I meant is a F9 or USB reset and not a simple reboot
Ah! Well, that's what backups are for, right? Besides, once you know how it's easy to do over again. The explanation I give takes longer to read than it takes to do (unless you play with xfontsel for too long.) ![]()
Starting out with an eye-wateringly small font is a xterm flaw, not specific to the Eee, BTW. It has to do with how xterm picks a font if one isn't specified for it. This could have been fixed with a simple edit to the standard resource files distributed with X over 15 years ago and any time in between, but no, here we are still opening up xterm for the first time to see miniscule print.
Last edited by saundby (2007-12-15 7:04:35 am)
Offline
As requested, a screenshot.
The small terminal window that is mostly covered is the default settings, the larger one in the foreground shows the results of the short .Xresources file.
The text is larger and easier to read on the Eee's LCD,
it's green, my preferred color,
there's a scrollbar, on the right where I like it
with some colors to make it look a bit nicer than the default
it's a bit narrower than the default in order to make it take up a bit less screen space
(and allow an even larger font without running offscreen if I choose to change to it.)
Offline
Another screencap--an alternate setup I use. Larger sans-serif font, amber color text:
Offline
Thanks, saundby, I'm reconfiguring my eeepC to give to a relative, so this guide was very useful!
Offline
There's a tutorial (with screenshots of the different available terminals) on eeepc logiciel, which explains you how to change your default terminal and to choose one of the 5 that are installed by default in Xandros: http://www.eeepc-logiciels.com/2008/04/ … ar-defaut/
All you have to do is to open a terminal (Ctrl+Alt+T) and type the following:
sudo update-alternatives –config x-terminal-emulator
You will be given 6 choices: konsole, xterm, uxterm, koi8rxterm, lxterm and default.
Type the choosen number, then enter, and there it is.
Last edited by oupsemma (2009-02-23 11:38:42 pm)
Offline
Wow, I never knew that! How interesting! It's good to see there are at least some geeks who know what they're doing on these forums. And I learn something new about these netbooks every day.
[edit: I see that this information is indeed in the eeePC wiki!]
Last edited by RubyTuesday (2009-02-25 4:02:08 pm)
Offline