Merge release-1.2 with master #93
Conversation
I added a new section called _Paste warnings_ with the new settings from this PR: microsoft/terminal#6631. I also added a little bit of explanation about you would want these warnings to be enabled.
These themes are bad, and we feel bad for shipping them. They're still in the code, but by removing them from the docs, hopefully fewer people will make the mistake of using these themes.
Pursuant to microsoft/terminal#6891
Add always on top mode to the keybindings, globals
Add: `toggleRetroEffect`, `renameTab`, `setTabColor`, `openColorPicker`
Remove rowsToScroll from the global settings section
Add settings for paste warnings
Fix up 1.2 release branch
|
Docs Build status updates of commit e87c2a2:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| TerminalDocs/tips-and-tricks.md | View | Details | |
| TerminalDocs/command-line-arguments.md | ✅Succeeded | View | |
| TerminalDocs/customize-settings/color-schemes.md | ✅Succeeded | View | |
| TerminalDocs/customize-settings/global-settings.md | ✅Succeeded | View | |
| TerminalDocs/customize-settings/key-bindings.md | ✅Succeeded | View | |
| TerminalDocs/customize-settings/profile-settings.md | ✅Succeeded | View | |
| TerminalDocs/panes.md | ✅Succeeded | View |
TerminalDocs/tips-and-tricks.md
- Line 31, Column 233: [Warning-file-not-found]
Invalid file link: './customize-settings/profile-settings'. - Line 35, Column 263: [Warning-file-not-found]
Invalid file link: './customize-settings/profile-settings'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching in the Docs contributor and Admin Guide
- See the frequently asked questions
- Post your question in the Docs support channel
Co-authored-by: Kayla Cinnamon <[email protected]>
…s_are_bad Add some notes about the color issues in 1.2
|
Docs Build status updates of commit 521ded6:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| TerminalDocs/tips-and-tricks.md | View | Details | |
| TerminalDocs/command-line-arguments.md | ✅Succeeded | View | |
| TerminalDocs/customize-settings/color-schemes.md | ✅Succeeded | View | |
| TerminalDocs/customize-settings/global-settings.md | ✅Succeeded | View | |
| TerminalDocs/customize-settings/key-bindings.md | ✅Succeeded | View | |
| TerminalDocs/customize-settings/profile-settings.md | ✅Succeeded | View | |
| TerminalDocs/panes.md | ✅Succeeded | View | |
| TerminalDocs/troubleshooting.md | ✅Succeeded | View |
TerminalDocs/tips-and-tricks.md
- Line 31, Column 233: [Warning-file-not-found]
Invalid file link: './customize-settings/profile-settings'. - Line 35, Column 263: [Warning-file-not-found]
Invalid file link: './customize-settings/profile-settings'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching in the Docs contributor and Admin Guide
- See the frequently asked questions
- Post your question in the Docs support channel
No description provided.