I thought I’d thoroughly read this article, but upon reading it again today, I noticed a key point I’d missed. If you can’t upgrade your SVN client, do a fresh checkout with the older client. I’m going to have to try this now…
This client is too old to work with working copy ‘XXX’
The full error message is:
This client is too old to work with working copy ‘.’; please get a newer Subversion client.
You will get this error message once you have used a Subversion client linked with a higher Subversion version, and then try to execute a command with a Subversion client linked with an older version, e.g., you used an 1.4.x client on your working copy, and now you try an svn 1.3.x client on the same working copy.
The reason for this is that Subversion 1.4 and 1.5 upgrade the working copies transparently on every command. But once the working copy format is upgraded, older clients can’t access the working copy anymore because they don’t know the new format.
The only solution to ‘fix’ this is to upgrade whatever clien
via This client is too old to work with working copy ‘XXX’ | TortoiseSVN
Came across this while debugging a program today in Eclipse:
0xBAADF00D : Used by Microsoft‘s LocalAlloc(LMEM_FIXED) to mark uninitialised allocated heap memory
…I very obviously forgot to initialize one of my variables. 😉
If you’re like me, you’re probably quite annoyed with the system beep in Ubuntu. Luckily, there’s an easy fix:
To disable it temporarily:
- In Terminal (or the console), enter: “sudo rmmod pcspkr”
- You should not hear the system beep until your next system reboot.
To disable it permanently:
- In Terminal (or the console), enter: “sudo nano /etc/modprobe.d/blacklist”
- At the end of the file, enter a new line “blacklist pcspkr”
- Type Ctrl+O (to save the file), then Ctrl+X (to exit nano)
- After your next system reboot, you should no longer here the system beep.
Thanks to Turning Off The System (hardware) Beep : Linux Tutorial for the info!
This is freakin’ awesome; I had no idea that you could assign keyboard shortcuts this easily:
- Press Ctrl+D or choose Font from the Format menu. (If you are using Word 2007, press Ctrl+D or click the Home tab of the ribbon, then click the small control at the bottom-right of the Font group.) Word displays the Font tab of the Font dialog box. (Click here to see a related figure.)
- Hold down Alt+Ctrl and, at the same time, press the plus sign on the numeric keypad. The mouse pointer turns into a clover symbol.
- Click on the Strikethrough check box in the Font dialog box. (As you move the mouse pointer to get ready to click, the mouse pointer may change back to an arrow instead of a clover; this is OK.) When you click, Word displays the Customize Keyboard dialog box with the insertion point blinking in the Press new Shortcut Key box. (Click here to see a related figure.)
- Type whatever shortcut key you want to use for the strikethrough format. Just hold down whatever combination of the Alt, Ctrl, and Shift keys you want, and then press the desired key to go with that combination. If the combination is already taken, that information shows just below the Customize Keyboard dialog box, and you can then change to a different shortcut key. (A good combination to consider is Alt+Shift+S or Ctrl+Alt+S, neither of which are used in a default installation of Word.)
- Click the Assign button. The shortcut key is now assigned to apply strikethrough formatting.
- Click Close to dismiss the Customize Keyboard dialog box.
- Click Cancel to dismiss the Font dialog box.
(via Topics: Strikethrough Shortcut Key)
More shortcuts available here: http://word.tips.net/W020_Shortcut_Keys.html
Woo-hoo! Another milestone!
Special thanks to the post Visual Studio 2008 Is Pretty Damn Slow… for giving me over 7,000 hits on its own! (Seems that people are still searching pretty heavily for Visual Studio 2008 being slow and how to fix it…)
Anyone ever seen this when attempting to use the “Press This” bookmarklet with a large chunk of text selected?
Interesting to note that they’re using LiteSpeed, as well.