Skip to content

Improve invalid keybind error messages#3727

Closed
otherJL0 wants to merge 96 commits intoghostty-org:mainfrom
otherJL0:detailed-keybind-errors
Closed

Improve invalid keybind error messages#3727
otherJL0 wants to merge 96 commits intoghostty-org:mainfrom
otherJL0:detailed-keybind-errors

Conversation

@otherJL0
Copy link
Copy Markdown

@otherJL0 otherJL0 commented Dec 28, 2024

Draft for Better keybind error messages discussion

@otherJL0 otherJL0 force-pushed the detailed-keybind-errors branch from 2f29653 to 670ee41 Compare December 31, 2024 12:04
salfel and others added 29 commits January 1, 2025 13:55
`desktop` is the default value of `gtk-single-instance`; `detect` is not a valid value.
I think this must have snuck in due to my fork falling behind the
upstream.
…onfirmation

Fixes ghostty-org#3648
The confirm-close-surface configuration can now be set to always
ensuring a confirmation dialog is shown before closing a surface, even
if shell integration indicates no running processes.
Co-authored-by: Gareth Widlansky <101901964+gerblesh@users.noreply.github.com>
This gives people finer-grained control over the coloring of their
window titlebars. Currently only implemented for GTK.

Signed-off-by: Tristan Partin <tristan@partin.io>
It currently has two backticks side by side, which end up rendering as actual backticks rather than a code-formatted blank space.
gigamonster256 and others added 26 commits January 1, 2025 13:55
When writing selected text to file, use `topLeft` and `bottomRight` instead of
`start` and `end` to ensure correct coordinate ordering. This fixes an issue
where selection files could be empty when selecting text in reverse order.

- Use `terminal.Selection.topLeft()` for start coordinate
- Use `terminal.Selection.bottomRight()` for end coordinate
Quick Terminal now focuses on the surface under the mouse
pointer when `focus-follows-mouse` is enabled.

Fixes ghostty-org#3337
The original version had issues converting properly and caused broken
glyphs. This version tries to be as simple as possible in order to make
it easy to understand. I haven't measured the performance but in
practice this will only happen during the first render of the glyph
after a face change (i.e. during launch or when changing font size).
This allows for crisp bitmap font rendering once again.
Now we can be certain that bitmap fonts stay crisp. :^)
This is an expected occurrence with bitmap glyphs and causes unnecessary
spam when using the terminal with one.
macOS bitmap-only fonts are a poorly documented format, which are often
distributed as `.dfont` or `.dfon` files. They use a 'bhed' table in
place of the usual 'head', but the table format is byte-identical, so
enabling the use of bitmap-only fonts only requires us to properly fetch
this table while calculating metrics.

ref: https://fontforge.org/docs/techref/bitmaponlysfnt.html
Fixes ghostty-org#3219

We were holding a reference cycle to the base terminal controller. This
was preventing the window from ever being fully deallocated.
Fixes ghostty-org#4146

This makes it so that keys such as `cmd+1` and `cmd+one` are identical.
@otherJL0 otherJL0 force-pushed the detailed-keybind-errors branch from 670ee41 to 2daeb0d Compare January 1, 2025 18:55
@mitchellh
Copy link
Copy Markdown
Contributor

The history here is a bit crazy and impossible to read. Can you try reopening a clean PR? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.