Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing core features (or their doc) #4511

Closed
sytelus opened this issue Feb 8, 2020 · 3 comments
Closed

Missing core features (or their doc) #4511

sytelus opened this issue Feb 8, 2020 · 3 comments
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Question For questions or discussion Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered

Comments

@sytelus
Copy link

sytelus commented Feb 8, 2020

I am a heavy user of conEmu on WIndows as well Terminator on Linux and came to this repo with high hopes but there seems to be many missing features. To remain fair to other terminals, I expected to find this basic information in Readme but I couldn't so I assume these are the missing features.

  1. How do I divide the window into multiple sizable terminals (aka layout)? There is nothing in readme and nothing in UX to know if this core feature exists.
  2. What are all the settings available? Again nothing in the readme or in UX. When I click settings in UX, it opens up settings file buried in non-user folder with very few settings without much comments. I would highly recommend yaml for self-documenting settings file. Also, settings file should reside in user folder as .windows-terminal.config or something like that and employ VSCode like override mechanism.
  3. How do I make it rto emember my session? Everytime I reopen Terminal, it starts new PowerShell (which I don't use).
  4. How do I set working directories and commands for each terminal (in tab or layput)? Again nothing in readme or UX to make this intuitive (if feature already exists).

I feel above 4 are the core features before leaning on Windows Terminal full time.

Thank you for this effort and hope this can be equivalent of Terminator on Linux (not the most self-explanatory UX but I still can figure out the above features :)).

@sytelus sytelus added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Feb 8, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 8, 2020
@sytelus sytelus changed the title Too many missing core features Missing core features (or their doc) Feb 8, 2020
@awgv
Copy link

awgv commented Feb 9, 2020

Hello @sytelus, hopefully, this will be useful.

  1. How do I divide the window into multiple sizable terminals (aka layout)? There is nothing in readme and nothing in UX to know if this core feature exists.

Panes are possible, here’re the related keyboard shortcuts:

{ "command": { "action": "splitPane", "split": "horizontal"}, "keys": [ "alt+shift+-" ] },
{ "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift+plus" ] },

{ "command": { "action": "resizePane", "direction": "down" }, "keys": [ "alt+shift+down" ] },
{ "command": { "action": "resizePane", "direction": "left" }, "keys": [ "alt+shift+left" ] },
{ "command": { "action": "resizePane", "direction": "right" }, "keys": [ "alt+shift+right" ] },
{ "command": { "action": "resizePane", "direction": "up" }, "keys": [ "alt+shift+up" ] },

{ "command": { "action": "moveFocus", "direction": "down" }, "keys": [ "alt+down" ] },
{ "command": { "action": "moveFocus", "direction": "left" }, "keys": [ "alt+left" ] },
{ "command": { "action": "moveFocus", "direction": "right" }, "keys": [ "alt+right" ] },
{ "command": { "action": "moveFocus", "direction": "up" }, "keys": [ "alt+up" ] },

I agree it would be nice to have a dedicated settings UI, but considering the fact that technical people are used to working with text files, I also think that the lack of it shouldn’t be a huge issue.

  1. What are all the settings available? Again nothing in the readme or in UX. When I click settings in UX, it opens up settings file buried in non-user folder with very few settings without much comments. I would highly recommend yaml for self-documenting settings file. Also, settings file should reside in user folder as .windows-terminal.config or something like that and employ VSCode like override mechanism.

The topmost comment in profiles.json—that’s the one you open from the UI—mentions it:

// To view the default settings, hold "alt" while clicking on the "Settings" button.

This opens the file I linked above, and it shows all settings that can be changed. Since the terminal is in development and is several months from hitting v1.0, you might need to follow the development and occasionally delete profiles.json to recreate it with settings that were missing. Also, VSCode shows settings’ descriptions in profiles.json when a setting is hovered.

  1. How do I make it rto emember my session? Everytime I reopen Terminal, it starts new PowerShell (which I don't use).

Set this in your settings (if I’m not mistaken, can be a profile’s name, guid, or index):

"defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",

  1. How do I set working directories and commands for each terminal (in tab or layput)? Again nothing in readme or UX to make this intuitive (if feature already exists).

Should be set for each profile:

"startingDirectory": "%USERPROFILE%",

Panes also use this setting, and I don’t think this behavior can be changed right now.

In any case, if all is well, v1.0 should be released in April.

@j4james
Copy link
Collaborator

j4james commented Feb 9, 2020

FYI, you can find documentation on most of these features here:
https://github.com/microsoft/terminal/tree/master/doc/user-docs

@zadjii-msft
Copy link
Member

I'm pretty sure @Banandrew has done an excellent job answering this question. I couldn't have said it better myself :)

@sytelus if you have any further questions, I'd be happy to help point you in the right direction.

@zadjii-msft zadjii-msft added Area-Settings Issues related to settings and customizability, for console or terminal Issue-Question For questions or discussion Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered and removed Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. labels Feb 10, 2020
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Feb 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Question For questions or discussion Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered
Projects
None yet
Development

No branches or pull requests

4 participants