use tramp mode; then, you can run email in full mouse-supporting glory on the client platform, and emacs will transparently copy files hence and forth. All you need is ssh access to the robot, not even emacs there.
Hopefully the 64-bit versions of various multimedia codecs will become available as part of the system; it's a bit sucky to have to use a 32-bit environment just to run Mplayer and friends on my Linux-AMD64 system...
Why, exactly, was work on GMC just given up on?
GMC caused to many development headaches, because it's based on the synchronous, console-mode MC which is sychronous. Porting it to a asynchronous (GUI) environment proved very hard, leading to lots of bugs.
Granted, if Nautilus was to dissolve that code would become the world's, but would outside programmers be able to catch onto it and take off from where they left off? I'm sure plenty of programmers out there have seen a plenthora of programs that are poorly commented, poorly put together...
If you're suggesting that Nautilus was badly written, please come up with some facts
With Miguel proclaiming "Let's Make Unix Suck Less" [via making everything more componentized, or, hell, the UNIX philosophy in general] the whole Nautilus idea is this complete contradiction toward what he supposedly believes in. The opposite is true. Nautilus really is a component container, exactly like Evolution. Check this.
there's only a windows dll, which has been there for a *long* time. For documentation on the ICQ protocol (which is _very_ ugly*) ) check:
http://www.d.kth.se/~d95-mih/icq/
*) one of the ugly things like the way is deals with someone marking himself as 'invisible'. This is implement by having the clients of his *peers* no longer showing the invisible man - well, if the clients are 'official' clients, that is...
use tramp mode; then, you can run email in full mouse-supporting glory on the client platform, and emacs will transparently copy files hence and forth. All you need is ssh access to the robot, not even emacs there.
Hopefully the 64-bit versions of various multimedia codecs will become available as part of the system; it's a bit sucky to have to use a 32-bit environment just to run Mplayer and friends on my Linux-AMD64 system...
n't "I-T"
Some corrections.
Why, exactly, was work on GMC just given up on?
GMC caused to many development headaches, because it's based on the synchronous, console-mode MC which is sychronous. Porting it to a asynchronous (GUI) environment proved very hard, leading to lots of bugs.
Granted, if Nautilus was to dissolve that code would become the world's, but would outside programmers be able to catch onto it and take off from where they left off? I'm sure plenty of programmers out there have seen a plenthora of programs that are poorly commented, poorly put together...
If you're suggesting that Nautilus was badly written, please come up with some facts
With Miguel proclaiming "Let's Make Unix Suck Less" [via making everything more componentized, or, hell, the UNIX philosophy in general] the whole Nautilus idea is this complete contradiction toward what he supposedly believes in.
The opposite is true. Nautilus really is a component container, exactly like Evolution. Check this.
there's only a windows dll, which has been there for a *long* time. For documentation on the ICQ protocol (which is _very_ ugly*) ) check: http://www.d.kth.se/~d95-mih/icq/ *) one of the ugly things like the way is deals with someone marking himself as 'invisible'. This is implement by having the clients of his *peers* no longer showing the invisible man - well, if the clients are 'official' clients, that is...
qmail does support mbox; in fact it does so by default.
mbox and to a lesser extent maildir, are supported by multiple mua's, so you could use a different mua every day.
what's missing is a cross-mua format for *indexing* these mbox's/maildir. indexing would speed things up *a lot*.