Skip to content

pkgforge-community/ghostty-appimage

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

36 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Ghostty Logo AppImage Logo
Ghostty AppImage
License: MIT Forks Stars Build Status Open Issues Pull Requests
GitHub Downloads (all assets, all releases) GitHub Downloads (all assets, latest release) GitHub Release GitHub Release Date Contributors

This repository provides build scripts to create a Universal AppImage for Ghostty. This unofficial build offers an executable AppImage compatible with any Linux distribution.

Ghostty Source Code: Click Here

🚀 Quick Start

  1. Download the latest AppImage from the releases section.
  2. Follow the installation instructions below to run the AppImage.

⚙️ Installation

Command Line (Manual)

Run the following commands in your terminal:

# Download the latest AppImage package from releases
wget https://github.com/psadi/ghostty-appimage/releases/download/${VERSION}/Ghostty-${VERSION}-${ARCH}.AppImage

# Make the AppImage executable
chmod +x Ghostty-${VERSION}-${ARCH}.AppImage

# Run the AppImage
./Ghostty-${VERSION}-${ARCH}.AppImage

# Optionally, add the AppImage to your PATH for easier access

# With sudo for system wide availability
sudo install ./Ghostty-${VERSION}-${ARCH}.AppImage /usr/local/bin/ghostty

# Without sudo, XDG base spec mandate
install ./Ghostty-${VERSION}-${ARCH}.AppImage $HOME/.local/bin/ghostty

# Now you can run Ghostty from anywhere using the command:
# ghostty

Note: By using AM/AppMan, PATH config done automatically when you install appimages with it.

Command Line (Auto)

Ghostty AppImage is also available via Soar which automatically handles the install, upgrade and desktop integration process

# Install
soar install ghostty

# Upgrade
soar update ghostty

# Uninstall
soar remove ghostty

Graphical

  1. Download the latest AppImage package from the releases section.
  2. Locate the downloaded file in your file explorer (e.g., Nautilus, Thunar, PCManFM).
  3. Right-click the downloaded file and select Properties.
  4. Navigate to the Permissions tab and check the box that says Allow executing file as program/Executable as Program.
  5. Close the properties window and double-click the AppImage file to run it.

Step 1 Step 2

⏫ Updating

Since AppImages are self-contained executables, there is no formal installation process beyond setting executable permissions.

Update manually:

  1. Download the latest AppImage package from the releases section.
  2. Follow the same steps as in the Installation section to make it executable and run it.

Update automatically:

  1. Use AppImageUpdate which reads the update information in the AppImage. This is a low level tool.
  2. Use a higher level tool that uses AppImageUpdate, like AM or appimaged daemon, these tools also automatically handle desktop integration.

🖥️ Supported System Architectures

This AppImage supports the following architectures:

# Architecture Status Availability
1 x86_64 🟢 Available
2 aarch64 🟢 Available

Notes:

  • x86_64: Widely used in modern desktops and servers, supporting 64-bit processing.
  • aarch64: 64-bit ARM architecture, planned for future support in cloud computing environments.

🛠️ Troubleshooting

Known Issues

  1. Failed to create EGL Display

    Fix (Interim): Fallback to x11 backend by running the AppImage from one of the below following options,

    # Option 1
    ❯ GDK_BACKEND=x11 ./Ghostty-${VERSION}-${ARCH}.AppImage
    
    # Option 2export GDK_BACKEND=x11
    ❯ ./Ghostty-${VERSION}-${ARCH}.AppImage
    
    # Option 3: Add `export GDK_BACKEND=x11` to your .bashrc or .zshrc and launch the appimage normally
  2. TERMINFO xterm-ghostty not-set/breaks functionality

    Fix: Set the TERMINFO value to xterm-256color at runtime by running the AppImage as follows,

    # Option 1
    ❯ TERM=xterm-256color ./Ghostty-${VERSION}-${ARCH}.AppImage
    
    # Option 2: Add `export TERM=xterm-256color` to your .bashrc or .zshrc and launch the appimage normally

If you encounter any errors, check the terminal for error messages that may indicate missing dependencies or other issues

🤝 Contributing

Contributions & Bugfixes are welcome. If you like to contribute, please feel free to fork the repository and submit a pull request.

For any questions or discussions, please open an issue in the repository.