Kai Jaeger

"But that works by injecting ")load xxx.dws" into the session, which is a bit naff." I disagree. That is exactly how it should be. And it should print "}XLOAD" to...

Also, anything printed to the session can be modified before actually executing it, for example ")load" can become ")copy"

I am not arguing with any of this. As long as the two behave the same;) On 12 June 2018 at 15:44, Gilgamesh Athoraya wrote: > Now change your prefs...

No pref at all. On 12 June 2018 at 15:49, Gilgamesh Athoraya wrote: > and your preference? > > — > You are receiving this because you authored the thread....

I fully agree with Andy: overwrite does not matter these days. I don't do overstrikes; that makes 99% of my destructive modes accidents.

I can see plenty of cons an no pro at all. Just saying. Any way to tell them apart would be an improvement.

That might well be a valid point from your prespective. From a user's perspective the feature makes perfect sense, and its absence is simply annoying.

When the deprecated flag is set there should also be an additional field "comment" that allows remarks like "See instead package x.y.z" etc.

> May I suggest that Tatin continue to scan all the registries anyway Well, that comes with a significant performance penalty - are you willing to pay that price for...

Also: * Mention the /LOG command line parameter for SetUp.exe * Explain why setting the version number of an EXE is imperative.