Config-driven sessions about tab-rs HOT 5 CLOSED

If each tab ended with a trailing slash, then autocomplete between api/ and api/serve would work nicely.

from tab-rs.

If the list of 'available tabs' was driven by the current directory (by looking for tab.yml up in the dir tree), then the 'command-line-ish' quality of the way tabs are switched would be enhanced.

from tab-rs.

Resolve config by walking the directory tree, up until you find tab.yml.

from tab-rs.

Commands can be 'preloaded' by typing them without a newline at the end.

from tab-rs.

The directory structure provides hierarchy. It also provides a natural way to structure 'level of detail'.

If your workspace contains:

• api/
• frontend/

And your api folder contains:

• api/git/
• api/serve/

The configs could be:

workspace/tab.yml
workspace:
- name: api
  dir: api-server/
- name: frontend

workspace/api-server/tab.yml:
repo:
  - name: git
  - name: serve
    command: cargo run

Workspaces are boundaries. Only the innermost workspace is visible.

Repos are simply folders of tabs, linked to the working directory. Any tab within the workspace is visible, and can be switched to.

from tab-rs.