Ondrej Kelle

Hi, perhaps this helps: A long time ago, I've solved a similar problem differently. I split the setup into two processes: 1. client with UI and 2. elevated server with no UI. I used some modified old-style DataSnap code for inter-process communication which was easy at the time but that's just an implementation detail. https://tondrej.blogspot.com/2007/06/datasnap-to-rescue.html

According to the documentation, it should:

A long time ago I wrote one for files in the $(DELPHI)\Source directory: https://cc.embarcadero.com/Item/18989 It could be adjusted to work for any files on the library search path.

(I apologise if I'm missing the context here.) Automatically and unconditionally sorting units alphabetically doesn't seem to be a good idea. If you have multiple units exposing the same identifier then changing the order of units in the uses clause changes how they are resolved, probably leading to unintended changes to runtime behaviour of your code.

git svn rebase is what I usually do.

Hi. Sorry, I haven't used it for years now and I have no idea.

Without UNION ALL referencing itself, it's just a non-recursive CTE.

Your CTE is in fact not recursive as it doesn't reference itself or use UNION ALL. Generalized syntax for a recursive CTE looks like this: WITH RECURSIVE <cte_alias> AS ( SELECT <parent data> -- root node’s data UNION ALL SELECT <child data> -- children’s data JOIN <cte_alias> ON <parent_link> ) -- DO // for the Delphians SELECT * FROM <cte_alias> Source: https://www.firebirdsql.org/file/community/ppts/fbcon11/FBTrees2011.pdf

https://www.delphipower.xyz/guide_7/adding_new_application_templates.html Alternatively, you could write a design-time IDE extension implementing IOTAProjectCreator interface.

From the comment about TLine from coreide60.bpl, it might have been Delphi 6. Sorry if it's no longer applicable.

Years ago I wrote the "JEDI Uses Wizard" which scanned compiler messages to "catch" unresolved symbol errors and offer adding appropriate units to the uses clause. With no official OpenTools API available, it had to use a hack to retrieve the compiler output from the message window's treeview. The code is very old and perhaps a bit dangerous (although back then it seemed stable) and I have no idea if it still works today (the IDE internals might have changed). See if it helps you: https://github.com/project-jedi/jcl/blob/master/jcl/experts/useswizard/JCLUsesWizard.pas

There's an option of running WebAssembly via ChakraCore. I've blogged about it here: WebAssembly with Delphi and ChakraCore. There's source code for Delphi 7 or higher and Free Pascal 3.0.4 or higher. It should be possible to use V8 or SpiderMonkey in a similar way. I haven't tried this. I also know of some WebAssembly runtimes like wasmtime and wasmer (these two are both written in Rust) but unfortunately their C-style API is still incomplete (even the API spec itself is still work in progress)...

I've found this way: In the Explorer view, open your working copy file In the File History view, right-click on the first commit in your range, select "Select for Compare". Still in the File History view, right-click on the last commit in your range, select "Compare with Selected"

Recently, I also find GitLens extension for VS Code quite useful.

I find TortoiseGit useful. It's a Windows Explorer extension, similar to TortoiseSVN which you might know already.