Obviously, I'm on about desktops again. This time it's not anything specific as such though.
One of the best points I've always held about Linux is that immense amount of choices you have - this Window Manager over that one, the text editor from there instead of there, and so on.
It could be said that in places there is too much choice, and that the overwhelming number tends to be, well, overwhelming. But that's a topic for another time.
Like anyone else, I like thing to work my way. This means that while I'm now running a KDE4 desktop - which hasn't managed to disappoint me yet, a fair feat given past experience with this troublesome DE - not all my apps are KDE, or even QT based.
For example, while I'm running KWin as the window manager, the effects don't seem to want to stay on, even if all I want is the compositing. And of course, even if I can get that to work, the moment I start to use Portage, it disables them again because the compiling uses too much resources.
Compare this to Metacity with it's own built in compositor. It only disables itself if you tell it to, and doesn't get in the way at all. On the other hand, there's no standalone application to set the window border without pulling in a lot of Gnome.
Now, while KDE offers the option to use another Window Manager instead of KWin, besides having to remember how to set themes for that Window Manager, it also isn't going to integrate well.
The solution? I'm running KWin, with effects disabled and using 'xcompmgr' to give me Metacity-like compositing that doesn't turn itself off, though I have a handy plasmoid that looks like a little switch. Turning it on starts up xcompmgr, and turning it off kills it. There's a similar plasmoid available on kde-look.org that does this for KWin's own, but this one can be customized to do anything really.
Problem solved.
The programs I use also tend to be similar. Chromium is a GTK+ based application, as is GEdit, but both of them have a few things about them that I like and want to keep.
Konqueror has, rather impressively, managed to overcome both Chromium and Firefox as the default web browser (and file manager too, an invaluable feature for me) but I keep Chromium around because sometimes it does have it's little issues.
Similarly, while Kate and KWrite are decent applications too and also have their good points, GEdit is a long time friend of mine - it's familiar, I know it, and I know how to make it do what I want.
Some people say this is wrong, and one should stick to apps from one single toolkit, but with GTK+, QT, and ETK (Enlightenment, in case you're wondering) not to mention any other toolkits I've not noticed and of course anything running through Wine, you're never going to be able to get one single unified toolkit. There'll always be people who like applications for one toolkit, while running a desktop for another.
So in short, don't feel that because you're running one desktop, you can't choose applications from another toolkit. They may not look right, and sometimes they may need a little work to make them play nice. My workaround to compositing proves that.
But never be put off doing it - mix things up, go with what you want regardless of what others suggest.
In slightly unrelated news, has anyone ever managed to get KDE 4.7.x to emerge successfully on Gentoo? It doesn't seem to want to play nice with me. Not that I have any problems with the 4.6.5 I've got now, except a periodically segfaulting Konqueror, but I feel like giving it a try.
Right, that's all. Keep rocking, people.
Saturday, 6 August 2011
Friday, 22 July 2011
When giving it a Bash just doesn't cut it
Or what's in a Shell?
Bash is pretty much the de facto standard shell everyone sees whenever they open up a terminal. I can't say for BSD, Solaris or Mac systems, but on every Linux based system I've ever used, and even on Cygwin/MinGW on Windows, the Bash shell is the default.
Bash has and still does serve many people well. It's extendible with the bash-completion options, adding lines to the right files it sources can be quite powerful. Even the prompt itself can be customised a great deal.
But there comes a time for nearly every app on any system where the user will inevitably ask that question: 'Is there anything better out there?'
Of course 'better' is a matter of perspective. Some say KDE is better than Gnome. Some say the spartan desktops provided by just a simple tiling window manager are better than a fully fledge desktop session.
But the only real way to tell if something is better in your own opinion is of course to try it yourself.
Now, the Bash shell is something that like many people I rarely actually think about. I think in terms of the terminal itself - right on the console with no X session, within Terminator or a Gnome Terminal, maybe even xterm when all else fails for whatever reason. But essentially all they are is a way to give you your selected Shell - Bash.
Over time though, and through periodic trawls through package listings when bored, I keep noticing other shells. ksh, dash and zsh to name but a few.
Zsh is the only alternative I've tried yet, and after a little experimenting with it, its quickly become the default shell for me. I find it's even more powerful than Bash, without losing any functionality at all. The completion in Zsh can be autoloaded and is much better than in Bash.
Small annoyances such as forgetting to type 'cd' when moving around directories are easily resolved with a simple command. Type a directory, and it can be told to act as if you'd prepended it with 'cd'.
Often find yourself mistakenly typing suod instead of sudo, or other such similar mistakes? There's a little command that'll make zsh prompt and ask if you want it to auto-correct it for you.
There are two caveats though.
Firstly, if zsh can't find and .zshrc in your home folder, it'll assume you've never run it and go through a sometimes bemusing first-run wizard. Which is useful in it's way, but you're better of creating the file yourself and running around the Internet looking at the great many guides and pages on it - or of course, read the man pages on it. I'm not going to list all the pages here, but two that you should definitely look at are the Arch Linux wiki page, and the Gentoo Wiki page (Note that the latter is not linked to from gentoo.org - go to en.gentoo-wiki.org instead)
And Secondly, it doesn't always act the same way as Bash. For example, Home and End do not move to the start or end of the line you're entering. I've yet to find a fix for this, but it's only a minor annoyance for now.
These are just my initial impressions of it. I've barely been using it for an hour, but it's impressed me, and I'm sticking with it for now. As for you, as said earlier - the only way you'll be able to tell if it's better for you is to try it yourself.
That's all from me. Keep on rocking, people.
Bash is pretty much the de facto standard shell everyone sees whenever they open up a terminal. I can't say for BSD, Solaris or Mac systems, but on every Linux based system I've ever used, and even on Cygwin/MinGW on Windows, the Bash shell is the default.
Bash has and still does serve many people well. It's extendible with the bash-completion options, adding lines to the right files it sources can be quite powerful. Even the prompt itself can be customised a great deal.
But there comes a time for nearly every app on any system where the user will inevitably ask that question: 'Is there anything better out there?'
Of course 'better' is a matter of perspective. Some say KDE is better than Gnome. Some say the spartan desktops provided by just a simple tiling window manager are better than a fully fledge desktop session.
But the only real way to tell if something is better in your own opinion is of course to try it yourself.
Now, the Bash shell is something that like many people I rarely actually think about. I think in terms of the terminal itself - right on the console with no X session, within Terminator or a Gnome Terminal, maybe even xterm when all else fails for whatever reason. But essentially all they are is a way to give you your selected Shell - Bash.
Over time though, and through periodic trawls through package listings when bored, I keep noticing other shells. ksh, dash and zsh to name but a few.
Zsh is the only alternative I've tried yet, and after a little experimenting with it, its quickly become the default shell for me. I find it's even more powerful than Bash, without losing any functionality at all. The completion in Zsh can be autoloaded and is much better than in Bash.
Small annoyances such as forgetting to type 'cd' when moving around directories are easily resolved with a simple command. Type a directory, and it can be told to act as if you'd prepended it with 'cd'.
Often find yourself mistakenly typing suod instead of sudo, or other such similar mistakes? There's a little command that'll make zsh prompt and ask if you want it to auto-correct it for you.
There are two caveats though.
Firstly, if zsh can't find and .zshrc in your home folder, it'll assume you've never run it and go through a sometimes bemusing first-run wizard. Which is useful in it's way, but you're better of creating the file yourself and running around the Internet looking at the great many guides and pages on it - or of course, read the man pages on it. I'm not going to list all the pages here, but two that you should definitely look at are the Arch Linux wiki page, and the Gentoo Wiki page (Note that the latter is not linked to from gentoo.org - go to en.gentoo-wiki.org instead)
And Secondly, it doesn't always act the same way as Bash. For example, Home and End do not move to the start or end of the line you're entering. I've yet to find a fix for this, but it's only a minor annoyance for now.
These are just my initial impressions of it. I've barely been using it for an hour, but it's impressed me, and I'm sticking with it for now. As for you, as said earlier - the only way you'll be able to tell if it's better for you is to try it yourself.
That's all from me. Keep on rocking, people.
Wednesday, 20 July 2011
Office Suites
One of the main reasons I like Linux distros over Windows is because of how much software they come with out of the box - or at least, easily available. No hunting around for things, just ask the package manager.
But even the package managers have to admit defeat sometimes, and it seems that alternative Office Suites are one of those areas.
As far as I can tell, there are four main options: OpenOffice, LibreOffice, GOffice and KOffice.
The first two are well known enough. Both have pretty good track records, though OO.o may soon be heading away from that thanks to Apache.
GOffice isn't so much a suite as it is a collection of apps that give you most of it, but the down-side is that Abiword and Gnumeric can't always open documents not saved in their own formats - and the OpenDocument formats Libre/OpenOffice uses are the biggest casualty here, as I've yet to make them open one without getting a stream of garbage data.
KOffice on the other hand is a fair competitor to Open and Libre, and as its name suggests is designed to work with KDE. Which kind of makes it not so helpful for those of us who don't run KDE, or want to pull in half the dependencies just to work on our documents.
However, since my Gentoo install has begun to throw up unusual errors when trying to run LibreOffice, errors that refuse to be solved by rebuilding, removing all trace from the home directory and even starting on a fresh user, I'm at a bit of a loss. KOffice seems like overkill for a Gnome-based and mostly lightweight desktop, and as OpenOffice is doing the same as LibreOffice, it too is counted out.
GOffice as mentioned has trouble with the OpenDocument formats, which most of my work is, rather inconveniently, saved in.
This leaves me with a bit of a dilemma, since no one seems to be able to give even the slightest hint on the LIbreOffice errors (if you're curious, look here: http://www.linuxquestions.org/questions/gentoo-87/libreoffice-exits-immediately-after-starting-890419/) I can't work on my work.
For now I've got a temporary stop-gap measure by using the Windows LibreOffice through Wine, but it's far from perfect.
So does anyone happen to know of any LibreOffice-compatibile word processing apps out there?
But even the package managers have to admit defeat sometimes, and it seems that alternative Office Suites are one of those areas.
As far as I can tell, there are four main options: OpenOffice, LibreOffice, GOffice and KOffice.
The first two are well known enough. Both have pretty good track records, though OO.o may soon be heading away from that thanks to Apache.
GOffice isn't so much a suite as it is a collection of apps that give you most of it, but the down-side is that Abiword and Gnumeric can't always open documents not saved in their own formats - and the OpenDocument formats Libre/OpenOffice uses are the biggest casualty here, as I've yet to make them open one without getting a stream of garbage data.
KOffice on the other hand is a fair competitor to Open and Libre, and as its name suggests is designed to work with KDE. Which kind of makes it not so helpful for those of us who don't run KDE, or want to pull in half the dependencies just to work on our documents.
However, since my Gentoo install has begun to throw up unusual errors when trying to run LibreOffice, errors that refuse to be solved by rebuilding, removing all trace from the home directory and even starting on a fresh user, I'm at a bit of a loss. KOffice seems like overkill for a Gnome-based and mostly lightweight desktop, and as OpenOffice is doing the same as LibreOffice, it too is counted out.
GOffice as mentioned has trouble with the OpenDocument formats, which most of my work is, rather inconveniently, saved in.
This leaves me with a bit of a dilemma, since no one seems to be able to give even the slightest hint on the LIbreOffice errors (if you're curious, look here: http://www.linuxquestions.org/questions/gentoo-87/libreoffice-exits-immediately-after-starting-890419/) I can't work on my work.
For now I've got a temporary stop-gap measure by using the Windows LibreOffice through Wine, but it's far from perfect.
So does anyone happen to know of any LibreOffice-compatibile word processing apps out there?
Friday, 1 July 2011
USE flags and Updates
For once, something that at first seems like a regular annoyance has turned out to be an interesting habit.
I had originally decided not to customise the USE flags on my Gentoo install too much, preferring instead to modify them only where I felt necessary. After a bit of a delve into the details though, I've decided the reverse is true.
It's quite an interesting ability, being able to disable or enable support for something so easily, rather than having to dig into the configure-time details to see if things can be changed thus.
What's more, where I used to think I'd chafe at the time spent compiling periodic updates, I've found that properly set up, Gentoo is quite happy to update, or rebuild a large number of packages with new use flags or even both, without getting in the way too much. Maybe updates do take a little longer, but with the massive flexibility given, it's well worth it.
The only complaint I have is that there's no easy way to figure out what packages aren't needed any longer - you know the kind, they were pulled in as a dependency, but aren't needed any more? I used to regularly tidy up the system of such packages, but I can't seem to find any easy way to do that on Gentoo. At least not yet.
But overall... I don't think I'm going to be leaving the comfort of Gentoo anytime soon.
I had originally decided not to customise the USE flags on my Gentoo install too much, preferring instead to modify them only where I felt necessary. After a bit of a delve into the details though, I've decided the reverse is true.
It's quite an interesting ability, being able to disable or enable support for something so easily, rather than having to dig into the configure-time details to see if things can be changed thus.
What's more, where I used to think I'd chafe at the time spent compiling periodic updates, I've found that properly set up, Gentoo is quite happy to update, or rebuild a large number of packages with new use flags or even both, without getting in the way too much. Maybe updates do take a little longer, but with the massive flexibility given, it's well worth it.
The only complaint I have is that there's no easy way to figure out what packages aren't needed any longer - you know the kind, they were pulled in as a dependency, but aren't needed any more? I used to regularly tidy up the system of such packages, but I can't seem to find any easy way to do that on Gentoo. At least not yet.
But overall... I don't think I'm going to be leaving the comfort of Gentoo anytime soon.
Saturday, 4 June 2011
Gentoo: AKA Time Well Spent
Eight days ago, I started installing Gentoo Linux on my laptop.
Three days later, I had a working Gnome Desktop.
And now, after much patience, it's finished. Who'd have thought I'd finally get around to doing this?
Not me, if you'd asked me when I first understood what Gentoo was about.
There's still the odd little thing now and then, but they're now restricted to my making spelling error when trying to use Portage. The graphic frontends aren't entirely perfect, but they're good at what they do, and I'm getting to grips with how the whole thing works.
I've even managed to get some apps working that never worked for me before.
The biggest bother for me though is lib* updates - more often than not, this results in a lot of packages that depended on the old version needing to be rebuilt - but with the handy command of 'revdep-rebuild', even this is no problem.
I like Gentoo. It's a bit of a hassle to get up and running, especially if you're a stranger to configuring your own kernel (Which I cheat on and use genkernel with a few tweaks), but in the end I think it's worth it.
Not one for those without much patience though, that's for sure - especially if you decide to compile Firefox, Xulrunner, Wine or LibreOffice from source. These do take time. LibreOffice's ebuild helpfully says that it could take 'up to a day' depending on system speed. I found this to be a little inaccurate, taking this laptop a little over six hours - but even so, this is a bit of a wait.
Right, I'm done for now. Expect Gentoo-related posts whenever I remember I have a blog again unless something manages to push me off it. Which isn't likely.
Rock on.
Three days later, I had a working Gnome Desktop.
And now, after much patience, it's finished. Who'd have thought I'd finally get around to doing this?
Not me, if you'd asked me when I first understood what Gentoo was about.
There's still the odd little thing now and then, but they're now restricted to my making spelling error when trying to use Portage. The graphic frontends aren't entirely perfect, but they're good at what they do, and I'm getting to grips with how the whole thing works.
I've even managed to get some apps working that never worked for me before.
The biggest bother for me though is lib* updates - more often than not, this results in a lot of packages that depended on the old version needing to be rebuilt - but with the handy command of 'revdep-rebuild', even this is no problem.
I like Gentoo. It's a bit of a hassle to get up and running, especially if you're a stranger to configuring your own kernel (Which I cheat on and use genkernel with a few tweaks), but in the end I think it's worth it.
Not one for those without much patience though, that's for sure - especially if you decide to compile Firefox, Xulrunner, Wine or LibreOffice from source. These do take time. LibreOffice's ebuild helpfully says that it could take 'up to a day' depending on system speed. I found this to be a little inaccurate, taking this laptop a little over six hours - but even so, this is a bit of a wait.
Right, I'm done for now. Expect Gentoo-related posts whenever I remember I have a blog again unless something manages to push me off it. Which isn't likely.
Rock on.
Wednesday, 1 June 2011
From Gentoo
That's right, Gentoo. After only a few issues with getting the graphics card and wireless to play nicely, I have a functional Gnome desktop running on Gentoo.
I've been after something like this for a long time.
The problem now remains that since I chose to emerge gnome-light instead of the full Gnome suite, I have to fetch all the other bits and pieces I want, copy all kinds of things from my Sabayon home folder, and generally finish setting it up the way I want.
But the point is, it works.
And now I'm going to see how long it takes for me to break something.
This will probably be until I change USE flags, or add any more testing packages. Firefox 4 is one of them, but emerged after only a few minor issues.
Oh. And I have to get used to Portage. This could take me a bit longer. So I'm going to see what graphic Portage frontends there are and use one to give me a hand in this area.
That's all for now.
I've been after something like this for a long time.
The problem now remains that since I chose to emerge gnome-light instead of the full Gnome suite, I have to fetch all the other bits and pieces I want, copy all kinds of things from my Sabayon home folder, and generally finish setting it up the way I want.
But the point is, it works.
And now I'm going to see how long it takes for me to break something.
This will probably be until I change USE flags, or add any more testing packages. Firefox 4 is one of them, but emerged after only a few minor issues.
Oh. And I have to get used to Portage. This could take me a bit longer. So I'm going to see what graphic Portage frontends there are and use one to give me a hand in this area.
That's all for now.
Friday, 27 May 2011
A change or two
It's been a while since I last updated this, with good reason - too much has been changing.
So far, I've ditched Arch Linux because of issues with KDE and power management, ditched KDE in general (again) because as usual, I just can't seem to get on with it, and picked up both Sabayon and Gnome (again).
And now I'm headed from Sabayon to Gentoo.
Normally when I've tried Gentoo, I end up giving up before I even see a usable X session or desktop.
Over time, the reasons for this have been anything from a failed kernel config (I don't care what they say, it most definitely is NOT easy) to missing drivers or a lack of patience.
However, I'm putting all that aside and giving it another go.
And I'm using genkernel because I'm not going to muck about trying to build my own kernel.
Gentoo is often reported as having the most flexibility of all, quite probably because everything gets compiled (unless you opt for the -bin packages) with your choice of compiler and USE flags.
In deciding to use genkernel instead of tinkering, I've already taken one part of that flexibility and high-optimisation out of my soon-to-be (hopefully) install. In deciding not to alter any USE flags, I've removed another.
Why? Because my desktop, window manager and default apps change so much, that there isn't much point in tailoring everything for a GNOME session, then deciding I want to try KDE again and having to recompile many packages to give them KDE/QT support again. So I'm opting for wide-scale compatibility and as few rebuilds as I need.
So far, I have my typically vague plan of what I intend to end up with out of it.
In this case, it'll be a GNOME session, with GDM to login, Chromium as the browser, LibreOffice and Dropbox around, and WICD for the network management. And that's all. The rest will come as and when I get to it.
In theory, this shouldn't give me any trouble.
However, such theories generally don't translate to practice very well when dealing with me and Gentoo.
So with any luck, the next post here will come from a working Gentoo system, or be complaining about whatever put me off it this time.
Incidentally, has anyone ever managed to get the blogtk application to work with Blogger? It'd be nice to have a desktop app for posting these things - one that works, for a change.
Rock on, people.
So far, I've ditched Arch Linux because of issues with KDE and power management, ditched KDE in general (again) because as usual, I just can't seem to get on with it, and picked up both Sabayon and Gnome (again).
And now I'm headed from Sabayon to Gentoo.
Normally when I've tried Gentoo, I end up giving up before I even see a usable X session or desktop.
Over time, the reasons for this have been anything from a failed kernel config (I don't care what they say, it most definitely is NOT easy) to missing drivers or a lack of patience.
However, I'm putting all that aside and giving it another go.
And I'm using genkernel because I'm not going to muck about trying to build my own kernel.
Gentoo is often reported as having the most flexibility of all, quite probably because everything gets compiled (unless you opt for the -bin packages) with your choice of compiler and USE flags.
In deciding to use genkernel instead of tinkering, I've already taken one part of that flexibility and high-optimisation out of my soon-to-be (hopefully) install. In deciding not to alter any USE flags, I've removed another.
Why? Because my desktop, window manager and default apps change so much, that there isn't much point in tailoring everything for a GNOME session, then deciding I want to try KDE again and having to recompile many packages to give them KDE/QT support again. So I'm opting for wide-scale compatibility and as few rebuilds as I need.
So far, I have my typically vague plan of what I intend to end up with out of it.
In this case, it'll be a GNOME session, with GDM to login, Chromium as the browser, LibreOffice and Dropbox around, and WICD for the network management. And that's all. The rest will come as and when I get to it.
In theory, this shouldn't give me any trouble.
However, such theories generally don't translate to practice very well when dealing with me and Gentoo.
So with any luck, the next post here will come from a working Gentoo system, or be complaining about whatever put me off it this time.
Incidentally, has anyone ever managed to get the blogtk application to work with Blogger? It'd be nice to have a desktop app for posting these things - one that works, for a change.
Rock on, people.
Subscribe to:
Posts (Atom)