Tuesday, November 29, 2016

Visual Studio Code: Autohotkey-based popup Cheatsheet for Keyboard Shortcuts

11/29/2016: I like Visual Studio Code a lot - it's got some warts, and gaps, but there's some thing's it does amazingly well (and some it sort of stumbles at). If you write in Powershell, it's probably the best/lightest/most-stable editor I've found, with the range of features you get, and rampant-growth and availability in user-created extensions -  (Though it really needs better-rounded debugging... *grumble* ;P) .

Anyway, one of my pet peeves for 'Code.exe' is it's lack of good quick popup references for common tasks - well that and some of it's interface & control choices that don't match most of the common keystrokes and mouse behaviors I've gotten used to in other editors.

Autohotkey fills the gap!

Toward that end, the below is an Autohotkey-based quick-n-dirty Popup Cheatsheet for Visual Studio Code. If you use  AHK & 'Code', you might find this gapfills a niche.

I don't doubt you can hack Code.exe itself to display a menu with a hot key binding. But I work for a living ; I don't want to burn a lot of time learning how to build objects in code.exe itself. :P But I do make tons of use of AutoHotKey these days -- (automation tied to working for a firm with a lot more user-interaction than I've had in the past: BOILERPLATE! AUTOMATE!) --  so I decided yesterday to take a few minutes and whip up a quick popup dialog in AHK that just lists out the key keyboard shortcuts I want to use (especially where addon extension commands and bindings are concerned).

It's pretty simple, docs are inline in the script (stored & kept updated at Github):
Two chunks below: the .ahk script file, and a .csv file that drives the displayed menu.

Lemme know if you have any questions. :^D

What's your revision, Exchange?

11/29/2016: More quick-shared code: This is a tweaked variant of Bhargav Shukla's script that polls all Exchange 2007/2010/2013 boxes in the org, and reports on current Exch patch revision.
Changes I made were pretty minimal: adding pshelp, reformatting layout a tad, adding progress echo's, and renaming the output to a timestamped csv file, named for the script itself (easier to track changes over time, than the default 'results.csv' in your script directory). 

Here's the code

Autohotkey hotkeys for Ecco Pro

11/29/2016: I've committed to actively trying to post more of what I write for code snippets, time-permitting. :D
Today, frustration at a lack of the functional hotkeys I wanted in the old EccoPro outliner, led me to throw together some quick functions in Autohotkey.

This is very sketchy very quick & dirty, simple menu-automation. Gets the job done. I guess at most it'd save someone five mins or so tossing the necessary AHK Send commands together from scratch. :D
Here's the code

Tuesday, October 11, 2016

Ghacks Technology News

If you've been fighting to keep Microsoft's latest privacy-invasive (and win10-peddling) patches off of your computers, MS is now taking away the ability to choose which patches you want. Or even he choice to remove them at all...
via Facebook http://ift.tt/2dO843V

Wednesday, October 5, 2016

First Click: OK Google, why is iCloud storage so expensive?

I've got to agree. Bigger & bigger phones that can't be cloud backed up anywhere but Apple iCloud have resulted in fairly 'hidden' annual backdoor fees that are obnoxious compared to other cloud storage vendors.
via Facebook http://ift.tt/2dJfSD8

Monday, August 22, 2016

Microsoft to push all-in-one Windows updates - gHacks Tech News

Should be titled "Windows 10, coming back to your computer whenever Microsoft feels like it". The first thing I thought of, when I started seeing pundit's peddling the party-line on the announcement below, was that MS just side-stepped folks (like myself) who manually tear out some Windows Update patches immediately after monthly patches. Odd coincidence I just tore back _7_ Windows-10-peddling & MS data-spying patches from my Windows7 and Windows8.1 machines, yesterday. And now, we find out that Microsoft is taking away your ability to even pick and choose between patches at all: Starting in October, they're just releasing a _single_ patch for Win7/Win8 just like they have been for Win10. I've been shifting more and more of my machines at home to Linux, with this baloney, it looks like I've gotten fresh motivation to start looking at the laptops along with the utility roles (home theater pc, file server, music server).
via Facebook http://ift.tt/2be992q

Tuesday, August 2, 2016

My Microsoft Office 365 woes: Constant crashes, malware macros – and settings from Hell

THIS. We shifted to Office365 Office at work in April (I early-adopted on April Fools Day, apropos? :D) In the past, the centrally-managed workstation patching processes included monthly MS Office patching, bundled into managed & scheduled OS & desktop app patches. Which resulted in 1-2 mandated 'patching' shutdown & reboots per month. Now, with Office 365, I have Microsoft independently _pushing it's own_ unmanaged patch reboot demands, _in addition to_ the preexisting OS locally-managed patches. I've worked at firms that required detail time-accounting, so I routinely track every minute of my day in an app. I also run a lot of monitoring and dev components open on my desktop - which takes a while to get reloaded, after a reboot (which is why I hibernate my laptop daily for the trip home). Net result, every mandated reboot costs a minimum of 20mins of work-time. So, when I look back at time allocated to 'Mandated Workstation Patching' (company managed + o365), I find that in June alone of this year, I had to perform _8_ separate reboots on different days of the month. Some were prompted (or unprompted) patches, and some were reboots tied to sorting out buggy code in Office365. And yea, I'd echo most of the complaints from the below. Compared to the Office 2010 I'd run at work until April: Office 365 is _much_ slower, much more bloated for memory, and annoying as spit to any power user that works primarily from the keyboard (the shift to touchscreen interface support made a lot of useful shortcuts go away). Fact is, I still run an old copy of Office 2003 Visio from time to time at home, and I do some pretty fancy architecture diagrams for the office (with Visio2013 & now 2016): Visio 2003 isn't missing a single core function I rely on in Visio 2016/O365, but it runs much snappier, and a lot cleaner. Not to mention with a lot more stability. I'm starting to believe Office365's 'Ever-Green' continuous-revision concept actually means, 'Never-Stable'. #^|
via Facebook http://ift.tt/2afOFXY

Tuesday, July 19, 2016

CenturyLink Follows Comcast, Begins Charging Overage Fees • /r/cordcutters

Grrr. We've got CL dsl (only thing I hate more than greedy ISP's is having Comcast as an ISP). Nothing *wins* quite like *lose*!
via Facebook http://ift.tt/2ashjEX