https://github.com/z-shell/fast-syntax-highlighting/blob/1e21d55703ebb9bc9c006dbce1d2b4dd5453323d/tests/main.zunit#L100

        # TODO: handle the non-SVN path's specifics

undefined

# TODO: map-outdates e.g: pnpm

https://github.com/z-shell/fast-syntax-highlighting/blob/6bb20bd08e0e6b77a782e0facadcfa09e685ca91/fast-highlight#L169

https://github.com/z-shell/fast-syntax-highlighting/blob/a3242a93399535faccda4896ab5c61a7a6dca1fe/→chroma/-git.ch#L257

Feature description

Title says it all.

Related Code

No response

Additional Context

No response

Self-service

• I'd be willing to address this documentation request myself.

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines.

Are you familiar with Contributor Covenant Code of Conduct?

• I have read the Contributor Covenant Code of Conduct.

Contact Details

No response

Environment

OSTYPE=darwin21.3.0 CPUTYPE=arm64 / MACHINE_TYPE=arm ZSH_VERSION=5.9

Expected behavior

Press <tab> and show nothing:

time -<tab>

Current behavior

>  time -
-                                      -fast-highlight-fill-option-variables  -fast-highlight-process
-fast-highlight-check-path             -fast-highlight-init                   -fast-highlight-string
-fast-highlight-check-path-handler     -fast-highlight-main-type              -fast-highlight-string-process
-fast-highlight-dollar-string          -fast-highlight-math-string            -fsh_sy_h_shappend

Steps to reproduce

time -<tab>

Code snippet

I use oh-my-zsh:

plugins=(... F-Sy-H)

Aditional information

None.

Self-service

• I'd be willing to address this documentation request myself.

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines.

Are you familiar with Contributor Covenant Code of Conduct?

• I have read the Contributor Covenant Code of Conduct.

Contact Details

No response

Environment

OSTYPE=linux-gnu CPUTYPE=x86_64 / MACHINE_TYPE=x86_64 ZSH_VERSION=5.9

Expected behavior

(with default theme)

With the prompt git commit some/file.lua

👉 The given file to commit is colored with 'correct-subtle'.

With the prompt git commit some/folder/with/changes/
👉 The given path to commit SHOULD BE colored with 'correct-subtle' as well

Current behavior

With the prompt git commit some/folder/with/changes/

👉 The given path to commit is instead colored with 'incorrect-subtle', so looks like an error even though is completely valid git-wise.

Steps to reproduce

N/A ?

Code snippet

No special config, the plugin is loaded with zi light /path/to/F-Sy-H-plugin

Aditional information

N/A ?

Self-service

• I'd be willing to address this documentation request myself.

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines.

Are you familiar with Contributor Covenant Code of Conduct?

• I have read the Contributor Covenant Code of Conduct.

Contact Details

here on github

Env: OSTYPE=linux-gnu CPUTYPE=x86_64 MACHINE_TYPE=x86_64 ZSH_VERSION=5.8.1

a rapid check of the code seems to show that I could set the FAST_WORK_DIR to change where the state of FSH is stored, by trying that:

FAST_WORK_DIR=~/.long_term_cache/zsh--fast-syntax-highlighting
echo "FAST_WORK_DIR (before zi): $FAST_WORK_DIR"

zi light z-shell/F-Sy-H

echo "FAST_WORK_DIR (after zi): $FAST_WORK_DIR"

Starting a new shell I get:

FAST_WORK_DIR (before zi): /home/lesell_b/.long_term_cache/zsh--fast-syntax-highlighting
FAST_WORK_DIR (after zi): /home/lesell_b/.cache/fsh

Which seems wrong...

In addition to that, it seems that the chroma system assumes the theme is stored in ~/.cache/fsh, and does not check what FAST_WORK_DIR is set to.
I tried to fix that in #24, but further testing showed the weird inconsistency above.

Description

As per #22 antigen requires special flags to indicate the use of main as the primary branch.

Instructions should specify antigen bundle z-shell/F-Sy-H --branch=main

