Comments for Count Infinity http://www.countinfinity.com/blog A collection of impossible things Wed, 16 Nov 2011 17:57:56 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on .svn/tmp directory may be missing or corrupt by Matt http://www.countinfinity.com/blog/2010/10/svntmp-directory-may-be-missing-or-corrupt/#comment-2111 Matt Wed, 16 Nov 2011 17:57:56 +0000 http://www.countinfinity.com/blog/?p=157#comment-2111 You are a lifesaver! You are a lifesaver!

]]> Comment on .svn/tmp directory may be missing or corrupt by Lindsay http://www.countinfinity.com/blog/2010/10/svntmp-directory-may-be-missing-or-corrupt/#comment-1998 Lindsay Fri, 15 Jul 2011 02:46:26 +0000 http://www.countinfinity.com/blog/?p=157#comment-1998 Oh my goodness, thank you so much for posting this. I cleaned my hard drive of empty folders without even a thought about possibly corrupting my svn repo. I did not realize how many friggin' empty tmp folders it uses. Saved me hours of trying to figure out to use a dos command to recursively search for missing tmp folders and create them. Oh my goodness, thank you so much for posting this. I cleaned my hard drive of empty folders without even a thought about possibly corrupting my svn repo. I did not realize how many friggin’ empty tmp folders it uses. Saved me hours of trying to figure out to use a dos command to recursively search for missing tmp folders and create them.

]]> Comment on Disabling (Fixing) Google’s New Instant Preview by John Crenshaw http://www.countinfinity.com/blog/2010/11/disabling-fixing-googles-new-instant-preview/#comment-1931 John Crenshaw Wed, 18 May 2011 18:33:54 +0000 http://www.countinfinity.com/blog/?p=169#comment-1931 @Jon, I tested that case specifically when I first crafted this code and it worked then. It looks like something that Google changed since then has partially broken #3 and #4 in my revised requirements. In many respects, given that this is really a hack for something not under my control, it is a pleasant surprise that it still works at all. I'll look into this when I get a chance and try to make those last two cases work properly again. Until then, toggling off by clicking the magnifying glass again DOES work, so if you open the preview, click the magnifying glass again to dismiss it. Certainly not ideal, but better than nothing until I can find time to update the code. @Jon, I tested that case specifically when I first crafted this code and it worked then. It looks like something that Google changed since then has partially broken #3 and #4 in my revised requirements. In many respects, given that this is really a hack for something not under my control, it is a pleasant surprise that it still works at all.

I’ll look into this when I get a chance and try to make those last two cases work properly again. Until then, toggling off by clicking the magnifying glass again DOES work, so if you open the preview, click the magnifying glass again to dismiss it. Certainly not ideal, but better than nothing until I can find time to update the code.

]]> Comment on Disabling (Fixing) Google’s New Instant Preview by jon http://www.countinfinity.com/blog/2010/11/disabling-fixing-googles-new-instant-preview/#comment-1926 jon Mon, 09 May 2011 04:41:54 +0000 http://www.countinfinity.com/blog/?p=169#comment-1926 what is happening is that this works fine UNTIL you click on the magnifying glass, no random clicks calls the preview UNTIL after you click for a preview with the eyeglass icon, once you click it off by clicking anywhere (a desired feature), then the page is back to ANY random click brings up the preview again. the desired behavior doesn't 'stick' once you use the icon once and turn it off. you must reload the page after each use of the preview magnifying glass icon to turn on one (1) preview and turn it off again. if you hover over a result, that one's eyeglass icon turns a brighter blue. when you click off a preview, they ALL highlight for a sec before going grey again, and then its like they all (each result's) are 'active' for a click, which results in the google default behavior anyway. Is there any way to fix that? what is happening is that this works fine UNTIL you click on the magnifying glass, no random clicks calls the preview UNTIL after you click for a preview with the eyeglass icon, once you click it off by clicking anywhere (a desired feature), then the page is back to ANY random click brings up the preview again. the desired behavior doesn’t ‘stick’ once you use the icon once and turn it off. you must reload the page after each use of the preview magnifying glass icon to turn on one (1) preview and turn it off again. if you hover over a result, that one’s eyeglass icon turns a brighter blue. when you click off a preview, they ALL highlight for a sec before going grey again, and then its like they all (each result’s) are ‘active’ for a click, which results in the google default behavior anyway.

