Closed nathan-rogers closed 1 month ago
Please try this in a freshly started copy of Dyalog.
Yes, I've freshly installed Dyalog version 19, and the above session was performed in a brand new session of Dyalog. I even uninstalled and reinstalled, requiring a reboot of my machine, and ]activate all -reset
then another restart of Dyalog after that
When I first looked at this I overlooked the cause of the problem, sorry: with 19.0 Cider and Tatin are no longer installed into the MyUCMDs\ folder but must be installed into C:\Users\
Please execute this statement:
⍪';'(≠⊆⊢)⎕se.SALT.Settings 'cmddir'
If the MyUCMDs\ folder is on the list and comes before the SessionExtensions\ folder then that explains what you are experiencing: the user command is detected in MyUCMDs\ and SALT (in charge for finding and establishing user commands) won't look any further.
If Cider/Tatin in MyUCMDs\ is a leftover from when you used Cider/Tatin with 18.0 or 18.2, then simply deleting them from the MyUCMDs\ folder will solve the problem.
If you want to use Cider/Tatin with 18.0 or 18.2 as well then please read "6. Updating Tatin" in the InstallingAndUpdatingTheTatinClient document: https://tatin.dev/Assets//docs/InstallingAndUpdatingTheTatinClient.html#updating-tatin
It explains how to make Cider/Tatin available in 18.0 or 18.2 after deleting both from the MyUCMDs\ folder.
I am going to close this issue. If you need further assistance, please communicate with me via kai@aplteam.com
After a fresh
]activate all -reset
, restarting version 19, I run the following user commands:I can
]CiderCreateProject
before I run the updates, but I'm updating because there is a bug in an older version when installing nuget packages. After the update, the user command script seems to be failing here: