Paranoia? 
I've had situations whereâand I can't remember any now, of courseâthe tilde-path failed in a Keyboard Maestro shell script action. It might've been with rsync, but I'm honestly not sure. Ever since, I just convert the tilde paths to full paths.
You could remove it with no change in functionality for the screen capture command, I think.
-rob.
Okay, thanks makes sense. I also noticed the double underscores for the local__New Name. I am guessing that was for the same reason to just be safe so Shell could call on those and habit of Global Variables needing those instead of local_New Name. I know you already know you don't need those so I am really just learning. I have learned a lot from this macro and spent several hours with it now.
Actually that's so that the dialog only shows "New Name." That's what the double underscores do.
-rob.
Okay I was thinking it was for the Shell since local variables remove local and instance in user prompts.
Still wrapping my head around a few things in the script that I am wanting to do with having it increase with padded numbers. Been at this for a several hours now.
I could've sworn I tested this a few times, but I just tried it again and it looks like this command does not like relative paths. So it makes sense to have this in here. I'm putting it back.
if [ -f "$KMVAR_newNameCheck" ]; then echo "Duplicate"; fi
I could've sworn I tested this a few times, but I just tried it again and it looks like this command does not like relative paths. So it makes sense to have this in here. I'm putting it back.
if [ -f "$KMVAR_newNameCheck" ]; then echo "Duplicate"; fi
I updated my first post with the one I will be using for screen captures from now on. Nice to only have one shortcut for these after all these years. It was funny while making these there were dozens of times that I needed my screen capture shortcut, but it wasn't there.
I spent about six hours trying to make a macro that would allow you, if it was a conflicting name to allow it to search the desktop and increase the number with a padded zero, but I was ultimately unsuccessful. Maybe somebody with more knowledge would be able to do that. I searched many forum posts on the wiki. I know KM can do it, however that is not something I am skilled enough yet to be able to do. I am learning to know when to surrender something.
~ isn't expanded when inside a double-quote. So handling a ~ path that also includes spaces can get... interesting.
But rather than mess around with search and replace and tokens, use the "Standardize Path" Filter to get your path into a double-quotable form:
This is so smart Rob, wow!
Your coloring & @skillet 's "if"-ing resulted in a macro that offers plenty of "how to"s to wannabe macroheads such as myself. It's pretty, useful, and clever.
This is great.
Will make good use of it!
Shottr's fast & accurate OCR occupies my ââ„âO. It offers the option to "cut line breaks" - that could be a useful feature to integrate into the OCR macro you made (which otherwise should be no different than yours perhaps?). Quality between Shottr and your OCR macro was 1:1 in a quick test (perhaps b/c Shottr uses native OCR?).
Thankfully Shottr is super light & fast (and good for quick edits where Snagit or another editor is too heavyweight).
Thanks for this pleasant surprise (improved screenshots!) 
Thanks I have tried several and I agree about SnagIt. I have been using that for about 15 years since it came out and have the latest version. There are some really neet things about it especially in this latest build for 2025 with numbering steps and simplifying that process but over all more than what I need other than the scrolling window capture. I haven't found anything that works with everything quite like Snagit to paste everything together from any window where you manually scroll yourself for windows that can't be seen.
heh
February must've been screenshot month. @noisneil's hat was in the ring too!
--
Not sure I ever finished drafting that comment but came to post something else -
I tried using / in a filename and received an error.
One screenshot macro did some clever checking to avoid illegal filenames (at least duplicate filenames) - might've been this one or another. Anyway, I'm not sure if it was also watching for naughty characters like forward slash. Certainly for this macro, I forgot I couldn't use forward slash in macOS filenames....... ... wait, we can, and just confirmed. Well, then perhaps this macro has a quirk where it glitches out on that character? (...maybe something gets encoded...)
Honestly, these macros work so well already there's no way I'll prioritize looking at this - just gonna remember "no slash" instead, but thought I'd mention and copy the error log:
2025-03-26 16:26:50 Execute macro âSuper Fast Screen Capture and Renameâ from trigger The Hot Key â§â3 is pressed
2025-03-26 16:27:14 Action 16810947 failed: Move or Rename file /tmp/screenshot_48967647-3E96-48D7-A560-76079A59CB0E.png failed with âscreenshot_48967647-3E96-48D7-A560-76079A59CB0Eâ couldnât be moved to âJustAFileNameButWatchOutHereComesTheForwardSlashAfterThisCharacterâ because either the former doesnât exist, or the folder containing the latter doesnât exist
2025-03-26 16:27:14 Move or Rename file /tmp/screenshot_48967647-3E96-48D7-A560-76079A59CB0E.png failed with âscreenshot_48967647-3E96-48D7-A560-76079A59CB0Eâ couldnât be moved to âJustAFileNameButWatchOutHereComesTheForwardSlashAfterThisCharacterâ because either the former doesnât exist, or the folder containing the latter doesnât exist in macro âSuper Fast Screen Capture and Renameâ (while executing Move file from /tmp to destination, and rename).
On the rare chance someone happens to lose a screenshot and finds this post, using Finder's "Go To Folder" with the temporary filename (e.g. /tmp/screenshot_48967647-3E96-48D7-A560-xxx.png) will take you right there!
