On Wed, 2 Sep 2020 10:50:37 +0200, R.Wieser wrote:
I think you have gotten enough "purposefully helpful suggestions" to be able
to improve upon it. :-) Go git.
Holy ****, Rudy Wieser.
o I'm shaking my head in serious amazement.
I have never before, not even once, thought you ever added any value.
o Nor, that you posted for any other reason than to toot your own horn.
But this time, for God's sake, you added value!
o And, this time, for heaven's sake, you actually comprehended the topic.
Dammit' Rudy. You actually _can_ add value!
o Hooray! I mean this.
To me, past posts are water under the bridge; everyone can be rehabilitated
o Well, everyone except Snit... but I digress.
Almost everything you wrote was apropos, and which I agree with.
o You even realized the hastily written tutorial had afterthoughts added.
For example, you are completely correct in surmising that I added the
killall _after_ I hastily wrote the initial tutorial, simply because I was
testing the tutorial out on a new system, which _needed_ the killall.
So I figured I'd add the multi-command shortcut, after the fact.
o But that's not all that you were correct in surmising.
For example, you're correct in intuiting I do everything from the Run
command, where, interestingly enough, I did since Windows 95 days.
o Win+R cclip
That clears the clipboard.
o It's easier than finding and then clicking on a shortcut.
Hence, you're correct that it doesn't matter _where_ the user puts the
shortcut; and you're correct that a novice might not know how to _create_ a
shortcut; and you're correct that the STARTIN is meaningless in most cases
with shortcuts; and you're correct that the Subject line, which was the
last thing added in that late-night post, doesn't fully match the main
point of the tutorial; and you're correct that I don't define, in this
tutorial (but I do define in others, but they're not mentioned) how to go
about choosing the logic for the file system hierarchy; and you are correct
that the AppPaths key can be any name, but my point was that whatever name
you give it must end with ".exe", which your point is that I wasn't clear
about that point; and you are correct that I use the terms "folder" and
"directory" interchangeably; and you are correct that you can omit the
shortcut altogether, since the AppPaths key works fine for commands; and
you are correct that creation of the icon isn't an important part of the
tutorial (I have posted _plenty_ of icon-creation & modification
tutorials); and you are correct that pinning the shortcut (not the icon) to
the taskbar is the correct terminology as is pointing out that it's also
quickly accessed that way; and you are correct that the example I gave of a
multi-command shortcut is a "bad example" (but... but... you missed one
thing, and one thing only, AFAICT)...
The one thing you missed, interestingly, is that the multiple line command
fails to work for some syntactical reason, unknown to be at the moment:
o What syntax combines 2 commands into a single shortcut TARGET line?
https://groups.google.com/forum/#!topic/alt.msdos.batch/azQbz6D_v0Y
Specifically this, as yet unanswered query on the killall syntax:
https://groups.google.com/d/msg/alt.msdos.batch/azQbz6D_v0Y/qeTHydqyAQAJ
==cut below for the question about multi-line shortcut target syntax==
QUESTION about TARGET multi-line-command syntax
1. This works from the Windows command line to kill all the users' tasks:
Win+R cmd {ctrl+shft+enter}
taskkill /f /fi "USERNAME eq %COMPUTERNAME%\%USERNAME%" /IM *
2. That also seems to work just fine from a shortcut TARGET line:
TARGET = taskkill /f /fi "USERNAME eq %COMPUTERNAME%\%USERNAME%" /IM *
3. It also seems to work in a comspec cmd (needed for multiple commands):
TARGET = %comspec% /c taskkill /f /fi "USERNAME eq %COMPUTERNAME%\%USERNAME%" /IM *
4. But it doesn't seem to work in multi-command shortcut comspec syntax:
TARGET = %comspec% /c "echo off | clip" & veracrypt /dismount /force /q & taskkill /f /fi "USERNAME eq %COMPUTERNAME%\%USERNAME%" /IM *
Q: What syntax change is needed for that multi-line comspec cmd to work?
See also:
o Tutorial for creating cclip & killall clearing the Windows clipboard & killing users' tasks in one fell swoop
https://groups.google.com/forum/#!topic/alt.msdos.batch/DqBXiTJ6FA0
--
Sometimes you need just a little bit of syntactical help to get it working.
==cut above for the question about multi-line shortcut target syntax==
Rudy,
Do you, or anyone else, know what's syntactically wrong in the query above?
--
Usenet is a wonderfully public discussion of varying people's views.