SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hello, thanks for the answer, the sh-option seems to work, but when I use
xterm -sh 2
I get double linespace and values of 1.1 or 1.2 up to 1.9 make no difference.
hmm - if I can reproduce this, I can investigate. At the moment I'm not seeing this (with
Debian 6.0). On that, fc-list says I have "DejaVu Sans Mono:Bold Oblique". Running xterm
with/without the space makes no difference (underlines always show up).
I don't think there is one source of information for this stuff. It's all rather messy and certain bits have evolved or been obsoleted over time. Best just to google for 'X' and 'fonts' and start there.
The desktop environments such as kde/xfce have their own hinting settings which can have a major effect. if you're using one of those desktops then perhaps try playing with the settings. You may also want to try using a minimal window-manager based desktop (which is what I use) which won't interfere with the font rendering.
Other than that, the only other thing I can think of that might cause your underscore to go missing would be if your X display is not running at the native resolution of your screen (assuming lcd panel).
Other than the above, I can't think of any other suggestions.
Last edited by GazL; 10-30-2012 at 09:47 AM.
Very odd that we get different results. I've tried xterm with font sizes from tiny->huge and they all display just fine (though when I use xmag it does look like the underscore is only a single pixel high when rendered so it would be susceptible to obliteration by any errant rendering.
Just out of interest. If you run xmag -mag 16 and select the area where the missing underscore is, do you see it in the magnification
Not so odd, considering that a lot of the hinting configuration is installed automatically (and not consistently from one platform to another). Given a specific version and configuration, it's (usually...) possible to isolate the problem.
Don't know whether you got anywhere with this Markus, but I just thought you'd be interested to know that when I just tried the latest nouveau and libdrm version from git on my system, my underscores disappeared too, so you're not alone in this. I swapped back to using the nvidia blob.