murex icon indicating copy to clipboard operation
murex copied to clipboard

theme colors configuration

Open orefalo opened this issue 2 years ago • 2 comments

Describe the problem:

other shells allow for precise color customizations, see below

# Syntax Highlighting Colors
set -U fish_color_normal $foreground
set -U fish_color_command $cyan
set -U fish_color_keyword $pink
set -U fish_color_quote $yellow
set -U fish_color_redirection $foreground
set -U fish_color_end $orange
set -U fish_color_error $red
set -U fish_color_param $purple
set -U fish_color_comment $comment
set -U fish_color_selection --background=$selection
set -U fish_color_search_match --background=$selection
set -U fish_color_operator $green
set -U fish_color_escape $pink
set -U fish_color_autosuggestion $comment

# Completion Pager Colors
set -U fish_pager_color_progress $comment
set -U fish_pager_color_prefix $cyan
set -U fish_pager_color_completion $foreground
set -U fish_pager_color_description $comment
set -U fish_pager_color_selected_background --background=$selection

Since shell users are console ASCII lovers, I would recommend allowing similar configurations in Murex. I realize the ask goes beyond coloring, the prompt must be able to identify the type of arguments such as commands, pipes, redirections..etc which I believe it already does.

ie. Fish:

CleanShot 2023-08-14 at 09 58 29

vs Murex

CleanShot 2023-08-14 at 09 59 29

orefalo avatar Aug 14 '23 07:08 orefalo

Agreed. This is part of the long term plan. In fact that part of the code is already abstracted ready to expose: https://github.com/lmorg/murex/blob/master/utils/parser/parser.go

I don't have an ETA for it though. Do you see this as something of high importance?

lmorg avatar Aug 14 '23 09:08 lmorg

No, coloring is low priority.

I am just going over all my fish scripts and trying to migrate them.

orefalo avatar Aug 14 '23 10:08 orefalo