
Another example would be - I work on multiple projects and always use my "main" frame for it. Other times I just use my org tab to determine the next task and/or set a note to it, so switching tab within the current frame would be more suitable. Sometimes when I do a lot of work in org mode, I would dedicate a whole monitor (Qtile workspace) to it. I would much rather maintain just one set of tabs, make Emacs frame for (almost) every Qtile workspace, and then just pick what I want to see and where. In my opinion, having one set of tabs per frame is an overkill. I am probably the only weirdo wanting this but would it be possible to share one set of tabs accross all Emacs frames? Hello u/daviwil, thank you for this great video. In general I really have to nail down better behavior for how Emacs chooses windows to display buffers, splitting or otherwise. That it happens is quite understandable, but is this something you've worked around, or can think of a workaround for? Some sort of way a buffer switch can happen virtually, within an undisplayed tab workspace? It was one benefit of exwm workspaces over tab workspaces, that what happens in a workspace stays in a workspace. Zoom is a PITA in general with its many windows, and it creates windows when a meeting ends, that just sprayed themselves all over the workspace I was working in (when I was largely ignoring a company-wide meeting). I've had other-workspace flycheck warning buffers throw themselves at me. Right now the stand-out problem is when something autonomously switches buffers they'll come to the current workspace. I like a bunch of things about it, not least switch-by-name and the more dynamic nature of the workspace list, but there are issues. Your post prompted me to explore and set up tab-bar workspaces instead of exwm workspaces. (if explicit-name tab-name (+ 1 tab-index))))))) (tab-name (alist-get 'name current-tab))) (explicit-name (alist-get 'explicit-name current-tab)) (let* ((current-tab (tab-bar-current-tab)) (if (< 0 (length tag)) tag (int-to-string num)))) (tag (nth 2 (assoc num (eyebrowse-get 'window-configs))))) (assq-delete-all 'eyebrowse-mode mode-line-misc-info) (< 1 (length (eyebrowse-get 'window-configs)))) Requires `eyebrowse-mode' or `tab-bar-mode' to be enabled." (doom-modeline-def-segment workspace-name Hi, thank you for the video (right after we talked about tab-bar-mode last time !) You mentioned that the current workspace is absent from doom-modeline once tab-bar-mode is deactivated, you can show it by redefining the corresponding segment: redefing segment to show workspace even when tab-bar-mode is disabled
