From: Peter G. <pe...@ar...> - 2003-05-19 15:48:17
|
This morning's development snapshot (j 0.18.1.15, lisp 0.0.0.30) is up: http://armedbear.org/j.zip (source) http://armedbear.org/j-jar.zip (just j.jar) This snapshot should fix ssh directory buffers to work on systems where the output of "ls -la" is not in English. In previous versions, j was looking for a line starting with "total " to detect the start of the directory listing. On a German system, however, what you get is "insgesamt 16" rather than "total 16", so now j looks for a regular expression that matches any non-numeric text, rather than just the bare string "total ". Investigation of this problem also revealed that using Ctrl W to close the initial transcript buffer when the failure occurred led not to the graceful recovery I had expected but rather to a complete hang. This was a totally separate problem, and it too is now fixed. For a long time, both of the known users of the edit-remote-files-via- ssh feature have been plagued by the following disconcerting message in their logs on an intermittent basis: BUG! SshSession.cleanup session is not in use but still locked I've finally tracked this problem down: killBuffer() was eventually calling SshSession.cleanup() in a situation where the buffer was no longer in the buffer list (hence the session was no longer in use), but the call sometimes occurred before the background thread that was using the session had a chance to unlock it. To resolve this, killBuffer() no longer calls SshSession.cleanup(). Now, when the user first opens an ssh buffer, j starts a background cleanup thread. This thread checks on things once a minute, cleaning up idle sessions as it deems fit, and then, when the session count goes to zero, the cleanup thread exits. There are no longer any timing issues, since the cleanup thread simply keeps working as long as any sessions are locked or in use. The same approach is now also used to clean up FTP sessions. This snapshot also features a number of improvements to the Java debugger (Alt X, "jdb") and the documentation thereof. Among other things, the control dialog toolbar layout has changed, and there are now useful jdb-related items (including "Run to current line") on the right-button context menu in Java mode buffers when the debugger is active. The tbreak command is now implemented as advertised. Thanks for your support. -Peter |