tabby-eternal-terminal 1.0.0 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +18 -9
  2. package/dist/index.js +1511 -827
  3. package/package.json +54 -29
package/README.md CHANGED
@@ -29,12 +29,21 @@ Key design decisions:
29
29
 
30
30
  ## Compatibility
31
31
 
32
- This plugin requires Tabby with the small SSH API changes in PR#11649.
33
- That PR/branch exports `SSHSession` and its keyboard interactive
34
- prompt, makes the prompt component available to plugins, and adds
35
- `SSHSession.openExecChannel()`. A stock Tabby release will not load
36
- the plugin correctly until those changes are accepted and released
37
- upstream.
32
+ This plugin needs a Tabby with the small SSH API changes in
33
+ [Tabby PR #11649](https://github.com/Eugeny/tabby/pull/11649). The PR
34
+ exports `SSHSession` and its keyboard-interactive prompt, makes the
35
+ prompt component available to plugins, and adds
36
+ `SSHSession.openExecChannel()`: 17 added lines in two files. Released
37
+ Tabby does not have them yet.
38
+
39
+ The plugin checks for them each time Tabby starts. On a Tabby without
40
+ them it still installs, but it says so when Tabby starts, in
41
+ **Settings → Eternal Terminal**, and in any Eternal Terminal tab, and
42
+ it does not try to connect.
43
+ [Getting a Tabby that can run Eternal Terminal](docs/tabby-support.md)
44
+ takes you through building one, step by step, and shows how to check
45
+ the change yourself first. Once a Tabby release includes the change,
46
+ update Tabby and the warning goes away.
38
47
 
39
48
  The ET server host must have `etserver` and `etterminal` installed. The plugin uses Tabby's SSH connection to start `etterminal`; it does not invoke a local ET binary.
40
49
 
@@ -49,9 +58,9 @@ connection type.
49
58
  You need a Tabby build with the SSH API changes described under
50
59
  [Compatibility](#compatibility), for example one built from the
51
60
  [`tabby-et-ssh-support`](https://github.com/qoke/tabby/tree/tabby-et-ssh-support)
52
- branch of `qoke/tabby`. A stock Tabby release will install the plugin
53
- but will not load it correctly. This requirement goes away once those
54
- changes are released in mainstream Tabby.
61
+ branch of `qoke/tabby`. [The setup guide](docs/tabby-support.md) shows
62
+ how. A released Tabby installs the plugin, but the plugin cannot open
63
+ connections there and says so.
55
64
 
56
65
  ### From inside Tabby
57
66