treemacs VS emacs-buttercup

Im trying to find any, but everything I have is https://github.com/Alexander-Miller/treemacs and https://github.com/alphapapa/org-sidebar which is not what im looking for. Please help!

I found the solution on Treemacs github https://github.com/Alexander-Miller/treemacs/issues/610

But I'm rethinking about my approach, as tab-bar-mode would give me nice visual help (#3), and it seems difficult to recover a perspective using perspective, and persp-mode may be a better fit in that sense (#4). The Treemacs integration isn't working for me either, and I get the same list of file trees for all perspectives -- I'm pretty sure I'm doing something stupid, but this was handled nicely with Doom Emacs's workspace support (#5). But perspective seems to work best for segregated buffer list (#1).

I'm not sure if it is possible. Have you tried it using one of the configuration variables (see the github-page), for example treemacs-default-visit-action ? Maybe you find some help in closed or open issues.

I've not used Sublime Text, but I think treemacs fits what you are looking for

https://github.com/Alexander-Miller/treemacs

For table of content you can use treemacs. It's a very capable package and can do much more, especially for code projects.

On Treemacs' github repository, there is a description:

Update treemacs. Treemacs used the deprecated make-obsolete interface in versions before January 2021; as Emacs 28 made the new interface mandatory (the old one had been deprecated since like Emacs 23), older versions no longer work in Emacs 28.

ERT doesn't have much to help with this, but Buttercup has a number of facilities to help with controlling the environment around each test: https://github.com/jorgenschaefer/emacs-buttercup/

> (For example, when trying to test things out I haven't really found a way much better than typing into scratch, selecting code and running it while staring at messages....)

Are you talking about when you're noodling, trying to figure how things work, or actually trying to build something?

For playing around, I found that scratch works ok, but I found a better workflow.

I end up using a daily note in org-roam, with #begin_src elisp... I then tag the heading with :REFILE:ELISP: so I can always find it later. Basically evaluate everything inline within that org-babel block.

When I'm building something, or driving towards a specific goal, I use buttercup [0] to write actual unit tests. If I squint, it kinda looks like TDD.

Finally, for debugging of running elisp, take a look at edebug [1]. It's a pretty standard looking debugger (if you used something like gdb). By default emacs uses debug which is not as friendly.

[0]: https://github.com/jorgenschaefer/emacs-buttercup

[1]: https://www.gnu.org/software/emacs/manual/html_node/elisp/Ed...

Ok, before posting this I looked up a bit and found this and this. Buttercup seems great. Links or tips from experienced developers are welcome.