Skip to content

Conversation

@alexmohr
Copy link

@alexmohr alexmohr commented Nov 11, 2025

Overview

Added a new configuration option to display workspace numbers instead of window layout previews in the menu bar.

Configuration

Add the following to your ~/.config/rift/config.toml:

[settings.ui.menu_bar]
enabled = true
show_workspace_numbers = true

Options

  • show_workspace_numbers = false (default): Shows the traditional window layout preview
  • show_workspace_numbers = true: Shows the workspace number (1-based) instead

This option can be combined with:

  • show_empty = false (default): Only shows workspaces with windows
  • show_empty = true: Shows all workspaces including empty ones

Example:
image

Notes

In contrast to other WMs like i3, hyprland etc, this will only show the workspace if at least one window exists or show_empty is set. This means switching to an empty workspace does not show the number yet, which is okay from my point of view.

@brianwk
Copy link

brianwk commented Nov 11, 2025

Maybe the workspace number starting at 0 or 1 should be configurable. For example, I use workspace 0 as I have 10 virtual work spaces configured.

Overview
Added a new configuration option to display workspace numbers instead of window layout previews in the menu bar.

Configuration

Add the following to your `~/.config/rift/config.toml`:

```toml
[settings.ui.menu_bar]
enabled = true
show_workspace_numbers = true
```

Options

- `show_workspace_numbers = false` (default): Shows the traditional window layout preview
- `show_workspace_numbers = true`: Shows the workspace number (1-based) instead

This option can be combined with:
- `show_empty = false` (default): Only shows workspaces with windows
- `show_empty = true`: Shows all workspaces including empty ones
@alexmohr
Copy link
Author

Maybe the workspace number starting at 0 or 1 should be configurable. For example, I use workspace 0 as I have 10 virtual work spaces configured.

Sure, I'm using 10 workspaces too, but with my keybindings starting at 1 makes more sense. I'll add another confguration key.

@acsandmann
Copy link
Owner

acsandmann commented Nov 11, 2025

so whilst this change is very welcome this pr cannot be merged in its current state. Rift uses the up to date objc2* family of macos bindings so we should aim to use those instead of core-foundation, core-graphics and so forth.

there are also a lot of unnecessary comments that i would rather not have in rifts codebase.

@alexmohr
Copy link
Author

alexmohr commented Nov 12, 2025

Closing this for now. I will reopen it if and when I find the time to try again without adding new dependencies

@alexmohr alexmohr closed this Nov 12, 2025
@acsandmann
Copy link
Owner

Closing this for now. I will reopen it if and when I find the time to try again without adding new dependencies

it should be relatively trivial since the crates you added are doing basically the same thing as the objc2* crates. just a simple translation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants