@nicodebo I think I might have found a way to solve the issue you reported.

The tab-line allows to customize how the list of tabs to display in the tab line is generated. See the "Window Tab Line" manual, which states that

You can customize the variable tab-line-tabs-function to define the preferred contents of the tab line. By default, it displays all buffers previously visited in the window, as described above.

I came up with a function that uses the default behavior (all buffers previously visited in the window), then filters out every buffer that doesn't belong to the current buffer's project (if any).

Here's that function's definition and how to apply it:

(defun project-tab-groups-tab-line-tabs-window-project-buffers ()
  "Return a list of tabs that should be displayed in the tab line.
Same as `tab-line-tabs-window-buffers', but if the current buffer
belongs to a project, all other buffers that don't belong to that
project are filtered out."
  (let ((window-buffers (tab-line-tabs-window-buffers)))
    (if-let* ((pr (project-current))
              (project-buffers (project--buffers-to-kill pr)))
        (seq-filter (lambda (buf) (member buf project-buffers)) window-buffers)
      window-buffers)))

(setq tab-line-tabs-function #'project-tab-groups-tab-line-tabs-window-project-buffers)

Add this snippet to your Emacs config if you want and give it a try yourself.

A quick first test seems promising, but I want to test-drive this for a week or so before I add it to the package, or its README at least.

Note that previous-buffer (C-x left) and next-buffer (C-x right) might behave a little unexpected at the tab line's edges now: they use the unfiltered list of windows, so you can move past the shown tabs in the tab-line, to buffers that don't belong to the project.

Let me know if you find anything that's odd or unexpected. Thanks!

Mixed project buffer in the tabline #1

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions