and for
commands like: *powershell.exe should not require full path

Moderators: Hacker, petermad, Stefan2, white
commands like: *powershell.exe should not require full path
I also use PowerShell, but why should I take a script when TC provides a native function.
The right move! Please remove all extreme whitespace characters, as well as exclude empty strings from the search for a string by number.
What do you mean with extreme? Tabstops?Please remove all extreme whitespace characters
Is that really a good idea? For example, when copying a button to the clipboard, empty lines are placeholders for empty fields, so ignoring them would assign the wrong values.exclude empty strings from the search for a string by number
No. All the topmost/lowest/leftmost/rightmost.
If it were a text file (like "%FL" here) rather than a clipboard, I would agree. But very often (in the same browser) lines are selected in bulk, where there are a lot of unnecessary empty lines, and there is no desire to count them. It is much easier to count the filled lines.ghisler(Author) wrote: 2024-11-05, 08:27 UTC Is that really a good idea? For example, when copying a button to the clipboard, empty lines are placeholders for empty fields, so ignoring them would assign the wrong values.
Topmost what? Windows? Files? I don't get you at all.No. All the topmost/lowest/leftmost/rightmost.
=
Take 'edge' instead of 'extreme'.Please remove all topmost/lowest/leftmost/rightmost whitespace characters
Code: Select all
string1
string2
string3
string4
Code: Select all
string1
string2
string3
string4
Code: Select all
string
Code: Select all
string
2ghisler(Author)04.11.24 Added: New pseudo environment variable %$CLIPNAME1%, %$CLIPNAME2% etc.: Inserts line 1, line 2 etc. from clipboard, characters replaced like with $CLIPNAME, removes leading and trailing spaces (32/64)
04.11.24 Added: New pseudo environment variable %$CLIPNAME0%: Same as %$CLIPNAME%, but replaces line breaks with spaces (32/64)
04.11.24 Added: New pseudo environment variable %$CLIPNAME% inserts up to 8191 characters from clipboard, replaces forbidden characters *?|<> with underscores_ (32/64)
04.11.24 Added: New pseudo environment variable %$CLIPBOARD1%, %$CLIPBOARD2% etc.: Inserts line 1, line 2 etc. from clipboard, otherwise unmodified (32/64)
04.11.24 Added: New pseudo environment variable %$CLIPBOARD0%: Same as %$CLIPBOARD%, but replaces line breaks with spaces (32/64)
04.11.24 Added: New pseudo environment variable %$CLIPBOARD% inserts up to 8191 unmodified characters from the clipboard (32/64)
Code: Select all
text
Code: Select all
' text '
Code: Select all
string1
string2
Code: Select all
string1
string2
Code: Select all
Name 1
Name 2
Name 3
Unicode characters or just bytes?04.11.24 Added: New pseudo environment variable %$CLIPBOARD% inserts up to 8191 unmodified characters from the clipboard (32/64)
I don't get it. The idea is when you use e.g. menu Mark - "Copy names with path to clipboard" to generate a valid command line with all the names after each other. That's why it's called %$CLIPNAME0%.But you didn't do exactly what I asked you to do. It's necessary to delete line breaks. Replacing with spaces only spoils everything.
How can you get a valid command line with a bunch of extra spaces?The idea is when you use e.g. menu Mark - "Copy names with path to clipboard" to generate a valid command line with all the names after each other.
Such a command is not declared in history. I tried it and it returns the same as %$CLIPBOARD%.That's why it's called %$CLIPNAMES0%.
Normally parameters are separated by spaces.How can you get a valid command line with a bunch of extra spaces?
Once again, this is not normal:
Code: Select all
' text '