[TC 11.57rc2] cm_Edit - Quoting behavior with different configurations for the editor

[AntonyD]

"For multiple names separated by a space or |"
ok all 3 examples contain OR a space OR a |, so far, so good.

"angle brackets are used for the entire parameter N"
Hmmm...let's see:

Code: Select all

N="name 1|name 2|name 3"

I see entire parameter N but do not see <> here. Sentence does not cover all cases?

"but double quotes are only allowed for |"
Again let's see the 1 variant of examples:

Code: Select all

N="name 1|name 2|name 3"

OK I understand this as a proof that " "-s must cover the entire parameter
EVEN IF any of the sub-names could potentially contain space inside 'em
Strange - but so be it...
And now another example:

Code: Select all

N=<"name 1" "name 2" "name 3">

from this case I understand this as a proof that " "-s must cover EACH sub-names,
especially because some of 'em could potentially contain spaces inside 'em.
BUT if it so - I do not understand why the first variant is allowed?

[Fla$her]

I see entire parameter N but do not see <> here. Sentence does not cover all cases?

It shouldn't. This information is already at the very beginning of the parameter description. "Equivalent entries:" does not refer only to "Note:".

BUT if it so - I do not understand why the first variant is allowed?

The same answer.

[AntonyD]

N="name": The name(s) of the file(s) to be opened/created - separate multiple file names with the | character (with or without double quotes), or put each name in double quotes and separate them by spaces. Alternatively, use templates from the "+" button to create multiple files. If a file already exists, it will just be opened, not overwritten with a new one.
Note: Use angle brackets to pass multiple names in double quotes:
N=<"name1" "name2" "name3"> or N=<"name1"|"name2"|"name3">

This is what we have right now in a CHM help file.

Suggestion is covering as I see ONLY the NOTE: section:

Note: For multiple names separated by a space or |, angle brackets are used for the entire parameter N, but double quotes are only allowed for |.
Equivalent entries: N="name 1|name 2|name 3" or N=<name 1|name 2|name 3> or N=<"name 1" "name 2" "name 3">

And so as I see - there are NO any specific sentences ABOVE the NOTE section in which we can to learn something else.
ONLY in this section <> are mentioned. And their mention is strictly within the framework of one situation:
"angle brackets are used for the entire parameter N"
So where and what information is given above that could answer my misunderstanding of logic?
for a "proper?" example of using sub-names in parameter N:

Code: Select all

N="name 1|name 2|name 3"

I do not see <> which "are used for the entire parameter N"

In other words, I cannot in any way or from any sentence of these text paragraphs somehow extract
the essence of the possibility of avoiding the using of these brackets.
Thus, it seems to me that they should ALWAYS be present if more than one sub-name is specified.
And in the Notes section, you can not specify an example line where they are not used.

[ghisler(Author)]

What's so difficult in understanding this sentence suggested by Fla$her?

Note: For multiple names separated by a space or |, angle brackets are used for the entire parameter N, but double quotes are only allowed for |.

Angle brackets are used for the entire parameter N. Double quotes (for the entire parameter N) are only allowed for separator | not for spaces between names.

[Fla$her]

Suggestion is covering as I see ONLY the NOTE: section:

This is your key mistake, which leads to false conclusions. The suggestion concerns the last two lines.
The last line completes the description of the N parameter.
The fact that a line comes after a line with "Note:" does not in any way obligate it to be related only to it.
This is just a set of options for equivalent entries for several names, reflected in the above description of the parameter.

The first sentence has all the details that relate to the relevant parts of the examples:

The name(s) of the file(s) to be opened/created - separate multiple file names with the | character (with or without double quotes), or put each name in double quotes and separate them by spaces.

[Fla$her]

2petermad
1. You're repeating the information from the first sentence.
2. Conciseness suffers.
3. The contradiction with 'otherwise double quotes can also be used', which I mentioned earlier, remains. It's clear what you want to say, but the wording itself is flawed.

[AntonyD]

What does conciseness have to do with it - are we writing a SMS with a 140-character limit or what is it equal to?
The current description with the proposed edit describes some isolated exceptions too concisely, too pointwise,
and generally does not make it possible to understand exactly how to set the attributes of this parameter.
Once again, I still don't see anywhere a description of why angle brackets may or may not be
mentioned in a line for the case of multiple attributes? And that's just one question!

