Migrate spelling-0.0.19 changes from main

.github/actions/spelling/advice.md

@@ -1,3 +1,4 @@
+<!-- markdownlint-disable MD033 MD041 -->
 <details>
 <summary>
 :pencil2: Contributor please read this
@@ -8,9 +9,10 @@ By default the command suggestion will generate a file named based on your commi
 :warning: The command is written for posix shells. You can copy the contents of each `perl` command excluding the outer `'` marks and dropping any `'"`/`"'` quotation mark pairs into a file and then run `perl file.pl` from the root of the repository to run the code. Alternatively, you can manually insert the items...
 
 If the listed items are:
+
 * ... **misspelled**, then please *correct* them instead of using the command.
-* ... *names*, please add them to `.github/actions/spelling/dictionary/names.txt`.
-* ... APIs, you can add them to a file in `.github/actions/spelling/dictionary/`.
+* ... *names*, please add them to `.github/actions/spelling/allow/names.txt`.
+* ... APIs, you can add them to a file in `.github/actions/spelling/allow/`.
 * ... just things you're using, please add them to an appropriate file in `.github/actions/spelling/expect/`.
 * ... tokens you only need in one place and shouldn't *generally be used*, you can add an item in an appropriate file in `.github/actions/spelling/patterns/`.
 
