Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've checked the documention and FAQ at Fluxbox homepage, but nothing was mentioned how to enable the antialiasing option (Right Click on desktop and there should have a Antialias option, missing now).
Does enabling antialiasing support in fluxbox means that all other X applications will have antialiased fonts too? (eg Mozilla, firefox, etc)
The currentl stable release, 0.1.14, does not support antialiasing at all. You will have to get an unstable (development) release or check out the source from CVS in order to get the new bloat...err...features.
And no, enabling antialiasing for Fluxbox just means you enable it in the menu, in window decorations and so on. To enable antialiasing for GTK2/XFT apps like Firefox (if you got the GTK2/XFT-built version) you simply need to set the environment variable $GDK_USE_XFT=1.
How can I set environment variable $GDK_USE_XFT=1 such that the value will be retained in every user's shell and after every reboot.
Thanks !
Quote:
Originally posted by hw-tph The currentl stable release, 0.1.14, does not support antialiasing at all. You will have to get an unstable (development) release or check out the source from CVS in order to get the new bloat...err...features.
And no, enabling antialiasing for Fluxbox just means you enable it in the menu, in window decorations and so on. To enable antialiasing for GTK2/XFT apps like Firefox (if you got the GTK2/XFT-built version) you simply need to set the environment variable $GDK_USE_XFT=1.
in /etc/bash.bashrc since bash.bashrc(Debian) affects system-wide shells?
Thanks !
Quote:
Originally posted by hw-tph If you do not export the variable then it is only assigned to the current shell. With export the variable is set for all subsequent shells.
For the record, there's nothing even close to bloat in cvs fluxbox... Until our good friend explains that comment, assume fluxbox cvs is as lean as 0.1.14..
Originally posted by Sebboh For the record, there's nothing even close to bloat in cvs fluxbox... Until our good friend explains that comment, assume fluxbox cvs is as lean as 0.1.14..
The development direction of Fluxbox is quite focused at eye candy and to some extent usability. Compare a 0.1.14 installation with the latest CVS. Are you going to say pixmap themes, transparency and anti-aliasing doesn't detract from performance at all? It is *not* "as lean as 0.1.14".
Bloat may be a harsh word in this case, but still - the original Fluxbox releases were quite a lot snappier and responsive than recent versions.
Does that mean the variable has been created successfully? Not nit-picking, but just trying to understand abit more in depth
Thanks
PS. using bash
Quote:
Originally posted by mrcheeks davidas
if you create a variable without exporting it, it is like this variable doesn't exist at all.
trying
MYVARIABLE=X doesn't really create it but
MYVARIABLE=X
export MYVARIABLE
or export MYVARIABLE=X does the trick
i suppose you use bash or zsh , i don't , but i assume you do.
Yes, that does work for that shell alone. But if you start a new shell (type bash or xterm or whatever from the shell you're using) and type echo $MYVARIABLE again it will be empty, non-existing. But if you type export MYVARIABLE=123 it will exist in subsequent shells.
It is however worth noting that other shells already running do not inherit the exported variables. You will have to restart them (from the shell where the variable is set) in order for the variables to be set.
(without the export) in /etc/bash.bashrc work since bash.bashrc(Debian) affects system-wide shells?
Thanks !
Quote:
Originally posted by hw-tph Yes, that does work for that shell alone. But if you start a new shell (type bash or xterm or whatever from the shell you're using) and type echo $MYVARIABLE again it will be empty, non-existing. But if you type export MYVARIABLE=123 it will exist in subsequent shells.
It is however worth noting that other shells already running do not inherit the exported variables. You will have to restart them (from the shell where the variable is set) in order for the variables to be set.
Originally posted by hw-tph The development direction of Fluxbox is quite focused at eye candy and to some extent usability. Compare a 0.1.14 installation with the latest CVS. Are you going to say pixmap themes, transparency and anti-aliasing doesn't detract from performance at all? It is *not* "as lean as 0.1.14".
Bloat may be a harsh word in this case, but still - the original Fluxbox releases were quite a lot snappier and responsive than recent versions.
Håkan
I understand you're point... But as long as you can not use those features, and gain BACK the 'snappiness' I definately would say implying 'bloat' isn't appropriate..
Not like being arguementative at all, and I hope you don't take as such... But pixmap/transparency definately have SOME performance hit, running w/o them easily makes it run as smooth as before...
With the push to freedesktop.org compliance (hints etc), I would say what you mentioned is the ONLY non-necessary work that has been done... And that ain't bad! AND you can choose to not use it to gaim back that original performance!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.