The suggestion concerns the last two lines.

and this is exactly the Note: section in question;)

[petermad]

2Fla$her
Sorry I deleted my previous post before >I saw that you responded to it.

New approach:

Note: In case of names in double quotes, angle brackets (< >) must enclose the entire parameter N, otherwise double quotes can also be used:
N=<"name 1" "name 2">, N=<"name 1"|"name 2"> or N="name 1|name 2".

[AntonyD]

2petermad
Can you explain the reason why we should discuss the POSSIBILITY of these brackets in general?
Why are they not mandatory for multiple parameter attributes?

[petermad]

What's so difficult in understanding this sentence suggested by Fla$her?

Note: For multiple names separated by a space or |, angle brackets are used for the entire parameter N, but double quotes are only allowed for |.

"are used for" makes it look like TC are using them (setting them), not that the user has to use them.

"double quotes are only allowed for |" - that is not true: N=""name 1"|"name 2"" is not allowed. It is not enough to write only allowes for | - it should be: "only allowed with not quoted names separated with |."

[petermad]

2petermad
Can you explain the reason why we should discuss the POSSIBILITY of these brackets in general?
Why are they not mandatory for multiple parameter attributes?

That is not my decision it is Ghisler's. But if the brackets are made mandatory now, it will break backwards compatibility

[Fla$her]

What does conciseness have to do with it - are we writing a SMS with a 140-character limit or what is it equal to?

See the reaction to my first suggestion.

and generally does not make it possible to understand exactly how to set the attributes of this parameter.

And I don't see any information that is missing. Everything is clear and understandable to me. Each sentence and example complement each other.

Once again, I still don't see anywhere a description of why angle brackets may or may not be mentioned in a line for the case of multiple attributes?

Because it's designed that way. Such things are not explained. The condition under which angle brackets may be used is described:

For multiple names separated by a space or |, angle brackets are used for the entire parameter N, but ...

New approach:

1. I have already written that double quotes for the second example are redundant, which the user will not know. An example with N=<name 1|name 2> is needed.
2. At the end, there should be a double quote, as far as I understand.

"double quotes are only allowed for |" - that is not true: N=""name 1"|"name 2"" is not allowed.

We return to this part, where I initially suggested another option, but Google didn't like something about it.

[petermad]

At the end, there should be a double quote, as far as I understand.

Yes, corrected in the post.

We return to this part, where I initially suggested another option, but Google didn't like something about it.

What you write in this part does not address N=""name 1"|"name 2"" which I believe is not allowed.

[petermad]

When I look at the current help:

N="name": The name(s) of the file(s) to be opened/created - separate multiple file names with the | character (with or without double quotes), or put each name in double quotes and separate them by spaces.
.
.
Note: Use angle brackets to pass multiple names in double quotes:
N=<"name1" "name2" "name3"> or N=<"name1"|"name2"|"name3">

It eems to already cover it - except for the examples which I think should be:

N=<"name 1" "name 2" name3> or N=<"name 1"|"name 2"|name3>

if it correct that names without spaces never needs quotes, even if there are also quoted names with spaces in the parameter.

[AntonyD]

Well, if the author's priority and principle is to write as little information as possible in the CHM-help about all options for using parameters,
then perhaps we should not continue this discussion, because in one small sentence with some kind of limitation in the number of
characters to describe it, we simply will not be able to describe what we would like.

P.S.
In general, it should be noted that in the description of the CHM help file, there are very few distinctive elements of the description that help to quickly find what you need, read and understand—what the emphasis in the description is based on.
https://i.ibb.co/0wS7t0X/2026-04-27-183650.png
Here is a very characteristic passage - all the parameters are arranged almost on top of each other. Inside the descriptions, there is no highlighting of the parameter and its attributes. No highlighting for examples - they should differ in text from the general description text. Everything is so similar that it is difficult for the eye to catch a line in order to read and translate it to understand what you are doubting...

And on top of all this, we are also imposing restrictions on the amount of text in this explanation?
But we want to make the reference understandable for everyone, right? Or only for native speakers of one language?