VS Code global configuration, instead of configuration file per project

[pauloendoh]

Please describe feature/problem details and solution you'd like. I don't want to have a sessions.json file in each of my projects just to set up my terminals, specially for work related projects. Would it be possible to attach these configurations to the user settings (JSON) instead?

Describe alternatives you've considered Terminal keeper adds commands to the command palette, but does not add any configurable settings in the user settings JSON.

[johurul-haque]

I would love to see this. I want to add some suggestions:

• If there's no sessions.json file, activating the terminal session would use the globally defined configurations.
• If there is a sessions.json it'll use that instead of the global configurations.
• And for the case where both of them are not defined activating the terminal session will create a sessions.json file (which is the current behavior).

[nguyenngoclongdev]

@johurul-haque Thank you for the excellent suggestions. I appreciate you taking the time to provide this constructive feedback. I will work on reviewing and releasing an update with these improvements soon. Please let me know if you have any other suggestions.

[nguyenngoclongdev]

@pauloendoh @johurul-haque

In the latest update (v1.1.23), we’ve introduced the ability to set some information in the VSCode settings, such as:

{
  "terminal-keeper.active": "default",
  "terminal-keeper.theme": "chaos",
  "terminal-keeper.noClear": false,
  "terminal-keeper.keepExistingTerminals": false,
  "terminal-keeper.activateOnStartup": false
}

However, we’ve decided to keep the sessions.json file because the terminal setting information can be quite large and complex. Additionally, having a separate file allows us to validate the content and support code suggestions based on the JSON schema. Therefore, we believe it’s better to have a dedicated place for this information.

We hope this answers your questions! Thank you!