Open rikedyp opened 2 months ago
Shouldn't there a way to control the log file from the Ride menus?! And to find out where it lives?
I've tried
I've asked John D and he said there's currently no way to make it so dyalog actually truncates the log on their end (so I suppose LOG_SIZE is supposed to limit the file written when ⎕OFF
). If I keep the log file I suffer not just this issue but also #1219. There are some other instances of my session log and input being strange in 19.0 but I haven't found consistent repros for them yet.
Perhaps it is the log of RIDE protocol messages getting long? I'm in a VM so graphical stuff can suffer but VSCode and Firefox are running just fine even with plenty of tabs open and web pages much longer than my session log...
Describe the issue you are having
When I start RIDE with a fresh session log, it is quite responsive both for input and for results being printed to the session from the interpreter. Once I have a few thousand lines of input, I notice both typing and session output becomes sluggish.
Did you connect to an already running interpreter or start the interpreter from Ride?
Start from RIDE
How do you reproduce the issue?
I work around the issue by setting config parameter LOG_FILE_INUSE=0 and restarting RIDE once it becomes slow. I can get to visible slowness by doing
Paste the contents of Help → About (Shift+F1)