-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Open
Description
When setting ZSH_HIGHLIGHT_STYLES[path]='none'
I think the whole path checking should be disabled. Slightly related to #144, I am having some problems with a FUSE mount, too.
What happens is that when I'm midway writing the path the FUSE mount keeps trying to find the path that doesn't exist. And this is pretty slow.
I don't really need the path highlighting and tried to set the style to 'none'
but noticed that it doesn't cut it.
So _zsh_highlight_main_highlighter_check_path()
should return 1 immediately if path style is set to 'none'
.
_zsh_highlight_main_highlighter_check_path()
{
[[ "$ZSH_HIGHLIGHT_STYLES[path]" == "none" ]] && return 1
...
Or if there's another way, please tell me. :)
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
danielshahaf commentedon Oct 3, 2016
Does
none
mean "fall back tozle_highlight[default]
", or does it mean "fall back to the terminal emulator's default colors (overridingzle_highlight[default]
)"?(My reading of zshzle(1) is that
none
means the latter, but as implemented it means the former.)If it's the former, then omitting a
none
entry fromregion_highlight
is a no-op, and your suggested fix makes sense. If it's the latter, we still need to add something toregion_highlight
, but we could use[[ $ZSH_HIGHLIGHT_STYLES[path] = $ZSH_HIGHLIGHT_STYLES[default] ]]
as the short-circuit condition, as in the following patch.The diff currently breaks all tests, see path-redirection2.zsh for why. (So it needs some test harness changes)
Action items:
none
. Clarify zshzle(1).