[Feature] CLI: arg "add all into one new multibuffer" #372

fzzr commented 2026年07月11日 11:51:56 +02:00

Feature Proposal

I proposing to add new feature and CLI-argument.

Ability to tell CLI to open given specified urls (like file|gram://path:line:row), reusing current window if it exists, into one single multibuffer.

E.g.: gram --multibuffer "gram://foo:42:1" "gram://bar:0:0" to open both foo and bar in the current (reusing latest active or new) a new window, as a single multibuffer with excerpts pointing to specified locations — same as "project search"-multibuffer.

Name of the tab, multibuffer name.
I propose to optionally set name as value for --multibuffer argument:

gram --multibuffer="my name" urls...

This should open urls in a single multibuffer name "my name".

Potential restrictions. It is likely that this feature, when the --multibuffer argument is present, imposes the following restriction on all path arguments passed: the paths must include a location. Otherwise, either the file must not be opened, or (the less desirable option) the default "0:0" will be used as the location.

### Feature Proposal I proposing to add new feature and CLI-argument. Ability to tell CLI to open given specified urls (like `file|gram://path:line:row`), _reusing current window if it exists_, into one single multibuffer. E.g.: `gram --multibuffer "gram://foo:42:1" "gram://bar:0:0"` to open both `foo` and `bar` in the current (_reusing_ latest active or new) a new window, as a single multibuffer with excerpts pointing to specified locations — same as "project search"-multibuffer. Name of the tab, multibuffer name. I propose to optionally set `name` as value for `--multibuffer` argument: ```sh gram --multibuffer="my name" urls... ``` This should open urls in a single multibuffer name "my name". Potential restrictions. It is likely that this feature, when the `--multibuffer` argument is present, imposes the following restriction on all path arguments passed: the __paths must include a location__. Otherwise, either the file must not be opened, or (the less desirable option) the default "0:0" will be used as the location.

krig commented 2026年07月12日 10:30:09 +02:00

It sounds like a great feature but I need to take a look at the support that is already there.. I've only ever used the command line to open single files or projects, but from the code I know there is some complex logic around opening multiple files and workspaces. Maybe a simpler default behaviour more like what you suggest would be a nice solution..

It sounds like a great feature but I need to take a look at the support that is already there.. I've only ever used the command line to open single files or projects, but from the code I know there is some complex logic around opening multiple files and workspaces. Maybe a simpler default behaviour more like what you suggest would be a nice solution..