Select the area that is associated with this issue.

ZI (this repository)

Self-service

• I'd be willing to address this documentation request myself.

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines.

Are you familiar with Contributor Covenant Code of Conduct?

• I have read the Contributor Covenant Code of Conduct.

Contact Details

[email protected]

# TODO: API update

https://github.com/z-shell/fast-syntax-highlighting/blob/29e605d7a5dcefd9620121799ebc1a899da2c51d/fast-syntax-highlighting.plugin.zsh#L365

Environment

OSTYPE=linux-gnu CPUTYPE=x86_64 / MACHINE_TYPE=x86_64 ZSH_VERSION=5.9

Expected behavior

For example, git subcommands should be highlighted.

Current behavior

No command-specific highlighting. Chroma files/functions not found:

$ chroma/-git.ch
zsh: chroma/-git.ch: function definition file not found

Steps to reproduce

Install F-Sy-H without package manager. For example, as a git submodule: https://github.com/amezin/zdotdir

Type "git checkout" in prompt, "checkout" isn't highlighted

Code snippet

source "${ZDOTDIR}/fast-syntax-highlighting/F-Sy-H.plugin.zsh"

# Adding the following line makes git-specific highlighting work
fpath+=("${ZDOTDIR}/fast-syntax-highlighting")

Aditional information

chroma should likely be inside functions

Self-service

• I'd be willing to address this documentation request myself.

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines.

Are you familiar with Contributor Covenant Code of Conduct?

• I have read the Contributor Covenant Code of Conduct.

Contact Details

No response

aliased $ is correctly parsed as an alias, but aliased ] is parsed as "unexpected symbol."

the ]s at the beginning of the line are my prompts.

Prepare for upcoming releases.
1 - CI
2 - Syntax
3 - Documentation

Environment

OSTYPE=linux-gnu CPUTYPE=x86_64 / MACHINE_TYPE=x86_64 ZSH_VERSION=5.9

Expected behavior

With this global alias:
alias -g NOOUT=">/dev/null"

When I use it in a simple command like echo foo NOOUT it shows like this (with default theme):

Current behavior

When I use it in a git command like git commit --dry-run NOOUT the chroma identifies the alias as an invalid token and uses color 'incorrect-subtle':

😞

Steps to reproduce

N/A?

Code snippet

No special config, the plugin is loaded with zi light /path/to/F-Sy-H-plugin

Aditional information

N/A?

Self-service

• I'd be willing to address this documentation request myself.

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines.

Are you familiar with Contributor Covenant Code of Conduct?

• I have read the Contributor Covenant Code of Conduct.

Contact Details

here on github

https://github.com/z-shell/fast-syntax-highlighting/blob/ee7ab48d292b2b5d3829e08b54b79ddd50bccd0d/test/to-parse.zsh#L551

I just saw that https://github.com/zdharma/fast-syntax-highlighting got created again and now points to this repo (https://github.com/z-shell/fast-syntax-highlighting) as upstream repo. Are you the real zdharma and is this now again the official upstream? https://github.com/zdharma-continuum/fast-syntax-highlighting got created in the meantime and accepted in the community.

If you are the real zdharma, can we rely on you not again deleting this repo?

More context for the drama: https://www.reddit.com/r/zsh/comments/qinb6j/httpsgithubcomzdharma_has_suddenly_disappeared_i/

I think it would be helpful for you to give us an answer on all this and not just pretend like it never happened.

        # TODO: handle the SVN path's specifics

undefined

This repository uses main as its default branch whereas zgen by itself searches only for master.

Hence, zgen load z-shell/F-Sy-H in the README should be replaced with zgen load z-shell/F-Sy-H . main or something like that.

On an unrelated note, when you try to create a new issue you're prompted to select the type, and "Community Discussion" leads to https://github.com/org/z-shell/discussions which doesn't exist.

TaskBoard

• Add docs to issue template so it's never missed:
  https://z.digitalclouds.dev/ecosystem/plugins/f-sy-h