> You do realize the shuttle was designed with core memory, right? > Like hand-woven magnetic cores, for fuck's sake.
You're shittin' me, right? Please say you are. Because. WOW. That would make NASA just about the only company with computer systems literally capable of dumping core.
> What I noticed was that the moment I switched to vi I got half as much finger movement, and the pain > started going down instead of up. Even though I'd tried to be careful with how I used emacs.
The only difference I can see is that with vi, you don't need to stretch the 1/4" from "a" to "control". Both editors make extensive use of esc.
What am I missing? Unless it's for the cursor keys, you don't need to move your right hand off the keyboard *at all* in emacs.
I can *more* than hold my own, touch-typing-wise, and generally, I don't really mind using the arrow keys in emacs.
The reason? If I'm using the arrow keys, it's because I'm cursoring around the document for something, which was already cost me huge amounts time; a few hundred nanoseconds aren't going to make a big difference. Additionally, since the key repeat rate is much slower than my intercharacter typing speed, the time required to move one hand from one well-known location to another becomes pretty much irrelevant. Just listen to a good piano player playing fast scales, the hand-jump takes an almost inaudible amount of time when we're talking static targets (not like a mouse).
When I need to jump around within the line I'm editing, I will often use C-a, C-s, . Counter-intuitive? Sure, but it works for me. It means I can jump halfway across the screen, to exactly where I want to be, very quickly.
The commands you need are global-set-key, backward-char, forward-char, previous-line and next-line.
Me, I prefer to use the perfectly functional arrow keys, although I have on occasion mapped C-i, C-j, C-k and C-l as cursor keys when dealing with an arrow-less keyboard.
I can't found the number of times vi has spewed an occasional ]A while I was scrolling through a document, because it got confused in the middle of a vt100 escape sequence *growl*
I can't believe you've used Emacs enough to "earn" a year off due to disability, but you never took the time to learn how to use the editor properly.
I have been using XEmacs 19.14 exclusively for a VERY long time (Let's see... apparently, it was built in September 1996....). I don't think I've *ever* touched the meta key in that entire time.
Hint: tapping esc is equivalent to holding meta.
Hint II: The control key belongs beside the A. If you have a fucked up keyboard that puts it somewhere else (like below the shift key), remap your goddamned keyboard.
Hint III: The esc key belongs beside the 1. If you have a fucked up keyboard that puts it somewhere else (like off by itself to the left of the F1 key), remap your goddamned keyboard.
So, to re-indent code: meta control q translates in to:
- tap esc with ring finger (requires a slight hand stretch; F finger stays where it belongs)
- hold control with pinky (moves only a fraction of an inch)
- tap q with with ring finger (natural position)
I can't believe you got a year off work and not even an hour of EMACS remedial physio.
LOL -- back in the good ol' days, FTP sites didn't have ratios! Ratio-aware FTP clients are a relatively new invention.
In the good ol' days, the warez d00dz cracked accounts on poorly-secured uni or corporate boxes (often via that old sendmail root shell 'sploit), and the admins often wouldn't notice for ages.
I remember back in '92 or so, ftp.xerox.com was a 0-day warez site for a LONG time. That was hilarious. Xerox? GET IT? ROTFLMAO!
Your Kato Ballroom slideshow is borked on my box -- I had to disable my web dev toolbar and status bar in order to be able to click on the horizontal scrolly to get through the pics.
Re:Why use XHTML when IE cannot parse it?
on
The Future of HTML
·
· Score: 1
More to the point -- why use XHTML when it breaks ????
I had to throw all my pages into quirks mode not long ago, because I needed a *really* basic table, that simply was unexpressible in CSS and rendered wrong in XHTML. *grumble grumble*
Or, rephrase it nicely. Trust me on this one. I only spent 30s on this analysis, but I'm arrogant^H^H^H^H^H^H^H^H^Hexperienced enough to know I'm right.;)
30s of investigation on my park shows that their HTTP header parsing is fux0red. The biggest problem IMNSHO is that they are *not* looking for the end of the HTTP header, they are looking for the end of the FIRST PACKET.
This will break any HTTP client which uses multiple write()s to the socket while constructing its query, and either takes too long for Nagle, has the Nagle Algorithm turned off, or constructs a query which exceeds the MTU of any network between itself and GoDaddy.
GoDaddy is badly broken. The programmer who wrote the redirect code DID NOT read Stevens UNP or TCP/IP Illustrated Volume I.
The JRE "fix" is probably just a default state change of Nagle or the HTTP header contruction code in some fancy-pants object. (I'm a UNIX C hacker, not a Java guy).
Symantec has been *hoping* to deliver something worthwhile ever since they stopped developing for DOS-mode.
Face it, the Norton Utilities used to be *great*. Now they suck! Norton Anti-Virus has never been spectactular. Norton Ghost.. Well, Norton Ghost is pretty good; at least the version I have; it still runs under DOS4GW with a non-MS GUI.
I ran two XServers on my Alpha... about a hundred years ago with RedHat 5... One on the mobo card, one on a Trident 9860 or something like that plugged into the PCI bus.
Now, you get two *displays* doing this, not one big screen, or a display with two screens.
All I had to two was fire up a different X Server, with a different X config file. Oh, and I had to set the keyboard and mouse on one of them to non-existant.. I used x2x to get mouse and keyboard on the other monitor.
Out of curiosity, did you hit the x or did you hit cancel?
IIRC, the JavaScript confirm() function returns three values -- true, false, or null, depending on whether you hit ok, cancel, or x. Unfortunately, most users think x and cancel are the same, and a lot of programmers forget to check for the null -- so when you hit x, you get the default behaviour in the code (whatever that might be).
The reason you can't interact with firefox until the confirm dialog is finished is actually sort of simple -- it's defined by the W3C to effectively be a page-modal dialog box. The FF developers have made it be a window-modal box. So far so good. So, they COULD make it so that the bookmarks and so forth worked, but that's about all they can legally do... short of adding an option to completely disable JavaScript for that page.
Slashdot Mirror
> You do realize the shuttle was designed with core memory, right?
> Like hand-woven magnetic cores, for fuck's sake.
You're shittin' me, right? Please say you are. Because. WOW. That would make NASA just about the only company with computer systems literally capable of dumping core.
> Researchers found that the Sony patch changed settings in IE so
> that any Web site could install software on those machines."
Wait. So, Sony is setting IE back to its default security settings?
That hardly seems newsworthy.
When I mentally "hear" that line, it is indeed with a fake eh-spanish accent.
Therefore, I conclude that IMDb is probably correct.
> What I noticed was that the moment I switched to vi I got half as much finger movement, and the pain
> started going down instead of up. Even though I'd tried to be careful with how I used emacs.
The only difference I can see is that with vi, you don't need to stretch the 1/4" from "a" to "control". Both editors make extensive use of esc.
What am I missing? Unless it's for the cursor keys, you don't need to move your right hand off the keyboard *at all* in emacs.
I can *more* than hold my own, touch-typing-wise, and generally, I don't really mind using the arrow keys in emacs.
The reason? If I'm using the arrow keys, it's because I'm cursoring around the document for something, which was already cost me huge amounts time; a few hundred nanoseconds aren't going to make a big difference. Additionally, since the key repeat rate is much slower than my intercharacter typing speed, the time required to move one hand from one well-known location to another becomes pretty much irrelevant. Just listen to a good piano player playing fast scales, the hand-jump takes an almost inaudible amount of time when we're talking static targets (not like a mouse).
When I need to jump around within the line I'm editing, I will often use C-a, C-s, . Counter-intuitive? Sure, but it works for me. It means I can jump halfway across the screen, to exactly where I want to be, very quickly.
The terminal I was having problems with was an *actual* DEC vt100.
Either linux or vi is (was?) broken. Pick which. The terminal emulation was, by definition, perfect, since it was not emulated.
I also had similar problems with Tektronics 4107.
*sigh*
The commands you need are global-set-key, backward-char, forward-char, previous-line and next-line.
Me, I prefer to use the perfectly functional arrow keys, although I have on occasion mapped C-i, C-j, C-k and C-l as cursor keys when dealing with an arrow-less keyboard.
I can't found the number of times vi has spewed an occasional ]A while I was scrolling through a document, because it got confused in the middle of a vt100 escape sequence *growl*
I can't believe you've used Emacs enough to "earn" a year off due to disability, but you never took the time to learn how to use the editor properly.
I have been using XEmacs 19.14 exclusively for a VERY long time (Let's see... apparently, it was built in September 1996....). I don't think I've *ever* touched the meta key in that entire time.
Hint: tapping esc is equivalent to holding meta.
Hint II: The control key belongs beside the A. If you have a fucked up keyboard that puts it somewhere else (like below the shift key), remap your goddamned keyboard.
Hint III: The esc key belongs beside the 1. If you have a fucked up keyboard that puts it somewhere else (like off by itself to the left of the F1 key), remap your goddamned keyboard.
So, to re-indent code: meta control q translates in to:
- tap esc with ring finger (requires a slight hand stretch; F finger stays where it belongs)
- hold control with pinky (moves only a fraction of an inch)
- tap q with with ring finger (natural position)
I can't believe you got a year off work and not even an hour of EMACS remedial physio.
sed -e 's/clients/servers/' < old_post > new_post
Argh.
LOL -- back in the good ol' days, FTP sites didn't have ratios! Ratio-aware FTP clients are a relatively new invention.
In the good ol' days, the warez d00dz cracked accounts on poorly-secured uni or corporate boxes (often via that old sendmail root shell 'sploit), and the admins often wouldn't notice for ages.
I remember back in '92 or so, ftp.xerox.com was a 0-day warez site for a LONG time. That was hilarious. Xerox? GET IT? ROTFLMAO!
Yo, Jeff --
Your Kato Ballroom slideshow is borked on my box -- I had to disable my web dev toolbar and status bar in order to be able to click on the horizontal scrolly to get through the pics.
More to the point -- why use XHTML when it breaks ????
I had to throw all my pages into quirks mode not long ago, because I needed a *really* basic table, that simply was unexpressible in CSS and rendered wrong in XHTML. *grumble grumble*
Send this post to your vendor: http://slashdot.org/comments.pl?sid=170621&cid=142 16183
;)
Or, rephrase it nicely. Trust me on this one. I only spent 30s on this analysis, but I'm arrogant^H^H^H^H^H^H^H^H^Hexperienced enough to know I'm right.
And the JRE version is just a red-herring.
30s of investigation on my park shows that their HTTP header parsing is fux0red. The biggest problem IMNSHO is that they are *not* looking for the end of the HTTP header, they are looking for the end of the FIRST PACKET.
This will break any HTTP client which uses multiple write()s to the socket while constructing its query, and either takes too long for Nagle, has the Nagle Algorithm turned off, or constructs a query which exceeds the MTU of any network between itself and GoDaddy.
GoDaddy is badly broken. The programmer who wrote the redirect code DID NOT read Stevens UNP or TCP/IP Illustrated Volume I.
The JRE "fix" is probably just a default state change of Nagle or the HTTP header contruction code in some fancy-pants object. (I'm a UNIX C hacker, not a Java guy).
In that case, I wonder if you could talk the post office into forwarding the mail? :)
Symantec Hopes this, Symantec Hopes that..
Symantec has been *hoping* to deliver something worthwhile ever since they stopped developing for DOS-mode.
Face it, the Norton Utilities used to be *great*. Now they suck! Norton Anti-Virus has never been spectactular. Norton Ghost.. Well, Norton Ghost is pretty good; at least the version I have; it still runs under DOS4GW with a non-MS GUI.
Rent the office where they used to be. Get registration-changing info sent to you in the [snail] mail.
Piece of cake.
I ran two XServers on my Alpha... about a hundred years ago with RedHat 5... One on the mobo card, one on a Trident 9860 or something like that plugged into the PCI bus.
Now, you get two *displays* doing this, not one big screen, or a display with two screens.
All I had to two was fire up a different X Server, with a different X config file. Oh, and I had to set the keyboard and mouse on one of them to non-existant.. I used x2x to get mouse and keyboard on the other monitor.
Not only is it the anniversary of the Nazi party; it's also the date in 1984 that RMS started developing GNU.
Now that's a sobering thought.
Right-CTRL, Right-ALT, non-numeric delete.
The three-fingered salute only requires three fingers, y'know.
Wow, sounds like you should be working for Berman and Braga!
I saw this on 20/20... like, oh at least TEN YEARS AGO!
That's very interesting, I wonder how the hell I got that into my head? I don't use those dialogs on a regular basis, but still...
[Hmmm]
Okay, I've tested NS4.7/UNIX, but IE 4 won't load anymore.
Ah... Seems I may be confused with the prompt() function. That's really odd, though, I would've bet a case of beer on my previous assertion.
Thanks for bringing that to my attention.
Out of curiosity, did you hit the x or did you hit cancel?
IIRC, the JavaScript confirm() function returns three values -- true, false, or null, depending on whether you hit ok, cancel, or x. Unfortunately, most users think x and cancel are the same, and a lot of programmers forget to check for the null -- so when you hit x, you get the default behaviour in the code (whatever that might be).
The reason you can't interact with firefox until the confirm dialog is finished is actually sort of simple -- it's defined by the W3C to effectively be a page-modal dialog box. The FF developers have made it be a window-modal box. So far so good. So, they COULD make it so that the bookmarks and so forth worked, but that's about all they can legally do... short of adding an option to completely disable JavaScript for that page.