How to enable antialias support in Fluxbox 0.1.14
 

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)

Any help on this, please?

Thanks !

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.


Håkan

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 !

You can add this line to /etc/profile:/etc/profile is used to set global environment variables, etc.


Håkan

What is the difference between and just Thanks!

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.


Håkan

Is putting in the /etc/profile equivalent to putting in /etc/bash.bashrc since bash.bashrc(Debian) affects system-wide shells?

Thanks !

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..

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.

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 assigned a value of 123 to MYVARIABLE and echo its value...this is what I get:

david@xdavid:~$ MYVARIABLE=123
david@xdavid:~$ echo $MYVARIABLE
123

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

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.


Håkan

For it to work in all new shells, would this code

(without the export) in /etc/bash.bashrc work since bash.bashrc(Debian) affects system-wide shells?

Thanks !

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!