diff options
| author | har7an <99636919+har7an@users.noreply.github.com> | 2022-10-13 08:17:54 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-13 08:17:54 +0000 |
| commit | 8d56def4fc3441b7231eda8c2ca944445af43920 (patch) | |
| tree | 7e2a9d769bacb240ad136a4dddbc9cb472ffb8a6 /default-plugins | |
| parent | docs(changelog): session-name cli fix (diff) | |
| download | sl0ppij-8d56def4fc3441b7231eda8c2ca944445af43920.tar.gz sl0ppij-8d56def4fc3441b7231eda8c2ca944445af43920.tar.xz sl0ppij-8d56def4fc3441b7231eda8c2ca944445af43920.zip | |
zellij/commands: Prevent recursive sessions (#1766)
* zellij/commands: Prevent recursive sessions
with session names specified in layout files. A "recursive session" is
created when, while running inside some zellij session, a user attempts
to spawn zellij and make it attach to that same session.
When attaching via CLI (`zellij attach`) we explicitly check for this
condition and error out when needed.
However, besides `zellij attach` it is also possible to declare the
session to attach to in layout files like so:
```yaml
session:
name: "foo"
```
This takes a different codepath when starting zellij, and hence bypases
the checks we already have in place to avoid recursive sessions. Hence,
we implement the check in the other codepath, too, and prevent recursive
sessions from happening for good.
Fixes: #1735
* changelog: fix recursive zellij sessions
Diffstat (limited to 'default-plugins')
0 files changed, 0 insertions, 0 deletions
