bmag

You should use `purpose-action-function-ignore-buffer-names`. You can see an example in [window-purpose-fixes.el#L159](https://github.com/bmag/emacs-purpose/blob/master/window-purpose-fixes.el#L159): ```elisp (add-to-list 'purpose-action-function-ignore-buffer-names "^ \\*LV\\*$") ``` Please tell me if this solves the problem: ```elisp (add-to-list 'purpose-action-function-ignore-buffer-names "\\*org-roam\\*") ```

Thanks, I reviewed the PR and submitted feedback. As I suggested in the issue report, please implement the change as a **new** extension, and don't change code1 itself. Copy code1...

> Oh yes, sorry forgot to ask you: what do you mean by "add code2" instead of "changing code1" ? Are you talking about adding separated vars, etc with code2...

Any news?

@sergeyglazyrindev It's ok, I understand, hope you're all better now and wish you the best. As for this PR, I'm very busy myself this month, so it will take me...

Hey, sorry for the late response, I was really busy and turns out "end of February" wasn't the worst case :frowning_face: I know putting together this PR is a considerable...

Hi @ville-h, thanks for the report. Not sure if it's still relevant to you, but as far as I can tell, the problem isn't actually in `purpose-load-window-layout-file`. What I assume...

Another pro: the docstring of `display-buffer-overriding-action` was changed in 26.2 to say specifically that it should *not* be changed permanently by elisp programs. Meaning, Purpose is doing something that contradicts...

I actually started implementing some of it in `base-action` branch, that is based on `develop` branch. The `develop` branch was meant to become version 2.0 of Purpose, but that work...

Thanks for posting this issue, I didn't know about that virtual frame. I would appreciate a PR, but as you noticed I'm not very active so it could take some...