For today, just want to share a piece of the new structure: clawe.debug/ls and clawe.debug/ls-print.

When debugging clawe, especially clawe's toggle feature, I often need to get a look at the workspaces and clients that are currently running - specifically the names, window titles, class names, etc, which are used to match with client/workspace definitions. When you invoke toggle for "spotify", clawe determines the current need. Are we already focusing spotify? Does the client exist in a different workspace? When this goes wrong, we need to figure out why.

The debug namespace is a quick way to list the clients or workspaces that clawe knows about - (clawe.debug/ls {:type :clients}) in a repl is simple and quite useful.

But sometimes you're not in a clojure repl, or you want to know what a fresh invokation of clawe would see. Maybe the repl state has some advantage or difference from the actual toggle invokation that your keybinding is sending.

> This is especially true for clawe, as I like to develop it against the > fully-featured jvm cider repl (against doctor 's backend server) rather than a > basic bb-repl. This supports extremely useful features like cider-inspect, > and makes clojure development a real joy.

> alias clawebb='bb --config ~/russmatney/clawe/bb.edn'
> clawebb -x clawe.debug/ls-print --type :clients

|           :client/window-title | :client/app-name |
|--------------------------------+------------------|
|                          clawe |        alacritty |
|                          clawe |            emacs |
|                           dino |            emacs |
|                       dotfiles |            emacs |
|            tauri-doctor-topbar |            clove |
|                        journal |            emacs |
|             slack | clojurians |            slack |
|                        spotify |          spotify |
| babashka/cli — mozilla firefox |          firefox |

There we are! We can see that the spotify client is found and properly labelled.

Note that here we're calling ls-print instead, which is a simple wrapper that passes the ls results to clojure.pprint/print-table.

(ns notebooks.tmux
  {:nextjournal.clerk/visibility {:code :hide :result :show}}
  (:require
   [clawe.debug :as debug]
   [nextjournal.clerk :as clerk]))

;; ### tmux sessions
^::clerk/no-cache
(clerk/table (debug/ls {:type :tmux}))

;; ### tmux panes
^::clerk/no-cache
(clerk/table (debug/ls {:type :tmux-panes}))

Another piece of the clawe refactor: Clawe now invokes its keybindings by default with -x.

;; from clawe/defs/bindings.clj
(defkbd toggle-terminal
  [[:mod] "Return"]
  (sxhkd-exec "bb --config ~/russmatney/clawe/bb.edn -x clawe.toggle/toggle --key terminal"))

(defkbd toggle-emacs
  [[:mod :shift] "Return"]
  (sxhkd-exec "bb --config ~/russmatney/clawe/bb.edn -x clawe.toggle/toggle --key emacs"))

(defkbd toggle-workspace-journal
  [[:mod] "u"]
  (sxhkd-exec "bb --config ~/russmatney/clawe/bb.edn -x clawe.toggle/toggle --key journal"))

(defkbd toggle-workspace-web
  [[:mod] "t"]
  (sxhkd-exec "bb --config ~/russmatney/clawe/bb.edn -x clawe.toggle/toggle --key web"))

Prior to this, I was using a defthing macro to register commands, and invoking them by passing the name into clawe's main function.

bb --config ~/russmatney/clawe/bb.edn -x clawe.toggle/toggle --key journal

This ends up being more performant as well - there's no need to require every namespace in clawe to call one command. When invoked via -x, only the required namespaces are loaded, so we get to the good bits right away.

For more on Clawe's features and design journey, check out the clawe workspace note.

A full-stack clojure app with deep tooling integrations.

Presents window management ui components (doctor-topbar) as well as a native or browser-based web app.

A feature of Doctor.

Intended as a workspaces-widget replacement.

Your workspaces and the apps they are responsible for.

Shows all the open workspaces, the active workspaces, the recently deleted ones. The amount of visible information is toggleable (modes, cycling levels of detail ).

The apps that are open (or could be opened) in those workspace and their statuses/urgencies/health-checks should be visible as well.

So you want to create a quick native dashboard. You know enough web dev to be dangerous, and now you're hoping to create something useful that isn't stuck in one of your browser tabs.

Here I'll touch on the path I took through Electron that eventually lead to Tauri, then include links to the way I'm currently using Tauri in Clawe.

aka status check.

i (of course) blew it out into an unfinishable doctor dashboards 'project'. (feel the disdain in those words)

nothing like an overengineered doctor.

A video overview of the components that make up the clawe monorepo.

Relevant April 2023.

I'll post a link here once it exists! For now, if you're reading this, I could stream this any day, so take a look at my schedule or ping me to see when it's going to happen.