@@ -18,10 +20,31 @@ See the `README.md` in each directory for more information.
 
 :microscope: You can test your commits **without** *appending* to a PR by creating a new branch with that extra change and pushing it to your fork. The [check-spelling](https://github.com/marketplace/actions/check-spelling) action will run in response to your **push** -- it doesn't require an open pull request. By using such a branch, you can limit the number of typos your peers see you make. :wink:
 
-:clamp: If you see a bunch of garbage and it relates to a binary-ish string, please add a file path to the `.github/actions/spelling/excludes.txt` file instead of just accepting the garbage.
+<details><summary>:clamp: If you see a bunch of garbage</summary>
+
+If it relates to a ...
+<details><summary>well-formed pattern</summary>
+
+See if there's a [pattern](https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples:-patterns) that would match it.
+
+If not, try writing one and adding it to a `patterns/{file}.txt`.
+
+Patterns are Perl 5 Regular Expressions - you can [test](
+https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your lines.
+
+Note that patterns can't match multiline strings.
+</details>
+<details><summary>binary-ish string</summary>
+
+Please add a file path to the `excludes.txt` file instead of just accepting the garbage.
 
 File paths are Perl 5 Regular Expressions - you can [test](
 https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your files.
 
-`^` refers to the file's path from the root of the repository, so `^README\.md$` would exclude [README.md](https://github.com/microsoft/terminal/blob/main/README.md) (on whichever branch you're using).
+`^` refers to the file's path from the root of the repository, so `^README\.md$` would exclude [README.md](
+../tree/HEAD/README.md) (on whichever branch you're using).
+</details>
+
+</details>
+
 </details>

.github/actions/spelling/allow/README.md

@@ -1,4 +1,4 @@
-# Dictionaries are lists of words to accept unconditionally
+# Allow files are lists of words to accept unconditionally
 
 While check spelling will complain about an expected word
 which is no longer present, you can include things here even if
@@ -8,11 +8,11 @@ E.g., you could include a list of system APIs here, or potential
 contributors (so that if a future commit includes their name,
 it'll be accepted).
 
-### Files
+## Files
 
 | File | Description |
 | ---- | ----------- |
-| [Dictionary](dictionary.txt) | Primary US English dictionary |
+| [Allow](allow.txt) | Supplements to the dictionary |
 | [Chinese](chinese.txt) | Chinese words |
 | [Japanese](japanese.txt) | Japanese words |
 | [Microsoft](microsoft.txt) | Microsoft brand items |

.github/actions/spelling/allow/allow.txt

@@ -0,0 +1,77 @@
+apc
+calt
+ccmp
+changelog
+cybersecurity
+Apc
+clickable
+clig
+copyable
+dalet
+dcs
+Dcs
+dialytika
+dje
+downside
+downsides
+dze
+dzhe
+Enum'd
+Fitt
+formattings
+ftp
+fvar
+geeksforgeeks
+ghe
+gje
+hostname
+hostnames
+hyperlink
+hyperlinking
+hyperlinks
+img
+It'd
+kje
+liga
+lje
+locl
+lorem
+Llast
+Lmid
+Lorigin
+maxed
+mkmk
+mru
+noreply
+nje
+ogonek
+ok'd
+overlined
+postmodern
+ptys
+qof
+qps
+rclt
+reimplementation
+reserialization
+reserialize
+reserializes
+rlig
+runtimes
+shcha
+slnt
+Sos
+timestamped
+TLDR
+tokenizes
+tonos
+tshe
+uiatextrange
+UIs
+und
+unregister
+versioned
+We'd
+wildcards
+yeru
+zhe

.github/actions/spelling/allow/apis.txt

@@ -1,19 +1,38 @@
 ACCEPTFILES
 ACCESSDENIED
+alignas
 alignof
+APPLYTOSUBMENUS
 bitfield
 bitfields
+BUILDBRANCH
+BUILDMSG
+BUILDNUMBER
+BYPOSITION
+charconv
 CLASSNOTAVAILABLE
 cmdletbinding
 COLORPROPERTY
+colspan
+COMDLG
+comparand
+cstdint
 CXICON
 CYICON
-D2DERR_SHADER_COMPILE_FAILED
 dataobject
+dcomp
 DERR
+dlldata
+DONTADDTORECENT
+DWORDLONG
+enumset
 environstrings
 EXPCMDFLAGS
 EXPCMDSTATE
+filetime
+FILTERSPEC
+FORCEFILESYSTEM
+FORCEMINIMIZE
 frac
 fullkbd
 futex
@@ -22,90 +41,154 @@ GETHIGHCONTRAST
 Hashtable
 HIGHCONTRASTON
 HIGHCONTRASTW
+hotkeys
 href
+hrgn
+IActivation
 IApp
 IAppearance
 IAsync
 IBind
 IBox
 IClass
-IConnection
 IComparable
+IComparer
+IConnection
 ICustom
 IDialog
 IDirect
 IExplorer
+IFACEMETHOD
+IFile
 IInheritable
 IMap
 IObject
+iosfwd
 IPackage
 IPeasant
+isspace
+ISetup
 IStorage
+istream
 IStringable
 ITab
 ITaskbar
+IUri
 IVirtual
+KEYSELECT
 LCID
 llabs
 llu
 localtime
 lround
 LSHIFT
-MULTIPLEUSE
+MENUCOMMAND
+MENUDATA
+MENUINFO
+memicmp
+mptt
+mov
 msappx
 MULTIPLEUSE
 NCHITTEST
 NCLBUTTONDBLCLK
 NCRBUTTONDBLCLK
+NIF
+NIN
 NOAGGREGATION
 NOASYNC
+NOCHANGEDIR
 NOPROGRESS
 NOREDIRECTIONBITMAP
+NOREPEAT
+NOTIFYBYPOS
+NOTIFYICON
+NOTIFYICONDATA
 ntprivapi
 oaidl
 ocidl
+ODR
+offsetof
+osver
+OSVERSIONINFOEXW
 otms
 OUTLINETEXTMETRICW
 overridable
 PAGESCROLL
+PICKFOLDERS
 pmr
+rcx
 REGCLS
 RETURNCMD
-REGCLS
 rfind
 roundf
 RSHIFT
-rx
 schandle
 semver
 serializer
+SETVERSION
+SHELLEXECUTEINFOW
 shobjidl
+SHOWMINIMIZED
+SHOWTIP
+SINGLEUSE
 SIZENS
 smoothstep
-GETDESKWALLPAPER
-SHELLEXECUTEINFOW
 snprintf
 spsc
 sregex
+SRWLOC
+SRWLOCK
 STDCPP
+STDMETHOD
 strchr
+strcpy
+streambuf
+strtoul
+Stubless
 Subheader
 Subpage
-UPDATEINIFILE
 syscall
+TASKBARCREATED
 TBPF
 THEMECHANGED
+tlg
 tmp
 tolower
+toupper
 TTask
 TVal
-tx
+UChar
 UPDATEINIFILE
 userenv
 wcsstr
 wcstoui
+winmain
+wmemcmp
 wpc
 wsregex
+wwinmain
+xchg
 XDocument
 XElement
+xfacet
+xhash
+XIcon
+xiosbase
+xlocale
+xlocbuf
+xlocinfo
+xlocmes
+xlocmon
+xlocnum
+xloctime
+XMax
+xmemory
 XParse
+xpath
+xstddef
+xstring
+xtree
+xutility
+YIcon
+YMax

.github/actions/spelling/allow/colors.txt

@@ -0,0 +1,117 @@
+alice
+aliceblue
+antiquewhite
+blanchedalmond
+blueviolet
+burlywood
+cadetblue
+cornflowerblue
+cornsilk
+cyan
+darkblue
+darkcyan
+darkgoldenrod
+darkgray
+darkgreen
+darkgrey
+darkkhaki
+darkmagenta
+darkolivegreen
+darkorange
+darkorchid
+darkred
+darksalmon
+darkseagreen
+darkslateblue
+darkslategray
+darkslategrey
+darkturquoise
+darkviolet
+deeppink
+deepskyblue
+dimgray
+dimgrey
+dodgerblue
+firebrick
+floralwhite
+forestgreen
+gainsboro
+ghostwhite
+greenyellow
+hotpink
+indian
+indianred
+lavenderblush
+lawngreen
+lemonchiffon
+lightblue
+lightcoral
+lightcyan
+lightgoldenrod
+lightgoldenrodyellow
+lightgray
+lightgreen
+lightgrey
+lightpink
+lightsalmon
+lightseagreen
+lightskyblue
+lightslateblue
+lightslategray
+lightslategrey
+lightsteelblue
+lightyellow
+limegreen
+mediumaquamarine
+mediumblue
+mediumorchid
+mediumpurple
+mediumseagreen
+mediumslateblue
+mediumspringgreen
+mediumturquoise
+mediumvioletred
+midnightblue
+mintcream
+mistyrose
+navajo
+navajowhite
+navyblue
+oldlace
+olivedrab
+orangered
+palegoldenrod
+palegreen
+paleturquoise
+palevioletred
+papayawhip
+peachpuff
+peru
+powderblue
+rebecca
+rebeccapurple
+rosybrown
+royalblue
+saddlebrown
+sandybrown
+seagreen
+sienna
+skyblue
+slateblue
+slategray
+slategrey
+springgreen
+steelblue
+violetred
+webgray
+webgreen
+webgrey
+webmaroon
+webpurple
+whitesmoke
+xaroon
+xray
+xreen
+xrey
+xurple
+yellowgreen

.github/actions/spelling/allow/fonts.txt

@@ -7,3 +7,4 @@ Iosevka
 MDL
 Monofur
 Segoe
+wght

.github/actions/spelling/allow/math.txt

@@ -0,0 +1,11 @@
+atan
+CPrime
+HBar
+HPrime
+isnan
+LPrime
+LStep
+powf
+RSub
+sqrtf
+ULP

.github/actions/spelling/allow/microsoft.txt

@@ -1,13 +1,22 @@
 ACLs
 ADMINS
+advapi
 altform
 altforms
 appendwttlogging
+appx
+appxbundle
+appxerror
+appxmanifest
+ATL
 backplating
 bitmaps
 BOMs
 CPLs
+cpptools
+cppvsdbg
 CPRs
+cryptbase
 DACL
 DACLs
 diffs
@@ -16,13 +25,21 @@ dotnetfeed
 DTDs
 DWINRT
 enablewttlogging
+Intelli
+IVisual
 LKG
+LOCKFILE
+Lxss
 mfcribbon
 microsoft
 microsoftonline
+MSAA
+msixbundle
+MSVC
 muxc
 netcore
 osgvsowi
+PFILETIME
 pgc
 pgo
 pgosweep
@@ -30,19 +47,29 @@ powerrename
 powershell
 propkey
 pscustomobject
+QWORD
+regedit
 robocopy
 SACLs
+sdkddkver
 Shobjidl
 Skype
+SRW
+sxs
+Sysinternals
 sysnative
 systemroot
 taskkill
 tasklist
 tdbuildteamid
+unvirtualized
 VCRT
 vcruntime
+Virtualization
 visualstudio
+vscode
 VSTHRD
+winsdkver
 wlk
 wslpath
 wtl

.github/actions/spelling/allow/names.txt

@@ -13,6 +13,7 @@ ethanschoonover
 Firefox
 Gatta
 glsl
+Gravell
 Grie
 Griese
 Hernan
@@ -30,6 +31,7 @@ Kourosh
 kowalczyk
 leonmsft
 Lepilleur
+lhecker
 lukesampson
 Manandhar
 mbadolato
@@ -51,6 +53,7 @@ oldnewthing
 opengl
 osgwiki
 pabhojwa
+panos
 paulcam
 pauldotknopf
 PGP
@@ -65,12 +68,13 @@ sonpham
 stakx
 thereses
 Walisch
+Wellons
 Wirt
 Wojciech
 zadjii
 Zamor
-zamora
 Zamora
+zamora
 Zoey
 zorio
 Zverovich

.github/actions/spelling/dictionary/colors.txt

@@ -1,782 +0,0 @@
-snow
-ghost-white
-ghostwhite
-white-smoke
-whitesmoke
-gainsboro
-floral-white
-floralwhite
-old-lace
-oldlace
-linen
-antique-white
-antiquewhite
-papaya-whip
-papayawhip
-blanched-almond
-blanchedalmond
-bisque
-peach-puff
-peachpuff
-navajo-white
-navajowhite
-moccasin
-cornsilk
-ivory
-lemon-chiffon
-lemonchiffon
-seashell
-honeydew
-mint-cream
-mintcream
-azure
-alice-blue
-aliceblue
-lavender
-lavender-blush
-lavenderblush
-misty-rose
-mistyrose
-white
-black
-dark-slate-gray
-darkslategray
-dark-slate-grey
-darkslategrey
-dim-gray
-dimgray
-dim-grey
-dimgrey
-slate-gray
-slategray
-slate-grey
-slategrey
-light-slate-gray
-lightslategray
-light-slate-grey
-lightslategrey
-gray
-grey
-xray
-x11gray
-xrey
-x11grey
-web-gray
-webgray
-web-grey
-webgrey
-light-grey
-lightgrey
-light-gray
-lightgray
-midnight-blue
-midnightblue
-navy
-navy-blue
-navyblue
-cornflower-blue
-cornflowerblue
-dark-slate-blue
-darkslateblue
-slate-blue
-slateblue
-medium-slate-blue
-mediumslateblue
-light-slate-blue
-lightslateblue
-medium-blue
-mediumblue
-royal-blue
-royalblue
-blue
-dodger-blue
-dodgerblue
-deep-sky-blue
-deepskyblue
-sky-blue
-skyblue
-light-sky-blue
-lightskyblue
-steel-blue
-steelblue
-light-steel-blue
-lightsteelblue
-light-blue
-lightblue
-powder-blue
-powderblue
-pale-turquoise
-paleturquoise
-dark-turquoise
-darkturquoise
-medium-turquoise
-mediumturquoise
-turquoise
-cyan
-aqua
-light-cyan
-lightcyan
-cadet-blue
-cadetblue
-medium-aquamarine
-mediumaquamarine
-aquamarine
-dark-green
-darkgreen
-dark-olive-green
-darkolivegreen
-dark-sea-green
-darkseagreen
-sea-green
-seagreen
-medium-sea-green
-mediumseagreen
-light-sea-green
-lightseagreen
-pale-green
-palegreen
-spring-green
-springgreen
-lawn-green
-lawngreen
-green
-lime
-xreen
-x11green
-web-green
-webgreen
-chartreuse
-medium-spring-green
-mediumspringgreen
-green-yellow
-greenyellow
-lime-green
-limegreen
-yellow-green
-yellowgreen
-forest-green
-forestgreen
-olive-drab
-olivedrab
-dark-khaki
-darkkhaki
-khaki
-pale-goldenrod
-palegoldenrod
-light-goldenrod-yellow
-lightgoldenrodyellow
-light-yellow
-lightyellow
-yellow
-gold
-light-goldenrod
-lightgoldenrod
-goldenrod
-dark-goldenrod
-darkgoldenrod
-rosy-brown
-rosybrown
-indian-red
-indianred
-saddle-brown
-saddlebrown
-sienna
-peru
-burlywood
-beige
-wheat
-sandy-brown
-sandybrown
-tan
-chocolate
-firebrick
-brown
-dark-salmon
-darksalmon
-salmon
-light-salmon
-lightsalmon
-orange
-dark-orange
-darkorange
-coral
-light-coral
-lightcoral
-tomato
-orange-red
-orangered
-red
-hot-pink
-hotpink
-deep-pink
-deeppink
-pink
-light-pink
-lightpink
-pale-violet-red
-palevioletred
-maroon
-xaroon
-x11maroon
-web-maroon
-webmaroon
-medium-violet-red
-mediumvioletred
-violet-red
-violetred
-magenta
-fuchsia
-violet
-plum
-orchid
-medium-orchid
-mediumorchid
-dark-orchid
-darkorchid
-dark-violet
-darkviolet
-blue-violet
-blueviolet
-purple
-xurple
-x11purple
-web-purple
-webpurple
-medium-purple
-mediumpurple
-thistle
-snow1
-snow2
-snow3
-snow4
-seashell1
-seashell2
-seashell3
-seashell4
-antiquewhite1
-antiquewhite2
-antiquewhite3
-antiquewhite4
-bisque1
-bisque2
-bisque3
-bisque4
-peachpuff1
-peachpuff2
-peachpuff3
-peachpuff4
-navajowhite1
-navajowhite2
-navajowhite3
-navajowhite4
-lemonchiffon1
-lemonchiffon2
-lemonchiffon3
-lemonchiffon4
-cornsilk1
-cornsilk2
-cornsilk3
-cornsilk4
-ivory1
-ivory2
-ivory3
-ivory4
-honeydew1
-honeydew2
-honeydew3
-honeydew4
-lavenderblush1
-lavenderblush2
-lavenderblush3
-lavenderblush4
-mistyrose1
-mistyrose2
-mistyrose3
-mistyrose4
-azure1
-azure2
-azure3
-azure4
-slateblue1
-slateblue2
-slateblue3
-slateblue4
-royalblue1
-royalblue2
-royalblue3
-royalblue4
-blue1
-blue2
-blue3
-blue4
-dodgerblue1
-dodgerblue2
-dodgerblue3
-dodgerblue4
-steelblue1
-steelblue2
-steelblue3
-steelblue4
-deepskyblue1
-deepskyblue2
-deepskyblue3
-deepskyblue4
-skyblue1
-skyblue2
-skyblue3
-skyblue4
-lightskyblue1
-lightskyblue2
-lightskyblue3
-lightskyblue4
-slategray1
-slategray2
-slategray3
-slategray4
-lightsteelblue1
-lightsteelblue2
-lightsteelblue3
-lightsteelblue4
-lightblue1
-lightblue2
-lightblue3
-lightblue4
-lightcyan1
-lightcyan2
-lightcyan3
-lightcyan4
-paleturquoise1
-paleturquoise2
-paleturquoise3
-paleturquoise4
-cadetblue1
-cadetblue2
-cadetblue3
-cadetblue4
-turquoise1
-turquoise2
-turquoise3
-turquoise4
-cyan1
-cyan2
-cyan3
-cyan4
-darkslategray1
-darkslategray2
-darkslategray3
-darkslategray4
-aquamarine1
-aquamarine2
-aquamarine3
-aquamarine4
-darkseagreen1
-darkseagreen2
-darkseagreen3
-darkseagreen4
-seagreen1
-seagreen2
-seagreen3
-seagreen4
-palegreen1
-palegreen2
-palegreen3
-palegreen4
-springgreen1
-springgreen2
-springgreen3
-springgreen4
-green1
-green2
-green3
-green4
-chartreuse1
-chartreuse2
-chartreuse3
-chartreuse4
-olivedrab1
-olivedrab2
-olivedrab3
-olivedrab4
-darkolivegreen1
-darkolivegreen2
-darkolivegreen3
-darkolivegreen4
-khaki1
-khaki2
-khaki3
-khaki4
-lightgoldenrod1
-lightgoldenrod2
-lightgoldenrod3
-lightgoldenrod4
-lightyellow1
-lightyellow2
-lightyellow3
-lightyellow4
-yellow1
-yellow2
-yellow3
-yellow4
-gold1
-gold2
-gold3
-gold4
-goldenrod1
-goldenrod2
-goldenrod3
-goldenrod4
-darkgoldenrod1
-darkgoldenrod2
-darkgoldenrod3
-darkgoldenrod4
-rosybrown1
-rosybrown2
-rosybrown3
-rosybrown4
-indianred1
-indianred2
-indianred3
-indianred4
-sienna1
-sienna2
-sienna3
-sienna4
-burlywood1
-burlywood2
-burlywood3
-burlywood4
-wheat1
-wheat2
-wheat3
-wheat4
-tan1
-tan2
-tan3
-tan4
-chocolate1
-chocolate2
-chocolate3
-chocolate4
-firebrick1
-firebrick2
-firebrick3
-firebrick4
-brown1
-brown2
-brown3
-brown4
-salmon1
-salmon2
-salmon3
-salmon4
-lightsalmon1
-lightsalmon2
-lightsalmon3
-lightsalmon4
-orange1
-orange2
-orange3
-orange4
-darkorange1
-darkorange2
-darkorange3
-darkorange4
-coral1
-coral2
-coral3
-coral4
-tomato1
-tomato2
-tomato3
-tomato4
-orangered1
-orangered2
-orangered3
-orangered4
-red1
-red2
-red3
-red4
-deeppink1
-deeppink2
-deeppink3
-deeppink4
-hotpink1
-hotpink2
-hotpink3
-hotpink4
-pink1
-pink2
-pink3
-pink4
-lightpink1
-lightpink2
-lightpink3
-lightpink4
-palevioletred1
-palevioletred2
-palevioletred3
-palevioletred4
-maroon1
-maroon2
-maroon3
-maroon4
-violetred1
-violetred2
-violetred3
-violetred4
-magenta1
-magenta2
-magenta3
-magenta4
-orchid1
-orchid2
-orchid3
-orchid4
-plum1
-plum2
-plum3
-plum4
-mediumorchid1
-mediumorchid2
-mediumorchid3
-mediumorchid4
-darkorchid1
-darkorchid2
-darkorchid3
-darkorchid4
-purple1
-purple2
-purple3
-purple4
-mediumpurple1
-mediumpurple2
-mediumpurple3
-mediumpurple4
-thistle1
-thistle2
-thistle3
-thistle4
-gray0
-grey0
-gray1
-grey1
-gray2
-grey2
-gray3
-grey3
-gray4
-grey4
-gray5
-grey5
-gray6
-grey6
-gray7
-grey7
-gray8
-grey8
-gray9
-grey9
-gray10
-grey10
-gray11
-grey11
-gray12
-grey12
-gray13
-grey13
-gray14
-grey14
-gray15
-grey15
-gray16
-grey16
-gray17
-grey17
-gray18
-grey18
-gray19
-grey19
-gray20
-grey20
-gray21
-grey21
-gray22
-grey22
-gray23
-grey23
-gray24
-grey24
-gray25
-grey25
-gray26
-grey26
-gray27
-grey27
-gray28
-grey28
-gray29
-grey29
-gray30
-grey30
-gray31
-grey31
-gray32
-grey32
-gray33
-grey33
-gray34
-grey34
-gray35
-grey35
-gray36
-grey36
-gray37
-grey37
-gray38
-grey38
-gray39
-grey39
-gray40
-grey40
-gray41
-grey41
-gray42
-grey42
-gray43
-grey43
-gray44
-grey44
-gray45
-grey45
-gray46
-grey46
-gray47
-grey47
-gray48
-grey48
-gray49
-grey49
-gray50
-grey50
-gray51
-grey51
-gray52
-grey52
-gray53
-grey53
-gray54
-grey54
-gray55
-grey55
-gray56
-grey56
-gray57
-grey57
-gray58
-grey58
-gray59
-grey59
-gray60
-grey60
-gray61
-grey61
-gray62
-grey62
-gray63
-grey63
-gray64
-grey64
-gray65
-grey65
-gray66
-grey66
-gray67
-grey67
-gray68
-grey68
-gray69
-grey69
-gray70
-grey70
-gray71
-grey71
-gray72
-grey72
-gray73
-grey73
-gray74
-grey74
-gray75
-grey75
-gray76
-grey76
-gray77
-grey77
-gray78
-grey78
-gray79
-grey79
-gray80
-grey80
-gray81
-grey81
-gray82
-grey82
-gray83
-grey83
-gray84
-grey84
-gray85
-grey85
-gray86
-grey86
-gray87
-grey87
-gray88
-grey88
-gray89
-grey89
-gray90
-grey90
-gray91
-grey91
-gray92
-grey92
-gray93
-grey93
-gray94
-grey94
-gray95
-grey95
-gray96
-grey96
-gray97
-grey97
-gray98
-grey98
-gray99
-grey99
-gray100
-grey100
-dark-grey
-darkgrey
-dark-gray
-darkgray
-dark-blue
-darkblue
-dark-cyan
-darkcyan
-dark-magenta
-darkmagenta
-dark-red
-darkred
-light-green
-lightgreen
-crimson
-indigo
-olive
-rebecca-purple
-rebeccapurple
-silver
-teal

.github/actions/spelling/dictionary/math.txt

@@ -1,3 +0,0 @@
-powf
-sqrtf
-isnan

.github/actions/spelling/excludes.txt

@@ -1,3 +1,4 @@
+(?:(?i)\.png$)
 (?:^|/)dirs$
 (?:^|/)go\.mod$
 (?:^|/)go\.sum$
@@ -35,7 +36,6 @@ SUMS$
 \.pbxproj$
 \.pdf$
 \.pem$
-(?:(?i)\.png$)
 \.psd$
 \.runsettings$
 \.sig$
@@ -54,13 +54,26 @@ SUMS$
 \.zip$
 ^consolegit2gitfilters\.json$
 ^dep/
-^oss/
+^doc/reference/master-sequence-list.csv$
 ^doc/reference/UTF8-torture-test\.txt$
+^oss/
+^src/host/ft_uia/run\.bat$
+^src/host/runft\.bat$
+^src/host/runut\.bat$
 ^src/interactivity/onecore/BgfxEngine\.
 ^src/renderer/wddmcon/WddmConRenderer\.
+^src/terminal/adapter/ut_adapter/run\.bat$
+^src/terminal/parser/delfuzzpayload\.bat$
+^src/terminal/parser/ft_fuzzer/run\.bat$
 ^src/terminal/parser/ft_fuzzer/VTCommandFuzzer\.cpp$
-^src/types/ut_types/UtilsTests.cpp$
+^src/terminal/parser/ft_fuzzwrapper/run\.bat$
+^src/terminal/parser/ut_parser/run\.bat$
+^src/tools/integrity/packageuwp/ConsoleUWP\.appxSources$
+^src/tools/lnkd/lnkd\.bat$
+^src/tools/pixels/pixels\.bat$
+^src/tools/texttests/fira\.txt$
 ^src/tools/U8U16Test/(?:fr|ru|zh)\.txt$
+^src/types/ut_types/UtilsTests.cpp$
 ^\.github/actions/spelling/
 ^\.gitignore$
-^doc/reference/master-sequence-list.csv$
+^\XamlStyler.json$

.github/actions/spelling/expect/alphabet.txt

@@ -1,3 +1,9 @@
+AAAa
+AAAAA
+AAAAAAAAAAAAA
+AAAAAABBBBBBCCC
+AAAAABBBBBBCCC
+abcd
 abcd
 abcde
 abcdef
@@ -5,12 +11,20 @@ ABCDEFG
 ABCDEFGH
 ABCDEFGHIJ
 abcdefghijk
+ABCDEFGHIJKLMNO
 abcdefghijklmnop
 ABCDEFGHIJKLMNOPQRST
 abcdefghijklmnopqrstuvwxyz
+ABCG
 ABE
-BBGGRR
+abf
+BBBBB
+BBBBBBBB
 BBBBBBBBBBBBBBDDDD
+BBBBBCCC
+BBBBCCCCC
+BBGGRR
+CCE
 EFG
 EFGh
 QQQQQQQQQQABCDEFGHIJ
@@ -31,3 +45,4 @@ ZYXWVUT
 ZZBBZ
 ZZZBB
 ZZZBZ
+ZZZZZ

.github/actions/spelling/expect/web.txt

@@ -1,6 +1,7 @@
 http
-td
 www
+easyrgb
+php
 ecma
 rapidtables
 WCAG
@@ -10,9 +11,9 @@ robertelder
 kovidgoyal
 leonerd
 fixterms
-uk
 winui
 appshellintegration
+mdtauk
 cppreference
 gfycat
-what3words
+Guake

.github/actions/spelling/patterns/patterns.txt

@@ -22,3 +22,6 @@ Base64::s_(?:En|De)code\(L"[^"]+"
 VERIFY_ARE_EQUAL\(L"[^"]+"
 "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789\+/"
 std::memory_order_[\w]+
+D2DERR_SHADER_COMPILE_FAILED
+TIL_FEATURE_[0-9A-Z_]+
+vcvars\w*

.github/actions/spelling/reject.txt

@@ -0,0 +1,22 @@
+^attache$
+^attacher$
+^attachers$
+^spae$
+^spaebook$
+^spaecraft$
+^spaed$
+^spaedom$
+^spaeing$
+^spaeings$
+^spae-man$
+^spaeman$
+^spaer$
+^Spaerobee$
+^spaes$
+^spaewife$
+^spaewoman$
+^spaework$
+^spaewright$
+^wether$
+^wethers$
+^wetherteg$

.github/workflows/spelling.yml

@@ -1,15 +0,0 @@
-name: Spell checking
-on:
-  pull_request_target:
-  push:
-
-jobs:
-  build:
-    name: Spell checking
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v2.0.0
-      with:
-        ref: ${{ github.event.pull_request.head.sha }}
-        fetch-depth: 5
-    - uses: check-spelling/check-spelling@0.0.17-alpha

.github/workflows/spelling2.yml

@@ -0,0 +1,20 @@
+# spelling.yml is blocked per https://github.com/check-spelling/check-spelling/security/advisories/GHSA-g86g-chm8-7r2p
+name: Spell checking
+on:
+  pull_request_target:
+  push:
+
+jobs:
+  spelling:
+    name: Spell checking
+    runs-on: ubuntu-latest
+    steps:
+    - name: checkout-merge
+      if: "contains(github.event_name, 'pull_request')"
+      uses: actions/checkout@v2
+      with:
+        ref: refs/pull/${{github.event.pull_request.number}}/merge
+    - name: checkout
+      if: "!contains(github.event_name, 'pull_request')"
+      uses: actions/checkout@v2
+    - uses: check-spelling/check-spelling@v0.0.19

doc/specs/#2634 - Broadcast Input/#2634 - Broadcast Input.md

@@ -0,0 +1,374 @@
+---
+author: Mike Griese @zadjii-msft
+created on: 2021-03-03
+last updated: 2021-03-04
+issue id: #2634
+---
+
+# Broadcast Input
+
+## Abstract
+
+"Broadcast Input" is a feature present on other terminals which allows the user
+to send the same input to multiple tabs or panes at the same time. This can make
+it simpler for the user to run the same command in multiple directories or
+servers at the same time.
+
+With a viable prototype in [#9222], it's important that we have a well-defined
+plan for how we want this feature to be exposed before merging that PR. This
+spec is intended to be a lighter-than-usual spec to build consensus on the
+design of how the actions should be expressed.
+
+## Background
+
+### Inspiration
+
+This spec is heavily inspired by the [iTerm2 implementation]. @carlos-zamora did
+a great job of breaking down how iTerm2 works in [this comment].
+
+SecureCRT also implements a similar feature using a "chat window" that can send
+the input in the chat window to all tabs. This seemed like a less ergonomic
+solution, so it was not seriously considered.
+
+Additionally, Terminator (on \*nix) allows for a similar feature through the use
+of "groups". From [@zljubisic]:
+
+> In Linux terminator you can define groups, and than put each pane in one of
+> defined groups. Afterwards, you can choose broadcasting to all panes, only
+> certain group or no broadcast at all.
+
+This also seemed like a less powerful version of broadcast input than the
+iterm2-like version, so it was also not further investigated.
+
+### User Stories
+
+iTerm2 supports the following actions:
+
+* **Story A:** _Send input to current session only_: The default setting.
+* **Story B:** _Broadcast to all panes in all tabs_: Anything you type on the
+  keyboard goes to all sessions in this window.
+* **Story C:** _Broadcast to all panes in current tab_: Anything you type on the
+  keyboard goes to all sessions in this tab.
+* **Story D:** _Toggle broadcast input to current session_: Toggles whether this
+  session receives broadcasted keystrokes within this window.
+
+
+## Solution Design
+
+### Proposal 1: iTerm2-like Modal Input Broadcast
+
+iTerm2 implements broadcast input as a type of "modal" system. The user is in
+one of the following modes:
+
+* Broadcast to all panes in all tabs
+* Broadcast to all panes in the current tab
+* Broadcast to some set of panes within the current tab
+* Don't broadcast input at all (the default behavior)
+
+These modes are vaguely per-tab state. There's a global "broadcast to all tabs &
+panes" property. Then, each tab also has a pair of values:
+* Should input be sent to all panes in this tab?
+* If not, which panes should input be sent to?
+
+It's not possible to send input to one pane in tab A, then another pane in tab
+B, without enabling the global "broadcast to everyone" mode.
+
+This seems to break down into the following actions:
+
+```json
+{ "action": "toggleBroadcastInput", "scope": "window" },
+{ "action": "toggleBroadcastInput", "scope": "tab" },
+{ "action": "toggleBroadcastInput", "scope": "pane" },
+{ "action": "disableBroadcastInput" },
+```
+
+Which would be accompanied by the following internal properties:
+* A window (`TerminalPage`-level) property for `broadcastToAllPanesAndTabs`
+* A per-tab property for `broadcastToAllPanes`
+* A per-tab set of panes to broadcast to
+
+The scopes would work as follows:
+
+* `"scope": "window"`: Toggle the window's "broadcast to all tabs and panes"
+  setting.
+* `"scope": "tab"`: Toggle the tab's "broadcast to all panes in this tab"
+  setting.
+    - This does not modify the set of panes that the user is  broadcasting to in
+      the tab, merely toggles the tab's setting. If the user has a set of panes
+      they're broadcasting to in this tab, then toggles this setting on and off,
+      we'll return to broadcasting to that set.
+* `"scope": "pane"`: Add this pane to the set of panes being broadcasted to in
+  this tab.
+    - **TODO: FOR DISCUSSION**: Should this disable the tab's
+      "broadcastToAllPanes" setting? Or should it leave that alone?
+* `"disableBroadcastInput"`: Set the global setting to false, the tab's setting
+  to false, and clear the set of panes being broadcasted to for this tab.
+
+#### Pros
+* This is exactly how iTerm2 does it, so there's prior art.
+* If you're not globally broadcasting, then you're only ever broadcasting to
+  some (sub)set of the panes in the current tab. So global broadcast mode is
+  the only time a user would need to worry about input being to be sent to
+  an inactive tab.
+* You can have a set of panes to broadcast to in the first tab, then a
+  _separate_ set to broadcast to in a second tab. Broadcasting in one tab
+  does not affect the other.
+
+#### Cons
+* I frankly think the `tab`/`pane` interaction can be a little weird. Like for
+  this scenario:
+  - enable broadcast input for tab 1
+  - switch to tab 2
+  - enable broadcast input for a pane in tab 2
+
+  There's valid confusion to be had between the following two behaviors:
+  1. input goes to all of tab 1 _and_ the pane in tab 2
+  2. input only goes to the pane in tab 2
+* You can't broadcast to a subset of panes in inactive tabs, in addition to
+  the active tab. All panes you want to broadcast to must be in the active
+  tab.
+* Does creating a new split in a pane that's being broadcast to add that pane to
+  the broadcast set?
+
+#### What would this mean for PR #9222?
+
+The prototype PR [#9222] basically just implemented `{ "action":
+"toggleBroadcastInput", "scope": "tab" }`. We could make `tab` the default
+`scope` if no other one is specified, and then the PR would need basically no
+modifications. Future PRs could add args to the `toggleBroadcastInput` action,
+without breaking users who bind a key to that action now.
+
+### Proposal 2: Broadcast Set
+
+This was the design I had originally came up with before investigating iTerm2
+much closer. This design involves a "broadcast set" of panes. All the panes in
+the broadcast set would also get the `KeySent` and `CharSent` events, in
+addition to the active pane. (The active pane may be a part of the broadcast
+set). If a pane is read-only in the broadcast set, then it won't handle those
+broadcasted events (obviously).
+
+As far as actions, we're looking at something like:
+
+* **A** Only send input to the active pane
+  * Remove all the panes from the broadcast set
+* **B** send input to all panes in all tabs
+  * If all the panes are in the broadcast set, remove them all. Otherwise, add
+    all panes in all tabs to the broadcast set.
+* **C** send input to all panes in the current tab
+  * If all the panes in the current tab are in the broadcast set, remove them
+    from the broadcast set. Otherwise, add all the panes from this tab to the
+    broadcast set.
+* **D** toggle sending input to the current pane
+  * If this pane is in the broadcast set, remove it. Otherwise add it.
+This seems to break down into the following actions:
+
+```json
+{ "action": "disableBroadcastInput" },
+{ "action": "toggleBroadcastInput", "scope": "window" },
+{ "action": "toggleBroadcastInput", "scope": "tab" },
+{ "action": "toggleBroadcastInput", "scope": "pane" },
+```
+
+Which would be accompanied by the following internal properties:
+* A window (`TerminalPage`-level) set of panes to broadcast to.
+
+#### Pros:
+* Mentally, you're either adding panes to the set of panes to broadcast to, or
+  removing them.
+* You can broadcast to panes in multiple tabs, without broadcasting to _all_
+  panes in all tabs.
+
+#### Cons:
+* is _slightly_ different from iTerm2.
+* Does creating a new split in a pane that's being broadcast to add that pane to
+  the broadcast set?
+* You can't have a set of panes to broadcast to in the one tab, and a different
+  set in another tab. As an example:
+  1. in tab 1, you add panes A and B to the broadcast set. Typing in either one
+     goes to both A and B.
+  2. in tab 1, switch to pane C. Now input goes to A, B and C.
+  3. in tab 1, switch to pane D. Now input goes to A, B and D.
+  4. switch to tab 2, pane E. Now input goes to A, B and E.
+
+  You can't have like, a set with A & B (in 1), then E & F (in 2). So if someone
+  wants to type to both panes in 1, then both panes in 2, then both panes in 1,
+  they need to keep toggling which panes are in the broadcast set.
+
+#### What would this mean for PR #9222?
+
+Similar to Proposal 1, we'd use `tab` as the default value for `scope`. In the
+future, when we add support for the other scopes, we'd change how the
+broadcasting works, to use a set of panes to broadcast to, instead of just the
+tab-level property.
+
+### Proposal 3: It's iTerm2, but slightly different
+
+While typing this up, I thought maybe it might make more sense if we took the
+iTerm2 version, and changed it slightly:
+
+* `"scope": "tab"`: If all the panes are in the broadcast set for this tab, then
+  remove them all. Otherwise, add all the panes in this tab to this tab's
+  broadcast set.
+* `"scope": "pane"`: If this pane is in the broadcast set for a tab, then remove
+  it. Otherwise, add it.
+
+With this, we get rid of the tab-level setting for "broadcast to all the panes
+in this tab", and rely only on the broadcast set for that tab.
+
+#### Pros:
+* All the pros from proposal A
+* Does away with the seemingly weird toggling between "all the panes in a tab"
+  and "some of the panes in a tab" that's possible with proposal A
+
+#### Cons:
+* You can't broadcast to a subset of panes in inactive tabs, in addition to
+  the active tab. All panes you want to broadcast to must be in the active
+  tab.
+* is _slightly_ different from iTerm2. Just _slightly_.
+* Does creating a new split in a pane that's being broadcast to add that pane to
+  the broadcast set?
+
+#### What would this mean for PR #9222?
+
+Same as with proposal A, we wouldn't change anything in the current PR. A future
+PR that would add the other scope's to that action would need to change how the
+broadcasting within a tab works, to use a set of panes to broadcast to, instead
+of just the tab-level property.
+
+## Conclusion
+
+I'm proposing these settings for broader discussion. I'm not really sure which I
+like most at this point. 1 & 3 have the advantage of being most similar to the
+prior art, but 2 is more easily extendable to "groups" (see [Future
+Considerations](#Future-Considerations)).
+
+**TODO**: Make a decision.
+
+_**Fortunately**_: All these proposals actually use the same set of actions. So
+it doesn't _really_ matter which we pick right now. We can unblock [#9222] as
+the implementation of the `"tab"` scope, and address other scopes in the future.
+We should still decide long-term which of these we'd like, but the actions seem
+universal.
+
+## UI/UX Design
+
+This is supposed to be a quick & dirty spec, so I'm LARGELY skipping this.
+
+As far as indicators go, we'll throw something like:
+
+![NetworkTower Segoe UI Icon](broadcast-segoe-icon.png)
+
+in the tab when a pane is being broadcasted to. If all tabs are being
+broadcasted to, then they'll all have that icon. If a tab is inactive, and any
+pane in that tab is being broadcast to, then show the icon in the tab.
+
+It probably makes the most sense to have pane titlebars (#4998) also display
+that icon.
+
+In the original PR, it was suggested to use some variant of the [accent color]
+to on the borders of panes that are currently receiving broadcasted input. We're
+already using the accent color on the borders of the active pane.
+`SystemAccentColorLight*`/`SystemAccentColorDark*` would provide a way of using
+a similar hue with different lightness/saturation. This would be a decent visual
+indicator that they're _not_ the active pane, but they are going to receive
+input. Something a bit like:
+
+![A sample of using the border to indicate the broadcasted-to panes](broadcast-input-borders.gif)
+
+iTerm2 also supports displaying "stripes" in the background of all the panes
+that are being broadcast too. That's certainly another way of indicating this
+feature to the user. I'm not sure how we'd layer it with the background image
+though.
+
+## Potential Issues
+
+<table>
+
+<tr>
+<td><strong>Compatibility</strong></td>
+<td>
+
+[comment]: # Will the proposed change break existing code/behaviors? If so, how, and is the breaking change "worth it"?
+
+</td>
+</tr>
+</table>
+
+[comment]: # If there are any other potential issues, make sure to include them here.
+
+### Future Considerations
+
+Let's look to iTerm2, who's supported this feature for years, for some
+inspiration of future things we should be worried about. If their users have
+asked for these features, then it's inevitable that our users will too 😉
+
+* [iterm2#6709]: Broadcast Input to multiple windows
+  - This is pretty straightforward. Would require coordination with the Monarch
+    though, and I'm worried about the perf hit of tossing every keystroke across
+    the process boundary.
+  - I suppose this would be `{ "action": "toggleBroadcastInput", "scope":
+    "global" }`
+* [iterm2#6451], [iterm2#5563]: "Broadcast commands"
+  - iTerm2 has an action that lets the user manually clear the terminal-side
+    buffer. (This is tracked on the Windows Terminal as [#1882]). It might make
+    sense for there to be a mode where some _actions_ are also broadcast to
+    panes, not just key strokes. But which actions would those be? Moving the
+    selection anchors? Copy doesn't really make sense. Paste _does_ though.
+    Maybe the open find dialog / next&prev search match actions?
+  - This probably would require it's own spec.
+* [iterm2#6007]: Different stripe color for different broadcast modes
+  - Have one color to indicate when broadcasting in `global` scope, another in
+    `tab` scope, a third in `pane` scope.
+  - This might mesh well with theming ([#3327]), for properties like
+    `pane.broadcastBorderColor.globalScope`,
+    `pane.broadcastBorderColor.paneScope`. Don't love those names, but you get
+    the idea.
+* **[iterm2#5639]: Broadcast groups**, [iterm2#3372]: Broadcast Input to
+  multiple but not all tabs
+  - This is probably the most interesting request. I think this one identifies a
+    major shortcoming of the above proposals. With proposal 2, there's only ever
+    one top-level broadcast group. With proposals 1 & 3, there's per-tab
+    broadcast groups. In neither proposal can you have multiple concurrent
+    side-by-side broadcast groups.
+  - Groups should probably work across tabs. This would suggest that Proposal 2
+    is closer to how groups would work. Instead of there being one top-level
+    set, there would be multiple. **I'm not sure how proposals 1&3 would
+    seamlessly transition into also supporting groups**.
+  - The major trick here is: how do we differentiate these different groups to
+    the user? If we used the broadcast icon with a number, maybe in the corner
+    of the tab? Like [📡: 1]? Can a pane be in multiple broadcast sets at the
+    same time?
+  - The natural arg idea would be `{ "action": "toggleBroadcastInput", "scope":
+    "tab", "group": 1 }` to say "add all panes in the tab to broadcast group 1",
+    or "remove all panes in the tab from broadcast group 1". If panes are in
+    another group, they'd be moved to the specified group. If all panes are in
+    that group, then remove them all.
+  - The UI for this would certainly get complex fast.
+  - This also matches the Terminator-style broadcasting to groups.
+
+## Resources
+
+[comment]: # Be sure to add links to references, resources, footnotes, etc.
+
+
+### Footnotes
+
+<a name="footnote-1"><a>[1]:
+
+
+[#1882]: https://github.com/microsoft/terminal/issues/1882
+[#2634]: https://github.com/microsoft/terminal/issues/2634
+[#4998]: https://github.com/microsoft/terminal/issues/4998
+[#9222]: https://github.com/microsoft/terminal/pull/9222
+[this comment]: https://github.com/microsoft/terminal/issues/2634#issuecomment-789116413
+[iTerm2 implementation]: https://iterm2.com/documentation-one-page.html#documentation-menu-items.html
+[@zljubisic]: https://github.com/microsoft/terminal/pull/9222#issuecomment-789143189
+[accent color]: https://docs.microsoft.com/en-us/windows/uwp/design/style/color#accent-color-palette
+
+
+[iterm2#6709]: https://gitlab.com/gnachman/iterm2/-/issues/6709
+[iterm2#6451]: https://gitlab.com/gnachman/iterm2/-/issues/6451
+[iterm2#6007]: https://gitlab.com/gnachman/iterm2/-/issues/6007
+[iterm2#5639]: https://gitlab.com/gnachman/iterm2/-/issues/5639
+[iterm2#5563]: https://gitlab.com/gnachman/iterm2/-/issues/5563
+[iterm2#3372]: https://gitlab.com/gnachman/iterm2/-/issues/3372