LangLangBart

Maybe you can test if this works for you. ```zsh fzf --preview "basename {} | grep {q} -i --color=always" --preview-window 'nohidden:wrap' # {q} is replaced to the current query string...

As a workaround you could use the `reload` action, see #1750 for details. ```sh rtf() { GREP_COMMAND="grep --color=always --line-number . ${@:?Provide at least one argument.}" FZF_DEFAULT_COMMAND="$GREP_COMMAND | cut -d :...

Referencing ticket: #156062 Exactly what I was looking for. The path is truncated from the left, like in macOS Spotlight. Tested this patch with the latest dev version and it...

I deleted my forked repository, which consequently closed this Pull Request (PR). GitHub does not permit reopening a PR in such a scenario, so I created a new PR, #3593.

I understand. I will make the necessary adjustments.

> zle vi-fetch-history -n ${num%\*} Is this truly necessary? In my testing, `zle vi-fetch-history` appears to handle the optional asterisk correctly. It was primarily the above regex that was overly...

> Probably not. But the official document for `vi-fetch-history` doesn't mention anything about > allowing non-numeric suffixes, so I think it's safer to do it even though it's not needed...

> I am on zsh and still getting the number asterisk pattern on version `0.46.1` when selecting > failed commands. I couldn't reproduce the issue. Could you please confirm that...

> ability to remove commands from history > sed -i "\${linenum}d" "$HISTFILE" The idea of removing entries based on their number may not be as straightforward as it seems, given...

The dedicated widget by `cenk1cenk2`, which makes use of the plugin from `marlonrichert`, works well and might be the best solution yet for removing entries from the history file using...