-
Notifications
You must be signed in to change notification settings - Fork 529
Is it possible to have blocks of text in my cheat sheets #954
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm not sure I understand your use case entirely, but have you considered writing these blocks of text into a .txt, and then adding a navi snippet such as |
support for multiline code-blocks would be great. I find it hard to maintain them after squashing them all in one line |
@kqvanity Multiline code-block is already supported. See multiline-snippets. # multiline sample ``` echo hello \ world ``` |
The multiline snippets doesn't show as multiple lines in the fuzzy search table, it's Also, it doesn't seem possible to have the comment span multiple lines, is it ? |
The main suggestion therefore becomes 2 requests:
|
We can write multiple lines of comments using
Although I think we cannot have multiple lines code blocks in the fuzzy search table, it can be configured to display it in the preview. |
…g on item.comment
…g on item.comment
…locks with multiple lines (only fzf supported)
I like to use cheat sheets not only for command lines, but also for any block of code or text.
A naive example of cheat-block would be on how to git rebase:
Another example would be to have a compact list of arguments for a command:
I also have cheats like that don't correspond to commands that should be executed:
And a last example:
The current implementation of navi doesn't allow for this type of cheat sheets.
A workaround is to split each line into multiple lines, with a common prefix, but lines can get messed-up in the fuzzy search. And it doesn't provide a compact result.
It would be great to have the possibility to have
navi
dump a block of text on stdout, such that it can be handily peaked for command composition right after.The text was updated successfully, but these errors were encountered: