rfeynman42B

Seconded (also you can use C-c C-k to quickly do this!). I’ve debugged Emacs startup errors and segfaults from within EXWM many times this way!

Also after a bit more thought I think implementing this would be useful for a totally different purpose: programmatically finding underused keybindings/functions could help a lot with discoverability!

I’ve been daily driving EXWM for about 3 years now and I love it. I haven’t noticed any performance problems and it should work great for just opening the apps you listed.

EXWM being single-threaded (and just being in Emacs) is still somewhat of an issue in that if you’re toying with Emacs and accidentally freeze or crash it, everything else goes down with the ship. It’s not that often of a problem in my experience and I personally find the benefits of EXWM totally outweigh this problem.

From a technical perspective maybe this is achievable through a mix of dribble files (see open-dribble-file) and simple heuristics for guessing which functions are associated with a package (see here maybe?)

I agree with others in that this might be a flawed way of measuring usage, but I think it still would be somewhat interesting to see those stats for fun!

For quick reference here’s the tutorial: https://orgmode.org/worg/org-contrib/babel/intro.html

Once you have it set up you can have Python code in the file like this:

#+begin_src python
# python code here
#+end_src