Repository navigation
Options and Terminal
What you can turn, where goSSMS keeps it, and what a terminal does to the keys and colours you think you asked for.
Eight settings, applied live — no restart, and no screen tear:
| Object Explorer Icons |
Emoji (the default) / Symbols / Portable / None. Symbols uses geometric glyphs instead of emoji; Portable is Symbols with the one glyph not every font has (the column mark) replaced by a plain bullet; None draws no icons. The tree is rebuilt on OK, so the change shows at once |
| Color Theme |
Dark (the default) / Light. The active style is read from the palette at draw time, so switching is a palette swap and everything repaints in place |
| Max default cell length | How many characters a results-grid cell shows before truncating; a column dragged wider shows more |
| Max characters per column (text) | The same cap for Results To Text — SSMS's "Maximum number of characters displayed in each column" |
| Indent size (spaces) | The editor's tab width, pushed into every open query panel and property sheet immediately, and used for new ones |
| Extended Events viewer holds (events) | How many events the live viewer keeps, which is what bounds its memory on a chatty session. A viewer takes it when it opens; open ones keep theirs |
| Max fetch rows (0 = unlimited) | How many rows a query panel keeps of each result set, in grid, text and file mode alike. Reaching it cancels the rest of the script, later GO batches included, and the results status line and Messages say so — see Query Editor. A run reads it when it starts |
| IntelliSense | On or off for the whole feature |
OK writes the config; Cancel or Esc closes without applying. The indent size is the one
setting with a second step behind it — it lives in each editor, so the dialog pushes it into
the panels that are already open rather than waiting for them to be recreated.
| Config and saved connections |
<user config dir>/gossms/config.json — one file holding both the settings above and the connection history, so a machine's worth of servers and a personal theme travel together. Connections are addressed by server and instance, the way Object Explorer shows them |
| Log |
<user config dir>/gossms/gossms.log, rotated at a size cap; the path is shown in Help ▸ About. Logging is on by default and needs no environment variable |
| Recovered query text | Written when the process would otherwise lose it: see Query Editor |
The user config directory is %APPDATA% on Windows, $XDG_CONFIG_HOME or ~/.config on
Linux, ~/Library/Application Support on macOS.
goSSMS is a terminal application, and the terminal decides what it can promise.
-
24-bit colour.
COLORTERM=truecolor|24bit— or aTERMvalue that is known to have it, such asxterm-256color,alacritty,foot-directorwezterm. Windows Terminal advertises it throughWT_SESSION. Without true colour the 16 ANSI colours are used and the theme reads roughly rather than as designed: goSSMS themes in the Delft palette family, whose shades sit between the box colours rather than on them. -
Mouse. Mouse reporting is enabled for the whole window, so click, drag, resize and the
wheels work in the tree, the grids, the splitters and the tabs. The price is that the
terminal no longer hands you its own select-to-copy: copy is in-app (Ctrl+C where a
copy would mean that —
Shift+Clickto follow a URL), and the terminal's own copy is still available withShiftheld where the terminal keeps a key for it. - Keys. See Keys and mouse: a window manager, a terminal multiplexer or an IME can claim a chord before goSSMS sees it. Help ▸ Key Diagnostics prints every key and mouse event with its modifiers and timing, which is the difference between a wrong binding and a key your terminal kept.
- A terminal that quits on a dropped connection (a closed SSH session, a window closed out from under the process) gets an emergency save rather than a lost buffer, because the alternative is a rule nobody learns before they need it.
- Performance is a per-frame budget rather than a polling loop: the screen redraws when something changes, and a 100,000-row grid that is not on screen is not drawn. The result is that idle CPU is what your terminal's own blinking cursor costs, and a query that returns a hundred thousand rows streams into a grid instead of freezing it.
If the mouse does not work, set TERM to xterm-256color, or use Windows Terminal; if the
colours look off, check COLORTERM; if a key does nothing, check Key Diagnostics before
blaming the app.
- Keys and mouse
- Connecting — what is saved, and how secrets are kept
- Query Editor
- Getting connected
- Browsing and editing
- Diagnosing and tuning
- Server features