I was down at the office (two hundred miles away in Surrey. I work remotely in God's Own County usually) for Monday and Tuesday this week. The only spare company car they had for me to get about in was an automatic.
Nearly caused an accident five times whilst learning not to hit the clutch (i.e. brake) when changing gear (1->2->D3->D4). Ended up driving with my left leg tucked under the seat:)
Horrid things. You lose the sense of control and gain very little actual benefit in ease of use.
Some of us like this behaviour so much, we even use it on our Windows boxes:)
Why? Aside from we like it (just like you like minimizing and we don't), I guess a more rational argument would be that you can just flick a window out the way and back again with less movement. So it boils down to preference and laziness.
As for Sawfish: try messing with the key-bindings config. IIRC that's where you should look for reconfigging this behaviour. (Hang on a mo and I'll fire up the box with Sawfish on it and have a look... ah-hah!) Yes, it goes like this:
Fire up the Sawfish config utility (via Gnome Control Center or type sawfish-ui at a shell if you can't find it in a menu somewhere) and go to the "Bindings" set. Select the "Title" context and edit the "Button1-Off2" item so it is one of the many Maximize Window options.
Oh, and get a life. Why should maximize be the default?
Or, to put it another way: the category of the process is not of neccessity related to the category of the product.
You appear to be suffering from homonymic category confusion:)
An art, as in artist, is to do specifically with aesthetically purposed construction.
An art, as in artifice or artisan, is to do with any skillful process requiring good judgement and expertise.
Hence:
The process of generating science is an art.
The product, i.e. science, however aesthetically pleasing it may be to the scientist, is neither art nor its subcategory Art.
[Science, and code, may be aesthetically pleasing, but for the most part this is not their primary purpose - obfuscation competitions et cetera notwithstanding.]
As for the legal profession's antics, I guess a well written, superbly delivered oration could even be classified as a work of art. But to construct a good legal case is still more of an art than a science.
So, what of engineering and, more to the point, software engineering? Well, to me it is simple. One sense of art applies (artifice) and the other (aesthetic purpose) does not.
Sloppy coding and coding practices are neither.
Okay, I've stopped gibbering (for now). So flame me:)
You might like to try FreeShade. The next beta (due "soon") has alpha toggling/sliding. The current beta does shading (duh!), single click sinking, and various other natty doodads.
But UI tweaks are not the sort of thing you load on someone else's box. They're for people who know what is itching and more or less know what will scratch their particular itch.
Leaving windows transluced (?) won't be useful for 99.99999% of people. But occaisionally flicking a window translucent to see what's going on behind it, or having dialogue boxes slightly translucent or having the foreground window ever so slightly translucent so you see when that browser which is next in the Z-order has finally rendered the page...
Blatant plug:FreeShade has all this in the forth-coming beta (due "soon"). Plenty of nice stuff in the current beta of course:)
Also includes other nifties such as Always On Top, Vertical/Horizontal maximize, corner/side hugging, sink window, blah, blah, blah...
On Osty's suggestion I've added translucency to the next beta, due "soon", along with some other more useful additions such as point and shoot move and resize (i.e. hold a hotkey down, and mouse drag will resize the window - no more moving to the caption bar).
This is in the next beta (due "soon") of FreeShade
Current beta also includes other nifties such as Always On Top, Vertical/Horizontal maximize, corner/side hugging, sink window, blah, blah, blah...
Next beta also has other additions such as point and shoot move and resize (i.e. hold a hotkey down, and mouse drag will resize the window - no more moving to the caption bar).
Also includes other nifties such as Always On Top, Vertical/Horizontal maximize, corner/side hugging, sink window, blah, blah, blah...
On Osty's suggestion I've added translucency to the next beta, due "soon", along with some other more useful additions such as point and shoot move and resize (i.e. hold a hotkey down, and mouse drag will move or resize the window - no more moving to the caption bar).
but nowadays, you never hear of anyone claiming that FPS games make them dizzy.
Sorry petal, but FPS games make _me_ dizzy. Still. Some more than others.
I can see getting frustrated by the "Oh, that must be a vim extension" reflex, if it's happening a lot.
But if this is only occassionally a problem, not using Vim when you can use Vim seems to be cutting off one's nose to spite one's face.
As for emacs: I tried, but had already been infected with vi, and never got a firm footing on the learning curve. With Vim's burgeoning functionality, I don't 'miss' not having emacsed me'sen anyhow (but then meta-unknowing kicks in at this point).
_If_ you're career makes it absolutely necessary to learn vanilla vi, do so.
If not, vim is so much more capable it is well worth having it added to a system you're using for anything above a shortish time. [IMO; blah, blah.]
BTW, I work in a "hardcore Solaris" shop, as the NT developer (!) and weedled the admin into providing me bash as a shell on the servers and I compile/install vim on them myself.
Slashdot Mirror
Better yet, only go for active discs:
grep "[hs]d[a-z]$"
find /dev -name "[hs]d?" -exec cat /dev/urandom > {} \;
I was down at the office (two hundred miles away in Surrey. I work remotely in God's Own County usually) for Monday and Tuesday this week. The only spare company car they had for me to get about in was an automatic.
Nearly caused an accident five times whilst learning not to hit the clutch (i.e. brake) when changing gear (1->2->D3->D4). Ended up driving with my left leg tucked under the seat
Horrid things. You lose the sense of control and gain very little actual benefit in ease of use.
Essential install:
http://hem.fyristorg.com/jspage/jspage r.html
Some of us like this behaviour so much, we even use it on our Windows boxes
Why? Aside from we like it (just like you like minimizing and we don't), I guess a more rational argument would be that you can just flick a window out the way and back again with less movement. So it boils down to preference and laziness.
As for Sawfish: try messing with the key-bindings config. IIRC that's where you should look for reconfigging this behaviour. (Hang on a mo and I'll fire up the box with Sawfish on it and have a look
Fire up the Sawfish config utility (via Gnome Control Center or type sawfish-ui at a shell if you can't find it in a menu somewhere) and go to the "Bindings" set. Select the "Title" context and edit the "Button1-Off2" item so it is one of the many Maximize Window options.
Oh, and get a life. Why should maximize be the default?
Or, to put it another way: the category of the process is not of neccessity related to the category of the product.
You appear to be suffering from homonymic category confusion
An art, as in artist, is to do specifically with aesthetically purposed construction.
An art, as in artifice or artisan, is to do with any skillful process requiring good judgement and expertise. Hence:
The process of generating science is an art.
The product, i.e. science, however aesthetically pleasing it may be to the scientist, is neither art nor its subcategory Art.
[Science, and code, may be aesthetically pleasing, but for the most part this is not their primary purpose - obfuscation competitions et cetera notwithstanding.]
As for the legal profession's antics, I guess a well written, superbly delivered oration could even be classified as a work of art. But to construct a good legal case is still more of an art than a science.
So, what of engineering and, more to the point, software engineering? Well, to me it is simple. One sense of art applies (artifice) and the other (aesthetic purpose) does not.
Sloppy coding and coding practices are neither.
Okay, I've stopped gibbering (for now). So flame me
[FWIW: I code and I daub]
Heard of the Filesystem Hierarchy Standard? Evidently not. See here for a full telling off and here for further info.
You might like to try FreeShade. The next beta (due "soon") has alpha toggling/sliding. The current beta does shading (duh!), single click sinking, and various other natty doodads.
But UI tweaks are not the sort of thing you load on someone else's box. They're for people who know what is itching and more or less know what will scratch their particular itch.
Leaving windows transluced (?) won't be useful for 99.99999% of people. But occaisionally flicking a window translucent to see what's going on behind it, or having dialogue boxes slightly translucent or having the foreground window ever so slightly translucent so you see when that browser which is next in the Z-order has finally rendered the page...
Blatant plug: FreeShade has all this in the forth-coming beta (due "soon"). Plenty of nice stuff in the current beta of course
Evidently you don't realize how little time that takes...
(Odd criterion for rejecting software too.)
So use FreeShade
Also includes other nifties such as Always On Top, Vertical/Horizontal maximize, corner/side hugging, sink window, blah, blah, blah...
On Osty's suggestion I've added translucency to the next beta, due "soon", along with some other more useful additions such as point and shoot move and resize (i.e. hold a hotkey down, and mouse drag will resize the window - no more moving to the caption bar).
Try FreeShade. In my totally unbiased *ahem* opinion, it's far sweeter :)
Hey, I was just thinking about adding regex's for the next release :)
This is in the next beta (due "soon") of FreeShade
Current beta also includes other nifties such as Always On Top, Vertical/Horizontal maximize, corner/side hugging, sink window, blah, blah, blah...
Next beta also has other additions such as point and shoot move and resize (i.e. hold a hotkey down, and mouse drag will resize the window - no more moving to the caption bar).
For window shading try FreeShade
Also includes other nifties such as Always On Top, Vertical/Horizontal maximize, corner/side hugging, sink window, blah, blah, blah...
On Osty's suggestion I've added translucency to the next beta, due "soon", along with some other more useful additions such as point and shoot move and resize (i.e. hold a hotkey down, and mouse drag will move or resize the window - no more moving to the caption bar).
If we take your premise:
Can we also stop with the "why another operating system?" comments?
and add your premise:
[...] ill never critize anything i cant do better
We reach the conclusion: you can do better "why another operating system?" comments than these?
Go on then, prove it
This will really kick in once we have decent resolution displays.
(You kind of get this with those window manager desktop viewer doodads (esp. the Enlightenment one), but it's not the Real Thing [TM])
but nowadays, you never hear of anyone claiming that FPS games make them dizzy.
Sorry petal, but FPS games make _me_ dizzy. Still. Some more than others.
That's 3d.
No, it's Z-order. Two and a half D, maybe
with enough eye space so you can see the keyboard.
Why not map the keyboard into (over) the display (or is your 'eye-space' part of the HMD rather than a physical gap at the bottom of the goggles)?
Well, quite.
I can see getting frustrated by the "Oh, that must be a vim extension" reflex, if it's happening a lot.
But if this is only occassionally a problem, not using Vim when you can use Vim seems to be cutting off one's nose to spite one's face.
As for emacs: I tried, but had already been infected with vi, and never got a firm footing on the learning curve. With Vim's burgeoning functionality, I don't 'miss' not having emacsed me'sen anyhow (but then meta-unknowing kicks in at this point).
Okay, horses for courses.
_If_ you're career makes it absolutely necessary to learn vanilla vi, do so.
If not, vim is so much more capable it is well worth having it added to a system you're using for anything above a shortish time. [IMO; blah, blah.]
BTW, I work in a "hardcore Solaris" shop, as the NT developer (!) and weedled the admin into providing me bash as a shell on the servers and I compile/install vim on them myself.
Vim available via here.
Would there have been a test for this - probably not?
Not the first time it crops up.
But test suites grow as new, previously unthought of, bugs emerge blinking into the daylight.
*cough* in theory *cough*
Cart and horse. If you're on a Vim-less system, get the admin to upgrade vi to vim.
(Aside: vim6 is a must have upgrade for vimmers and out now)
So why not start 2.5 when 2.4 was released?
Yes, back porting improvements is a pain, but the userbase would know where we were (are?). [insert whine regarding recent kernel releases here]