Replies: 3 comments 4 replies
-
|
I think option cat my_app.log | fzf --wrap --nth 2..
|
Beta Was this translation helpful? Give feedback.
-
One workaround is to include the timestamp in the info using cat /dev/urandom |
xxd -c 200 |
head -10 |
FZF_DEFAULT_OPTS_FILE='' FZF_DEFAULT_OPTS='' fzf \
--color 'hl:201:dim,hl+:201:bold' \
--info-command $'printf "%b%s%b %s" "\e[35;1m" {1} "\e[m" $FZF_INFO' \
--multi \
--nth 2.. \
--query abc
Footnotes |
Beta Was this translation helpful? Give feedback.
-
|
This is currently not possible. While I'm open to the idea, implementing this is not going to be trivial, so I can't make any promises. In these cases, I usually reformat each line into a multi-line entry, so that the timestamp (and some other metadata) is always visible on a separate line. cat my_app.log | perl -pe 's/\n/\0/s; s/ /\n ⋅ /' | fzf --read0 --gap |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
Hi, thanks for your hard work on fzf.
My use case:
I want to make a UI with fzf where in each entry, there is a timestamp, and very long text on the right side.
But so that, when you type, the timestamp or "prefix" would remain visible always, even the right side is fuzzy matched somewhere.
With the previous command, it behaves like this:
The timestamp becomes hidden, even when just searching the second the second part with
--nth 2..Maybe there could be some flag that makes it so that the non-
--nth 2..part is always visible.Maybe this is already possible. Thank you in advance.
Beta Was this translation helpful? Give feedback.
All reactions