GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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.
For me, an editor without syntax highlighting seems pretty lame.
Seeing as how I don't do much programming anymore (I can't even figure out how to properly manage arrays in C [e.g. with memset(), memcpy(), etc.] ), it's fine for me. If I need something with syntax highlighting, I use Geany.
Much improved ... but like stated earlier, how can you read things with this kind of complete transparent windows ? Can you ?
Yes, but you're right: It does cause text in the windows to become obfuscated in a way.
However, I would have tried to make just the border transparent -- if the current GTK+ RGBA module allowed such fine-grained customization. I also would have been able to control just how transparent the window border was -- but again: A Boolean ( e.g. rgba = TRUE) instead of a float is a bad way to control an alpha channel, that's for sure!
Yes, but you're right: It does cause text in the windows to become obfuscated in a way.
However, I would have tried to make just the border transparent -- if the current GTK+ RGBA module allowed such fine-grained customization. I also would have been able to control just how transparent the window border was -- but again: A Boolean ( e.g. rgba = TRUE) instead of a float is a bad way to control an alpha channel, that's for sure!
Compiz w/Emerald as the theme manager will let you control the transparency of your window borders.
Notice pacman running in the terminal window in that screenshot? That's because that terminal is chrooted into an external hard drive. Why? In this case, to install GNOME. Now, I am updating the packages on the chrooted environment of the system. I decided to use a chroot as a way of working around my wireless network adapter issues.
I was able to install the base system on the external drive by 'unsquashfs'-ing the root image (on the Core CD, as well as the local repository squashfs file) onto the mount point of the external drive.
Upgrading the core packages was the last thing I want to do. After that, I will 'grub-install /dev/sdc' (the device file for the external hard drive) and 'update-grub' in the chroot.
//This is a patch for gtk/gtkwidget.h that the above program depends on
--- 1238 void gtk_widget_set_default_colormap(GdkColormap *colormap);
+++ 1238 void gtk_widget_set_default_colormap(GdkColormap *colormap, GtkWidget *widget);
And Kenny_Strawn, that is impossible to read. IMO, window transparency should ONLY be used on inactive windows. And even then, it should only be a little bit.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.