Skip to content

glissues v0.0.7

Choose a tag to compare

View all tags
@ftorrresd ftorrresd released this 27 Apr 15:01
· 2 commits to main since this release
v0.0.7
632270c

Overview

This release focuses on a smoother startup experience and a much better workflow for writing longer issue descriptions and comments.

The biggest change is support for opening issue and comment bodies in your external editor, using the same editor resolution order Git users expect. The initial loading screen has also been redesigned with
clearer progress feedback, improved visibility, and a simpler product-focused presentation.

Highlights

  • Added external editor support for editing issue bodies and comment bodies.
  • Redesigned the startup loading screen with animated branding and a progress bar.
  • Added visible issue loading progress counters during startup preload.
  • Improved splash-screen readability and removed unnecessary GitLab-specific wording.
  • Updated the main mode label from BROWSE to glissues.

New Features

External editor support for issue and comment bodies

Issue and comment body editing now opens in an external editor instead of relying only on inline TUI text editing.

glissues resolves the editor in this order:

  1. $GIT_EDITOR
  2. git config core.editor
  3. $VISUAL
  4. $EDITOR
  5. vi

This makes longer Markdown editing more comfortable, especially for issue descriptions and detailed comments.

Issue editor behavior

When creating or editing an issue:

  • The title is still edited inline inside glissues.
  • Pressing Tab or Enter from the title field opens the body in the external editor.
  • When focused on the body field:
    • Enter reopens the external editor.
    • e also reopens the external editor.
    • Tab returns focus to the title field.
  • Ctrl-s saves the issue.
  • Esc keeps the draft locally.

Comment editor behavior

When adding a comment:

  • The comment body opens directly in the external editor.
  • After returning to glissues, the comment draft is shown in the popup.
  • Enter reopens the external editor.
  • Ctrl-s saves the comment.
  • Esc keeps the draft locally.

This is especially useful for multi-line comments, Markdown formatting, code blocks, checklists, and longer issue descriptions.

Startup and Loading Improvements

Redesigned startup splash screen

The initial loading screen has been redesigned to feel more polished and readable.

Changes include:

  • New centered GLISSUES splash screen.
  • Animated ASCII-style face/status text.
  • Framed popup layout.
  • Cleaner visual hierarchy.
  • Less noisy wording.

Progress bar during initial preload

Startup now displays a progress bar while loading issue data.

The splash screen shows:

  • A visual progress bar.
  • A numeric counter.
  • The current loading message.

This makes it clearer that glissues is actively preloading data instead of appearing idle during startup.

Issue counter visibility improvements

The progress counter and bar were adjusted to remain visible and readable across the loading flow.

Fixes include:

  • Ensuring the progress bar is always displayed.
  • Ensuring the counter is always displayed.
  • Increasing contrast for progress information.
  • Removing the redundant PROGRESS label.

UI Polish

Mode label update

The main mode label was changed from:

BROWSE

to:

  glissues

This makes the UI feel more branded and less mode-heavy during normal browsing.

Simpler loading copy

Loading messages were simplified from GitLab-specific wording to more general application wording.

For example:

  Loading GitLab data

is now:

  Loading data

This keeps the startup experience cleaner and avoids redundant wording, since GitLab is already implied by the application.

Fixes

  • Fixed startup progress bar visibility.
  • Fixed startup progress counter visibility.
  • Improved progress bar and counter contrast.
  • Removed the unused spinner frame helper.
  • Removed redundant splash-screen labels.
  • Simplified splash-screen text and removed unnecessary GitLab references.

User-facing Behavior Changes

Body editing now prefers an external editor

Issue body and comment body editing now uses an external editor workflow.

If you want a specific editor, configure one of the following:

  export GIT_EDITOR="nvim"

or:

  git config --global core.editor "nvim"

Other examples:

  export EDITOR="vim"
  export VISUAL="code --wait"
  export GIT_EDITOR="nano"

For GUI editors, make sure the command waits until the file is closed before returning to glissues.

For example:

  export GIT_EDITOR="code --wait"

Upgrade Notes

No configuration migration is required.

Existing project configuration, stored tokens, themes, filters, and project metadata continue to use the same config file:

  ~/.config/glissues/config.toml

Stored GitLab private tokens are still saved in plain text in the local config file.

Commit Summary

Changes since v0.0.6:

  • 632270c Add external editor support for issue/comment body editing
  • 58342e5 fix: change loading message from "Loading GitLab data" to "Loading data"
  • 172497a fix: remove PROGRESS label from splash screen
  • b258ced fix: make progress bar and counter more visible on splash screen
  • 4854458 fix: ensure progress bar and counter always display on splash screen
  • 935c5ee feat: display issue counter on splash screen
  • 99e7c87 feat: add frame border to splash screen
  • 6d8b8ae fix: remove unused spinner_frame method
  • 14efb2f fix: simplify splash screen and remove gitlab mention
  • 77e88c9 feat: redesign splash screen with animated ascii art and progress bar
  • ff02b53 feat: add elegant splash screen during initial data loading
  • 2fde1aa style: update mode label from BROWSE to glissues

Full Changelog

  https://github.com/ftorrresd/glissues/compare/v0.0.6...v0.0.7
Assets 5
Loading