%Q doesn't work with %A

[white]

Thanks for the suggestions, sounds all reasonable for %Ax parameters. It's still not clear what %q%A should do.

I think it still wasn't clear what %q%A1 should do too. For example, when the first paramater (%A1) has this value:

Code: Select all

"Jack said: ""Hi there!"" and Mary said ""Hello!"""

The task is to suppress the quotes in the required area, which will be defined by two %q:
"-par1 '%q%A' -par2 '"%O"' -par3 '%|EnVar|'%q"
I specifically indicated "%O" here to account for any source of double quotes. For this reason, the last %q is placed here before ", not after.
This means that you won't have to process each parameter separately, you will just remove all the quotes in the string between the two %q.
Every first %q in the pair will simply remove all double quotes until the next %q.

But finally the suggestion seems clear: Strip all quotes from the final end result, including quotes explicitly inserted by the user.

[Fla$her]

But finally the suggestion seems clear: Strip all quotes from the final end result, including quotes explicitly inserted by the user.

The point is not what I want ideally, but how much faster it can be implemented. Read the penultimate sentence and the author's earlier explanations about long tests.
Before this, I had never even thought about this approach...

[white]

But finally the suggestion seems clear: Strip all quotes from the final end result, including quotes explicitly inserted by the user.

The point is not what I want ideally, but how much faster it can be implemented. Read the penultimate sentence and the author's earlier explanations about long tests.
Before this, I had never even thought about this approach...

The point is that this is the first suggestion that seems clear. Any other suggestions made by you weren't clear.

[Fla$her]

As said before, people's buttons etc. that already use both %Q and %A in the parameter field will break.

Before asserting this, one needs to know about such people. But you don't know. You only know about the technical component, but obviously not about the actual needs.

The linked suggestion by petermad describes exactly the current implementation. It does not strip quotes that are part of the filename itself.

Well, considering that petermad confirmed the current behavior as a bug, it's not exactly what he expected.
However, that is your thought about part of the name, because the discussion was about quotation marks in general, not in names in particular.
Your answer still didn't make it clear why you did't challenge the original goal when it made sense — 4 years ago.

Exactly, it is not the same thing. The current implementation works as designed, but you want something different.

It's not the same thing, because "as designed" in your case is not related to the idea, but to the development.

And you still haven't clearly said what this feature should do exactly.

You still haven't given any clear answers to my questions either:

What is a plugin system?
Again, give an example with such a file system and %Q. What do you want to achieve in interacting with names where %N returns "1" 2 "3"?

Any other suggestions made by you weren't clear.

This is just your opinion. I could give you a few quotes with examples, but you can find them yourself.
It's more important to me that I'm understood by ghisler(Author).

[ghisler(Author)]

A new parameter %q (lowercase) has now been added to Total Commander 11.57 RC6.

28.04.26 Added: Internal command parameter %q (lowercase): Remove all double quotes from parameters %A1, %A2 etc. and %|envvar| (32/64)