this post was submitted on 22 Nov 2023
1 points (100.0% liked)

Emacs

311 readers
1 users here now

A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!

Get Emacs

Rules

  1. Posts should be emacs related
  2. Be kind please
  3. Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.

Emacs Resources

Emacs Tutorials

Useful Emacs configuration files and distributions

Quick pain-saver tip

founded 1 year ago
MODERATORS
rglullis@communick.news
raphael@communick.news
1
What to use for "Context Management"? (alien.top)
submitted 11 months ago by domsch1988@alien.top to c/emacs@communick.news
5 comments fedilink hide all child comments
 

I'll try to explain what i'm looking for: Let's say i'm working on a work project, on my emacs configuration and my org notes. All of those i'll use throughout the day but don't do simultaneosly. I'm trying to set it up so i can save the current state for buffers and open project for work, switch to my org notes, do something there, and switch back with all buffers in place and files open where they where.

Things like desktop-save-mode seem to handle restoring the last buffers, but aren't working for multiple sessions. So what's my best bet to have multiple separated "setups" depending on what i'm working on at the moment?

you are viewing a single comment's thread
view the rest of the comments
[–] github-alphapapa@alien.top 1 points 11 months ago (2 children)

https://github.com/alphapapa/burly.el: Expressly designed to solve this problem. Use with tab-bar-mode and burly-tabs-mode.

See also: https://github.com/alphapapa/bufler.el with bufler-workspace commands.

[–] domsch1988@alien.top 1 points 11 months ago (1 children)

Burly looks nice. But in my first use i ran into this bug https://github.com/alphapapa/burly.el/issues/28 So, that's not usable for me, sadly.

[–] github-alphapapa@alien.top 1 points 11 months ago

Please read that issue and post a reply to it with the version of Emacs you're using and the backtrace. And please test the branch in the comment that may fix the problem. As you can see, it's been several months since anyone provided feedback, so the fix may already be available, but it needs user confirmation.