Process Manager Utility

[ethanxxxl]

When I am using/hacking lem I often spawn a lot of threads/processes that end up getting lost and just run in the backgound, eating up resources or creating undesirable effects. I created this command that I put in my config that pulls up a list of all the threads and allows you to terminate them by clicking on them, I find it very handy and use it often:

(defpackage :es-process-manager
  (:use :cl :lem-user))

(in-package :es-process-manager)

(defun display-processes ()
  (let* ((buf (lem:make-buffer "*process-list*" :enable-undo-p nil :read-only-p nil))
        (windows (lem:get-buffer-windows buf)))

    ;; open up a buffer to put the thread list in.
    (if windows
        (lem:switch-to-window (first windows))
        (progn 
          (lem:split-window-horizontally (lem:current-window))
          (lem:switch-to-buffer buf)))

    ;; put the information into the buffer.
    (lem:with-current-buffer buf
      (when (lem:buffer-read-only-p buf)
        (lem:toggle-read-only))
      
      (lem:erase-buffer buf)
      (loop :for thread :in (sb-thread:list-all-threads)
            :do (let ((name (sb-thread:thread-name thread)))
                  (lem/button:insert-button (lem:current-point)
                                            (format nil "~A" name)
                                            (lambda ()
                                              (let ((t thread))
                                                (when (lem:prompt-for-y-or-n-p (format nil "kill thread ~S? " name))
                                                  (sb-thread:terminate-thread t)
                                                  (display-processes)))))
                  (lem:insert-character (lem:current-point) #\Newline)))
      
      (lem:toggle-read-only))))

(lem:define-command process-manager () ()
  (display-processes))

(lem:define-key lem:*global-keymap* "F1" 'process-manager)

note, there seems to be a bug where the buttons always delete the last thread in the list, it seems like the lambdas aren't retaining the thread they were created with.

also note, this is not suitable to be merged into lem, as it is relient on sbcl specifically.

[vindarel]

That looks good! I'll have to try.

sbcl only

just use… bordeaux-threads? It has the same function names than sb-thread: bt:list-all-threads, bt:thread-name, bt:terminate-thread.