[Suggestion]Introducing the "*" to Noreread

[WatchUer]

I don't like auto refresh when activating totalcmd, so I configure Noreread in wincmd.ini like this:
[Configuration]
Noreread=ABCDEFGHIJKLMNOPQRSTUVWXYZ\/:

In TC's options dialog, Copy/Delete section, we can use "*" for setting "Use compatibility mode for the following drives".

So maybe we can use the "*" for Noreread and Noreread2 too?
"*" should means auto refresh nothing.

[ghisler(Author)]

Unfortunately that would be incompatible with older TC versions, so I will not add it, sorry.

[karlchen]

Hi, Christian.

I admit I fail to see how this would break compatibility:

The old syntax of NOREREAD would still be valid in the new T.C. version. Additionally the new T.C. version would understand "*" as meaning all drives and network and whatsoever. So upgrading an existing installation will not cause any trouble at all.

Compatibility issue might only occur if you downgrade an existing TC 7 installation and re-use the existing wincmd.ini for the downgraded TC 6.56 version as well.

But is this not true for any other new variable/parameter introduced by new TC versions? They will never be understood by previous versions.

So what is the trouble with enhancing the NOREREAD syntax?

Kind regards,
Karl

[Clo]

2karlchen

Hello Karl!

• I agree, I don't see what is wrong using “*” there.
- It's a pretty standard wildcard, understood everywhere in a PC - even in HTML as :
“all the rest¦all needed” for a width¦height for instance - …
- It could be very useful for users like WatchUer who have a mountain of drives
(I guess that occurs often in companies having a large network…)
{ Aside : What should occur then, when the whole alphabet is used ? IIRC, one could get the next drive as AA:\… Is this still valid ? }

 VG
Claude
Clo

[roentgen]

If it has come to that, although I see little chance for this to get implemented, how about a special noreread for removable disks (regardless of assigned drive letter)?

[StatusQuo]

I admit I fail to see how this would break compatibility:

I pretty much like the chance to use the INI of a newer version on other PCs with possibly older versions of TC, so I support keeping compatibility.

But is this not true for any other new variable/parameter introduced by new TC versions?

AFAIS: No, new/unknown parameters are ignored. (I have some additional comments in the wincmd.ini, saved with names/headings that are unused by TC, starting with a user name followed by "_".)
Changing existing parameter formats can introduce values, that old versions don't understand.

But will an "*" cause problems in older versions - except that it will have no function, causing Noreread to be disabled?
If that's the only problem, I could live with that. Everybody still could use the conventional method for keeping compatibility (worth mentioning in the help).