10189 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Mitchell Hashimoto	b6f338065e	ci: workaround broken lxd start with snap builder (#7267) ... https://discourse.ubuntu.com/t/lxd-doesn-t-start-snap-lxd-device-directory-nonexistent/59785 https://github.com/canonical/lxd-pkg-snap/pull/789 This is required until Namespace or further upstream fixes are made. tip	2025-05-03 15:05:33 -07:00
Mitchell Hashimoto	e174599533	ci: workaround broken lxd start with snap builder ... https://discourse.ubuntu.com/t/lxd-doesn-t-start-snap-lxd-device-directory-nonexistent/59785 https://github.com/canonical/lxd-pkg-snap/pull/789 This is required until Namespace or further upstream fixes are made.	2025-05-03 13:20:00 -07:00
Mitchell Hashimoto	040cdba707	flatpak: update GNOME runtime to 48 (#7261) ... Notable dependencies updates: - GTK 4.16.13 -> 4.18.4 - Libadwaita 1.6.6 -> 1.7.2	2025-05-03 06:57:33 -07:00
Leorize	c0f41aba45	flatpak: update GNOME runtime to 48 ... Notable dependencies updates: - GTK 4.16.13 -> 4.18.4 - Libadwaita 1.6.6 -> 1.7.2	2025-05-02 14:24:02 -05:00
Mitchell Hashimoto	464b85b64c	codeowners: correct shell_integration.zig filename (#7255)	2025-05-02 08:25:27 -07:00
Jon Parise	b2138eeaf0	codeowners: correct shell_integration.zig filename	2025-05-02 10:59:52 -04:00
Mitchell Hashimoto	e79bf71f23	Binding for toggling window float on top (macOS only) (#7246) ... This adds a keybinding and apprt action for #7237.	2025-05-01 09:51:09 -07:00
Mitchell Hashimoto	6e11d947e7	Binding for toggling window float on top (macOS only) ... This adds a keybinding and apprt action for #7237.	2025-05-01 09:47:17 -07:00
Mitchell Hashimoto	a6fd499019	macos: add float on top feature for terminal windows (#7237) ... Closes #5188 **See:** - https://github.com/ghostty-org/ghostty/discussions/5188#discussioncomment-12607781 - https://github.com/ghostty-org/ghostty/discussions/5188#discussioncomment-12984898	2025-05-01 09:24:15 -07:00
Martin Hettiger	f83729ba48	macos: add float on top feature for terminal windows	2025-05-01 09:13:33 -07:00
Mitchell Hashimoto	4b3a49a56e	apprt/gtk: ensure configuration is loaded on startup (#7241) ... Restores the app configuration code removed in https://github.com/ghostty-org/ghostty/pull/6792. The was unnoticed due to `colorSchemeEvent` triggering a configuration reload if `window-theme` deviates from the default (i.e. dark mode is used). Fixes https://github.com/ghostty-org/ghostty/discussions/7206	2025-05-01 08:30:22 -07:00
Leorize	0af5a291ac	apprt/gtk: ensure configuration is loaded on startup ... Restores the app configuration code removed in https://github.com/ghostty-org/ghostty/pull/6792. The was unnoticed due to `colorSchemeEvent` triggering a configuration reload if `window-theme` deviates from the default (i.e. dark mode is used). Fixes https://github.com/ghostty-org/ghostty/discussions/7206	2025-05-01 01:59:36 -05:00
Leah Amelia Chen	2b4f1f8b84	Improve the documentation for gtk-custom-css (#7190) ... Recently when answering [a Discussion], I was reminded of when Tristan once linked the GTK CSS documentation and said “Perhaps good to add this to the docs of the GTK custom CSS config option”, so I decided to do that now. I also added a few random things that I found helpful when attempting to modify Ghostty's CSS; this information was mostly stolen from random people on Discord or accidentally discovered. I really do not care if this is merged or not, nor do I care if the strings are changed considerably[^1], so I am going straight for a Pull Request without bothering to open a Discussion, get that converted to an Issue after a few years, then finally remember to open a Pull Request. I only tested what this looks like in `ghostty +show-config --default --docs`, the manpage and the HTML output; I notably did not try seeing how it renders on the website. The links have to be in angle brackets for the HTML output to have it rendered as URLs, but it looks odd everywhere else; manpages have them with mathematical angle brackets, ⟨like this⟩. I also refrained from using an em (—) or en (–) dash instead of a normal dash (-) as that does not seem to be common in the rest of the documentation. [a Discussion]: https://github.com/ghostty-org/ghostty/discussions/7189 [^1]: I didn't see any guidelines or standards for these strings, so presumably these would be contested as I didn't know what to adhere to when writing them.	2025-04-30 22:33:11 +02:00
Mitchell Hashimoto	ff536e34d6	i18n: fixed the translation for Russian (#7218) ... The problem was highlighted in https://github.com/ghostty-org/ghostty/pull/7127#discussion_r2051223171 In Russian, the words [`затем`](https://ru.wiktionary.org/wiki/%D0%B7%D0%B0%D1%82%D0%B5%D0%BC) and [`либо`](https://ru.wiktionary.org/wiki/%D0%BB%D0%B8%D0%B1%D0%BE) are written separately. @zeshi09 @TicClick take a look?	2025-04-30 07:02:21 -07:00
Tim Culverhouse	b3edc88010	terminal(dcs): convert all xtgettcap queries to upper (#7230) ... XTGETTCAP queries are a semicolon-delimited list of hex encoded terminfo capability names. Ghostty encodes a map using upper case hex encodings, meaning when an application uses a lower case encoding the capability is not found. To fix, we convert the entire list we receive in the query to upper case prior to processing further. Fixes: #7229	2025-04-29 19:06:25 -05:00
Tim Culverhouse	2c1ade763f	terminal(dcs): convert all xtgettcap queries to upper ... XTGETTCAP queries are a semicolon-delimited list of hex encoded terminfo capability names. Ghostty encodes a map using upper case hex encodings, meaning when an application uses a lower case encoding the capability is not found. To fix, we convert the entire list we receive in the query to upper case prior to processing further. Fixes: #7229	2025-04-29 18:42:16 -05:00
Mitchell Hashimoto	533354480a	ci: drop l10n review workflow (#7228) ... *better things are coming*	2025-04-29 14:13:33 -07:00
trag1c	87107a7934	ci: drop l10n review workflow	2025-04-29 18:32:59 +02:00
Kat	4e39756501	Link to GTK CSS docs and add some useful tips to gtk-custom-css' docs. ... It may not be immediately obvious how to style Ghostty despite knowing of the existence of that configuration option; one who is more accustomed to web development would likely be very reliant on their browser's inspector for modifying and debugging the style of their application. GTK CSS also differs in some important ways from the CSS found in browsers, and hence linking to the GTK CSS documentation would save time for anyone new to styling GTK applications.	2025-04-29 22:56:23 +10:00
Mitchell Hashimoto	9a4419ce85	macos: key input that clears preedit without text shouldn't encode (#7226) ... Fixes #7225	2025-04-28 14:58:19 -07:00
Mitchell Hashimoto	e5e89bcbe4	macos: key input that clears preedit without text shouldn't encode ... Fixes #7225	2025-04-28 14:01:17 -07:00
Danil Ovchinnikov	42913c7830	i18n: fixed the translation for Russian ... Co-authored-by: TicClick <ya@ticclick.ch>	2025-04-28 04:08:04 +03:00
Mitchell Hashimoto	7daabdddef	ci: iTerm2 colorscheme update should update flatpak deps (#7214)	2025-04-27 07:50:18 -07:00
Mitchell Hashimoto	99db6b59be	Add config color palette C bindings (#7195) ... C bindings to expose the color palette to Swift for macOS. Returns the full 256 colors from the current color scheme. After fetching the palette with `ghostty_config_get`, you can access the desired color by its index in the list. ### Usage Here is one way to get the palette in Swift. ```swift import GhosttyKit private(set) var config: ghostty_config_t? = nil { didSet { // Free the old value whenever we change guard let old = oldValue else { return } ghostty_config_free(old) } } var paletteColors: [Color] { var paletteList: ghostty_config_palette_s = .init() let key = "palette" if (!ghostty_config_get(config, &paletteList, key, UInt(key.count))) { return [] } var colors: [Color] = [] let mirror = Mirror(reflecting: paletteList.colors) for (_, element) in mirror.children { if let color = element as? ghostty_config_color_s { colors.append(Color( red: Double(color.r) / 255, green: Double(color.g) / 255, blue: Double(color.b) / 255 )) } } print("Palette Colors: ", colors) return colors } ``` Result (GruvboxDarkHard theme) 	2025-04-27 07:14:26 -07:00
Mitchell Hashimoto	f0339d5e5b	ci: iTerm2 colorscheme update should update flatpak deps	2025-04-27 07:01:52 -07:00
Mitchell Hashimoto	c7b8fd1354	flatpak: update dependencies	2025-04-27 07:00:24 -07:00
Mitchell Hashimoto	17441de37f	Update iTerm2 colorschemes (#7210) ... Upstream revision: 5233095e44	2025-04-27 06:53:06 -07:00
Mitchell Hashimoto	d4acdf44a9	z2d 0.6.0 -> 0.6.1 for security fix (#7211) ... version 0.6.0 of z2d has a security vulnerability and the author suggests upgrading (randomly saw this in the zig discord) https://github.com/vancluever/z2d/security/advisories/GHSA-mm4c-p35v-7hx3 I don't know enough about how ghostty uses to it to say if it could be affected also updates that Context no longer returns an error type this says it was in the 0.6.0 changes which ghostty was already pinned to (it seems like that the tag might have been updated or something im not sure) you can see it listed as a change in 0.6.0 below https://github.com/vancluever/z2d/blob/main/CHANGELOG.md I'm not sure if any other changes are required I ran a `zig build` and `zig build test` and things seem to be fine on my end ~~I'm not sure I updated the zon nix stuff correctly I just ran the command in jcollie readme `nix run github:jcollie/zon2nix#zon2nix -- --nix=build.zig.zon.nix build.zig.zon`~~ looks like I should have just ran the script ps: sorry for the direct ping mitchell (I thought this might be important that you look at it)	2025-04-27 06:51:23 -07:00
rhodes-b	ba5c773f0f	update flatpak packages	2025-04-27 00:05:10 -05:00
rhodes-b	b1561112d0	run the nix cache script	2025-04-27 00:03:00 -05:00
rhodes-b	bbbe81efc5	z2d context no longer has err return	2025-04-26 23:51:04 -05:00
rhodes-b	0c8339d2da	update z2d to 0.6.1	2025-04-26 23:39:02 -05:00
mitchellh	12f48419b6	deps: Update iTerm2 color schemes	2025-04-27 00:14:50 +00:00
Mitchell Hashimoto	38445dca2a	feat: beautify macOS command palette (#7179) ... Resolve 1. of #7173 <img width="1126" alt="image" src="https://github.com/user-attachments/assets/8904b09f-42f6-4f26-a722-c92dad8e2933" /> Changes made: 1. Change shortcut from `String` to `[String]` so its easier to iterate over it. 2. Overlay background color on top of an `ultraThinMaterial` for better aesthetic. 3. Reorganize and beautify the spacings and paddings. 4. Unhide the scrollbar. 5. Reorder the modifier keys to Control, Option, Shift and then Command. <https://leancrew.com/all-this/2017/11/modifier-key-order/> 6. Style shortcut keys to resemble macOS menu bar items, using corresponding symbols and fixed-width for alignment.	2025-04-25 12:01:01 -07:00
Mitchell Hashimoto	2b4d89e11f	macOS: scheme doesn't need to be state	2025-04-25 11:42:12 -07:00
Friedrich Stoltzfus	77f5fc34f1	Add config color palette C bindings ... C bindings to expose the color palette to Swift for macOS.	2025-04-25 14:10:35 -04:00
Aaron Ruan	1acb1715c3	replace NSVisualEffectView with ultraThinMaterial plus a background color	2025-04-25 10:42:22 +08:00
Aaron Ruan	3827ce9e4c	feat: beautify command palette	2025-04-24 12:46:38 +08:00
Mitchell Hashimoto	4e91d11a60	macOS: add descriptions for PgUp, PgDown, End, and Home keys (#7177) ... Resolves #7174. The PgUp, PgDown, End, and Home keys were not being assigned a description in the `KeyboardShortcut` extension.	2025-04-23 13:32:51 -07:00
Friedrich Stoltzfus	f58fba54a0	macOS: add descriptions for PgUp, PgDown, End, and Home keys ... These keys were not being assigned a description in the KeyboardShortcut extension. This caused problems for the macOS command pallete.	2025-04-23 16:05:51 -04:00
Mitchell Hashimoto	afd8d10b82	macOS: Command palette has no selection by default, selection wraps (#7175) ... #7173 (1) The command palette no longer has any selection by default. If and when we introduce most recently used commands, defaulting to that would make sense. A selection only appears when the arrow keys are used or the user starts typing. (2) The selection with arrow keys now wraps, so if you press "down" on the last option, it will wrap to the first option, and if you press "up" on the first option, it will wrap to the last option. This matches both VSCode and Zed.	2025-04-23 10:50:13 -07:00
Mitchell Hashimoto	9bfe4544bf	macOS: Command palette has no selection by default, selection wraps ... #7173 (1) The command palette no longer has any selection by default. If and when we introduce most recently used commands, defaulting to that would make sense. A selection only appears when the arrow keys are used or the user starts typing. (2) The selection with arrow keys now wraps, so if you press "down" on the last option, it will wrap to the first option, and if you press "up" on the first option, it will wrap to the last option. This matches both VSCode and Zed.	2025-04-23 10:37:20 -07:00
Mitchell Hashimoto	f2c798d319	macOS: Command Pallete Improvements (#7171) ... As discussed in #7165, this PR resolves two issues with the command pallete on macOS. 1. The flashing of a command passing out of view was caused by the `withAnimation` function. Removing this closure resolved this issue. 2. The current implementation kept the selected command anchored to the middle of the pallete. However, most command pallates allow you to key through the visible options, only scrolling when your selection hits the boundary. I resolved this by removing the `anchor: .center` parameter for the `scrollTo` command.	2025-04-23 08:35:33 -07:00
Mitchell Hashimoto	ba6ed1f3c5	snap: build from source tarball (#6831) ... Eliminates the need for `blueprint-compiler`, which isn't quite new enough on the snap builder.	2025-04-23 06:58:14 -07:00
Jeffrey C. Ollie	6bd9e35cd6	snap: build from source tarball	2025-04-23 08:10:01 -05:00
Friedrich Stoltzfus	b4b2b10328	macOS: command pallete scroll improvements ... Removes the withAnimation closure which caused flashing when scrolling up or down with arrow keys. Also removes the center anchor to behave more like other command palletes (e.g., Zed, Raycast).	2025-04-22 16:12:09 -04:00
Mitchell Hashimoto	f5b5a36835	Fix flatpak packaging to a working state (#6678) ... This should make testing Flatpak builds a lot easier. To build, enter `flatpak/` directory and run: flatpak-builder --repo=repo builddir com.mitchellh.ghostty.yml alternatively, using org.flatpak.Builder flatpak: flatpak run -p org.flatpak.Builder \ --repo=repo \ builddir \ com.mitchellh.ghostty.yml The resulting flatpak can be installed using flatpak install ./repo com.mitchellh.ghostty Credit of AppStream metadata goes to @yorickpeterse.	2025-04-22 12:19:55 -07:00
Mitchell Hashimoto	e6c2105a2b	ci: fix up flatpak deps	2025-04-22 12:02:24 -07:00
Mitchell Hashimoto	946cf5a375	update flatpak build hash	2025-04-22 10:57:17 -07:00
Mitchell Hashimoto	d7256c71c4	ci: flatpak	2025-04-22 10:56:10 -07:00