Is there any way to fix that?

]]> Comment on Disabling (Fixing) Google’s New Instant Preview by anonymaus http://www.countinfinity.com/blog/2010/11/disabling-fixing-googles-new-instant-preview/#comment-1916 anonymaus Tue, 26 Apr 2011 20:27:18 +0000 http://www.countinfinity.com/blog/?p=169#comment-1916 It works, I love it! Thank you. It works, I love it! Thank you.

]]> Comment on 12 Reasons Ruby Should be Banished to Whatever Firey Pit It Came From by Nate http://www.countinfinity.com/blog/2011/04/12-reasons-ruby-should-be-banished/#comment-1886 Nate Thu, 07 Apr 2011 15:41:58 +0000 http://www.countinfinity.com/blog/?p=205#comment-1886 Awww. I was expecting something serious, like continued use of Ruby will cause the earth to split in half or something like that. :) Awww. I was expecting something serious, like continued use of Ruby will cause the earth to split in half or something like that. :)

]]> Comment on Disabling (Fixing) Google’s New Instant Preview by John Crenshaw http://www.countinfinity.com/blog/2010/11/disabling-fixing-googles-new-instant-preview/#comment-1833 John Crenshaw Sat, 02 Apr 2011 05:58:56 +0000 http://www.countinfinity.com/blog/?p=169#comment-1833 Thanks Ben. You just made my day. Thanks Ben. You just made my day.

]]> Comment on Disabling (Fixing) Google’s New Instant Preview by ben http://www.countinfinity.com/blog/2010/11/disabling-fixing-googles-new-instant-preview/#comment-1771 ben Tue, 29 Mar 2011 14:33:29 +0000 http://www.countinfinity.com/blog/?p=169#comment-1771 THANK YOU! It works on FF4 with no problem so far. This is the way it should behave. It wouldn't piss me off so bad it if just WORKED THE WAY IT SHOULD, instead of bringing up the preview whenever you click anywhere and then having to hit the tiny X. THANK YOU! THANK YOU! It works on FF4 with no problem so far. This is the way it should behave. It wouldn’t piss me off so bad it if just WORKED THE WAY IT SHOULD, instead of bringing up the preview whenever you click anywhere and then having to hit the tiny X. THANK YOU!

]]> Comment on Microsoft, My Wife is Crying by John Crenshaw http://www.countinfinity.com/blog/2010/12/microsoft-my-wife-is-crying/#comment-801 John Crenshaw Wed, 26 Jan 2011 19:49:45 +0000 http://www.countinfinity.com/blog/?p=186#comment-801 It does still count down under at least some circumstances. There are registry entries you can set to get some control over this, but by default, I know for a fact that 7 will still count down, at least some of the time. I saw it myself just 2 months ago on a brand new Windows 7 machine and was fortunate enough to stop it with only a couple of seconds to go. If you've never experienced it, you probably just have your settings set to the one option where it will never be a problem (which ironically is the setting that Windows makes the biggest fuss about). I was sitting in the room at the time, and I can tell you to an infinite certainty, there was no humanly possible way that she could have prevented the reboot. One second AutoCAD was running, the next second, the whole computer was shutting down, and there was no way to stop it. Best guess is that a countdown started in the background while AutoCAD was running in full screen mode (which prevented her from ever even seeing the countdown, even though she was sitting there working on the computer at the time). Another (but less plausible) theory is that a mouse click or keyboard shortcut at exactly the wrong moment "Approved" the reboot. A confirmation dialog would absolutely address the specific problem, because: 1. There would be no way for the computer to reboot while the user is away 2. It adds a clear layer of confirmation before anything happens 3. It guarantees that the user has the option to cancel any potentially unwanted reboot. 4. If the user opts to click on the message blindly/randomly, the problem is no longer a fundamentally broken updater with no respect for the user's potentially unsaved data; the problem in this case would be that the user did something stupid, and lost their own data as a direct result. Case in point: Most installers check for software that is currently running, but that needs to be closed to complete the installation. They don't automatically close the programs, don't have a timer, etc. These installers simply indicate that "the following programs are running and need to be closed before the installation can be completed." The user can choose to terminate these programs from the dialog, or close them manually. If a reboot is needed, they just pop up a message and ask. The user will respond when it is convenient. I've never lost data because of either behavior. I've never seen anyone lose data because of this, or heard anyone complain about losing data because of it. If someone randomly clicks the wrong button, they'll kick their own butt for it, but are highly unlikely to blame Microsoft. This is a good interface. It does still count down under at least some circumstances. There are registry entries you can set to get some control over this, but by default, I know for a fact that 7 will still count down, at least some of the time. I saw it myself just 2 months ago on a brand new Windows 7 machine and was fortunate enough to stop it with only a couple of seconds to go. If you’ve never experienced it, you probably just have your settings set to the one option where it will never be a problem (which ironically is the setting that Windows makes the biggest fuss about).

I was sitting in the room at the time, and I can tell you to an infinite certainty, there was no humanly possible way that she could have prevented the reboot. One second AutoCAD was running, the next second, the whole computer was shutting down, and there was no way to stop it. Best guess is that a countdown started in the background while AutoCAD was running in full screen mode (which prevented her from ever even seeing the countdown, even though she was sitting there working on the computer at the time). Another (but less plausible) theory is that a mouse click or keyboard shortcut at exactly the wrong moment “Approved” the reboot.

A confirmation dialog would absolutely address the specific problem, because:
1. There would be no way for the computer to reboot while the user is away
2. It adds a clear layer of confirmation before anything happens
3. It guarantees that the user has the option to cancel any potentially unwanted reboot.
4. If the user opts to click on the message blindly/randomly, the problem is no longer a fundamentally broken updater with no respect for the user’s potentially unsaved data; the problem in this case would be that the user did something stupid, and lost their own data as a direct result.

Case in point: Most installers check for software that is currently running, but that needs to be closed to complete the installation. They don’t automatically close the programs, don’t have a timer, etc. These installers simply indicate that “the following programs are running and need to be closed before the installation can be completed.” The user can choose to terminate these programs from the dialog, or close them manually. If a reboot is needed, they just pop up a message and ask. The user will respond when it is convenient. I’ve never lost data because of either behavior. I’ve never seen anyone lose data because of this, or heard anyone complain about losing data because of it. If someone randomly clicks the wrong button, they’ll kick their own butt for it, but are highly unlikely to blame Microsoft. This is a good interface.

]]> Comment on Controlling a Subdomain with Robots.txt by John Crenshaw http://www.countinfinity.com/blog/2010/07/controlling-a-subdomain-with-robots-txt/#comment-800 John Crenshaw Wed, 26 Jan 2011 19:17:11 +0000 http://www.countinfinity.com/blog/?p=51#comment-800 Yes, this is the basic idea of the whole thing. Your robots.txt file maps virtually behind the scenes, giving you subdomain level control. Yes, this is the basic idea of the whole thing. Your robots.txt file maps virtually behind the scenes, giving you subdomain level control.

]]>