helpful VS perspective-el

If you want to programmatically create files, write to them, etc, then read the fine manual, it comes with your Emacs, has index, search and web-like navigation. It is well worth your time investing in looking up the manual, both for Emacs and for Elisp. You access the manual via C-h i. Another good thing to learn how to use is Emacs built-in help. As a minimal basic, C-h f will display information about functions, and C-h v will display the documentation for variables. You can also see where things are declared, open the source code, etc. A good alternative to built-in help is Helpful, which I suggest installing and start using too.

It tweaks Emacs GC. You can run M-x describe-variable while your cursor is at gc-cons-threshold to learn about it. If you opted-in for using "Vim bindings" (Evil mode), you can press K while in normal mode. Note that K doesn't run the describe- command in Doom, but it runs helpful-command from (https://github.com/Wilfred/helpful), which provides more context that describe- commands usually do.

The packages helpful and elisp-demos are super useful because they enhance Emacs' built-in documentation.

You can try to actually use helpful for a while. There was also a package with examples, I don't remember the name, perhaps someone else knows which I mean, that shows usage of a function where available. I remember using it and found it very useful for a while when I was learning elisp more actively. I still use helpful sometimes.

Once you got the hang of keybindings, which-key is a helpful extension (aka package) to Emacs. At this stage, there are other helpful packages and keybindings.

helpful for better help buffers

Since you seem interested, have a look at elisp-demos , too. It works in tandem with helpful.

Elisp Docs are fantastic they have documented everything while with CL most documentation is missing or only on the Web. With Emacs, one need to learn about C-h f (describe-function), C-h k (describe-key), helpful.el and elisp-demos and a new world opens. Terminology is always different, simple example: Microsoft terminology sounds like bullshit, to a Unix person.

Your primary source of knowledge will be the manual and the built-in discoverability (describe-* functions, or helpful) and of course reading the code. I'm not a manual person myself, but Emacs is one of the examples where it is truly excellent and has answers for almost everything.

I opened a ticket https://github.com/nex3/perspective-el/issues/198 but can’t promise to get around to it soon.

I have tried to get this behaviour for a while. The closest I have gotten is using perspective.el, but it ended up being a bit clunky when I tried it like 4 years ago and now I just used bookmark+ which can save/load desktop files as bookmarks.

perspective for named workspaces.

persp-mode?

To scratch a personal itch, I created a little package that integrates perspective-el into the built-in tab-bar.

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 think perspective.el is about what I’m looking for. If you had a list of org-ids, theses could be brought up in indirect buffers, and then those buffers added to the perspective group.

As for why this broke: this change went into Perspective a few weeks after Emacs 28 shipped. You either updated your packages recently after not updating for a while, or you switched to Emacs 28 (or later). Full discussion surrounding this change: https://github.com/nex3/perspective-el/issues/180

It sounds a bit like you want „perspective.el“ (1). It allows you to define „virtual workspaces“ of buffers with individual window layouts. On each virtual desktop the standard buffer list is replaced with a shorter showing only buffers belonging to the current context. I use it every day to keep „code“ buffers separate from my „test“ buffers.

(1) https://github.com/nex3/perspective-el