Package Details: ghostty-shell-integration-git 1.1.2.r1500.gf1f9d5e-1

Git Clone URL: https://aur.archlinux.org/ghostty-git.git (read-only, click to copy)
Package Base: ghostty-git
Description: Shell integration scripts for ghostty
Upstream URL: https://github.com/ghostty-org/ghostty
Licenses: MIT
Conflicts: ghostty-shell-integration
Provides: ghostty-shell-integration
Submitter: gpanders
Maintainer: alerque
Last Packager: gpanders
Votes: 16
Popularity: 0.109382
First Submitted: 2024-06-07 14:51 (UTC)
Last Updated: 2025-07-03 01:06 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

markoff commented on 2025-02-27 12:02 (UTC) (edited on 2025-02-27 12:03 (UTC) by markoff)

Is this package installing for you guys? It is giving me errors:

error: the following build command failed with exit code 1:
/home/markoff/.cache/yay/ghostty-git/src/ghostty/.zig-cache/o/08416ebc7667c9532c0188f7d3db5c9c/build /usr/bin/zig /home/markoff/.cache/yay/ghostty-git/src/ghostty /home/markoff/.cache/yay/ghostty-git/src/ghostty/.zig-cache /home/markoff/.cache/zig --seed 0xba85c110 -Z6ff3699b04c46268 --summary all --prefix /usr --system -Doptimize=ReleaseFast -Dgtk-wayland=true -Dgtk-x11=true -Dcpu=baseline -Dpie=true -Demit-docs -Dversion-string=1.1.2-r242.gc7938af-1-arch

Radicaltray commented on 2025-02-24 13:45 (UTC)

blueprint-compiler is missing from make dependencies?

gpanders commented on 2025-02-14 16:56 (UTC)

fetch-zig-cache.sh was added back an hour ago https://github.com/ghostty-org/ghostty/pull/5762.

warmwaffles commented on 2025-02-14 14:27 (UTC)

I ditched the nix build stuff entirely. It builds just fine without it.

@@ -33,7 +33,6 @@ sha256sums=('SKIP')

 prepare() {
        cd "$_pkgbase"
-       ZIG_GLOBAL_CACHE_DIR="$srcdir/zig-global-cache/" ./nix/build-support/fetch-zig-cache.sh
 }

 pkgver() {
@@ -47,7 +46,6 @@ build() {
        DESTDIR=build zig build \
                --summary all \
                --prefix "/usr" \
-               --system "$srcdir/zig-global-cache/p" \
                -Doptimize=ReleaseFast \
                -Dgtk-wayland=true \
                -Dgtk-x11=true \

Toesmasher commented on 2025-02-12 12:56 (UTC)

There seems to be a breaking change upstream, fetch-zig-cache.sh has been removed. The change seems to have occurred in 3a8c934b1937762e00de1959d9f25a25794b4d85.

nezu commented on 2025-02-03 13:16 (UTC)

@munim this is a -git package, just rebuild

munim commented on 2025-01-31 11:45 (UTC) (edited on 2025-01-31 11:45 (UTC) by munim)

v1.1 released yesterday. Waiting for AUR update :)

https://github.com/ghostty-org/ghostty/releases/tag/v1.1.0

alerque commented on 2025-01-16 12:58 (UTC)

@adrinux Upstream seems to be miss-handling resources based on what is or isn't available user home directories; that has nothing to do with this packaging.

adrinux commented on 2025-01-15 10:17 (UTC)

The missing resources (including themes) is an ongoing upstream issue https://github.com/ghostty-org/ghostty/discussions/3500

Ghostty reported it was looking in $HOME/.config/ghostty for the themes. Since they're all in /usr/share/themes I just added a symlink as a workaround.

cd ~/.config/ghostty
ln -s /usr/share/ghostty/themes themes

My version is 1.0.1-r428

alerque commented on 2025-01-13 22:32 (UTC) (edited on 2025-01-13 22:43 (UTC) by alerque)

@yamafaktory As of yesterday when I was working on overhauling this, the file list in the final package does include the themes. If it doesn't now that's likely an upstream bug in Git HEAD, not in this packaging, we're currently coping everything in the build directory, then selectively removing a couple bits that we're putting in split packages. We're not removing themes.

Possibly upstream changed where they look for resources vs. where they build them to. But it isn't necessarily incumbent on this packaging to fix upstream bugs.

Edit: I just rebuilt the package now and far from not having themes, it has 16 more themes than yesterday when I built it. How exactly are you building the packages? And what exact version do you get? It is possible there was a problem upstream post 1.0.1.r379 (yesterday) and pre 1.0.1.r418 (now).