Describe the bug The original issue in #419 seems fixed, but I'm missing the placeholders when filling in my commands

To Reproduce Steps to reproduce the behavior:

1. navi (completion should contain <placeholder>
2. Select command
3. Notice <placeholder>: is missing

Expected behavior

• <placeholder>: should appear
• Number of commands should be consistent (See Additional context)

Screenshots

2.12.1

> ./navi --version
navi 2.12.1
> ./navi                                                                                                                                                                             
~ normal  < 1/32 +S
» cal                                normal calendar        cal -B <before> -A <after>  ⠀

# after selecting `cal`
~   < 1/1 +S
»

2.10.0

> navi --version
navi 2.10.0
> navi 
~ normal  < 1/26 +S
» cal                                normal calendar        cal -B <before> -A <after>  ⠀

# after selecting `cal`
before:   < 0/0 +S

Versions:

• OS: macOS
• Shell Version: fish 3.1.2, bash 5.0.18, zsh 5.7.1

Additional context

I also noticed

• 2.12.1 shows 32 commands, completion shows 1/1
• 2.10.0 shows 26 commands, completion shows 0/0

maybe related to the bug?

Describe the bug An error occurs when adding cheats for the first time

To Reproduce Steps to reproduce the behavior:

1. execute: brew install denisidoro/tools/navi
2. execute: navi repo add denistore/cheat
3. Error

$ brew install denisidoro/tools/navi
$ navi repo add denistore/cheat
Cloning https://github.com/denistore/cheat into /Users/rtoledo/Library/Application Support/navi/cheats/tmp...

thread 'main' panicked at 'failed to clone: unsupported URL protocol; class=Net (12)', src/flows/repo.rs:57:19
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Expected behavior Cheats should be added

Versions:

• OS: macOS 10.15.1 (19B2093)
• GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin19) Copyright (C) 2007 Free Software Foundation, Inc.

Describe the bug Error while trying to install from cargo or install script. Both give the same error.

To Reproduce Just run the required installation code.

Expected behavior To install it.

Screenshots

$ cargo install navi
    Updating crates.io index
  Installing navi v2.17.0
   Compiling libc v0.2.100
   Compiling cfg-if v1.0.0
   Compiling proc-macro2 v1.0.28
   Compiling unicode-xid v0.2.2
   Compiling syn v1.0.75
   Compiling version_check v0.9.3
   Compiling memchr v2.4.1
   Compiling log v0.4.14
   Compiling autocfg v1.0.1
   Compiling ppv-lite86 v0.2.10
   Compiling signal-hook v0.3.9
   Compiling serde_derive v1.0.128
   Compiling scopeguard v1.1.0
   Compiling serde v1.0.128
   Compiling smallvec v1.6.1
   Compiling unicode-segmentation v1.8.0
   Compiling hashbrown v0.11.2
   Compiling bitflags v1.3.2
   Compiling utf8parse v0.1.1
   Compiling regex-syntax v0.6.25
   Compiling lazy_static v1.4.0
   Compiling anyhow v1.0.43
   Compiling either v1.6.1
   Compiling linked-hash-map v0.5.4
   Compiling remove_dir_all v0.5.3
   Compiling unicode-width v0.1.8
   Compiling termcolor v1.1.2
   Compiling same-file v1.0.6
   Compiling dtoa v0.4.8
   Compiling os_str_bytes v3.1.0
   Compiling vec_map v0.8.2
   Compiling strsim v0.10.0
   Compiling instant v0.1.10
   Compiling lock_api v0.4.4
   Compiling proc-macro-error-attr v1.0.4
   Compiling proc-macro-error v1.0.4
   Compiling vte v0.3.3
   Compiling indexmap v1.7.0
   Compiling textwrap v0.14.2
   Compiling yaml-rust v0.4.5
   Compiling walkdir v2.3.2
   Compiling heck v0.3.3
   Compiling strip-ansi-escapes v0.1.0
   Compiling aho-corasick v0.7.18
   Compiling quote v1.0.9
   Compiling getrandom v0.2.3
   Compiling signal-hook-registry v1.4.0
   Compiling mio v0.7.13
   Compiling parking_lot_core v0.8.3
   Compiling atty v0.2.14
   Compiling which v4.2.2
   Compiling dirs-sys-next v0.1.2
   Compiling remove_dir_all v0.7.0
   Compiling rand_core v0.6.3
   Compiling parking_lot v0.11.1
   Compiling regex v1.5.4
   Compiling directories-next v2.0.0
   Compiling rand_chacha v0.3.1
   Compiling signal-hook-mio v0.2.1
   Compiling shellwords v1.1.0
   Compiling rand v0.8.4
   Compiling crossterm v0.20.0
   Compiling tempfile v3.2.0
   Compiling edit v0.1.3
   Compiling thiserror-impl v1.0.26
   Compiling clap_derive v3.0.0-beta.4
   Compiling thiserror v1.0.26
   Compiling clap v3.0.0-beta.4
error[E0658]: arbitrary expressions in key-value attributes are unstable
 --> /home/gca/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-3.0.0-beta.4/src/lib.rs:8:10
  |
8 | #![doc = include_str!("../README.md")]
  |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: see issue #78835 <https://github.com/rust-lang/rust/issues/78835> for more information

error[E0658]: use of unstable library feature 'osstring_ascii'
   --> /home/gca/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-3.0.0-beta.4/src/parse/matches/matched_arg.rs:130:19
    |
130 |                 v.eq_ignore_ascii_case(val)
    |                   ^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #70516 <https://github.com/rust-lang/rust/issues/70516> for more information

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0658`.
error: could not compile `clap`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: failed to compile `navi v2.17.0`, intermediate artifacts can be found at `/tmp/cargo-installph3cZ6`

Caused by:
  build failed

Versions:

• OS: Ubuntu 21.04
• Shell Version: GNU bash, version 5.1.4(1)-release (x86_64-pc-linux-gnu)
• Cargo Version: 1.51.0

Additional context Installed cargo via apt-get. Successfully installed other stuff via cargo.

Issue Description

Environment

• System: Ubuntu18.04
• Installation method: linuxbrew

When search a snippet, the comments and commands of all candidate snippet are interleved in a random way. Please see snapshot below :)

Describe the bug When using navi with the fish shell, I get an error where navi is using invalid shell syntax

To Reproduce Steps to reproduce the behavior:

1. start a fish shell
2. navi --path ~/.config/cheats

Expected behavior Should see a list of cheats from the ~/.config/cheats path

Screenshots

Versions:

• OS: Arch Linux
• Shell Version [replace this text with the output of fish, version 3.1.2]

Additional context https://github.com/denisidoro/navi/blob/6808dccf5c9d87d016734bbffe5779d35aaa70e5/src/cmds/core.rs#L101

When running navi after install and selecting the "Download default cheatssheets" will cause the following error:

Cloning https://github.com/denisidoro/cheats into /Users/<user>/Library/Application Support/navi/cheats/tmp...

Hey listen! Navi encountered a problem.
Do you think this is a bug? File an issue at https://github.com/denisidoro/navi.

Caused by:
    0: Failed to import cheatsheets from `denisidoro/cheats`
    1: Failed to clone `https://github.com/denisidoro/cheats`
    2: unsupported URL protocol; class=Net (12)

Is your feature request related to a problem? Please describe.

in this snippet

# login to a server and forward to ssh key (dangerous but usefull for bastion hosts)
ssh -A <user>@<server>

I would like to give just "recommendations" for user.

This just sets it to whoami

$ user : whoami 

This opens fzf and let me type something but typing something like root lets navi crash

$ user : whoami && echo 

thread 'main' panicked at 'byte index 18446744073709551615 is out of bounds of ``', src/libcore/str/mod.rs:2017:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

I also tried

$ user : whoami && echo --- --print-query

but this resulted in the same error.

Describe the solution you'd like

I would like to write this

$ user : whoami && echo "root" --- --print-query

or

$ user : whoami --- --print-query --no-select-1

to use whoami and root only as recommendation, so I can type what ever I want.

The openssl dependency is unnecessary. I created a feature dependency for macos targets.

I also created a travis ci build script to build the project on linux and macos machines to verify if everything is still working.

@denisidoro to make the travis part work, you have to sign in to travis-ci.org (can do that via github) and enable this project. Everything is already linked properly on the README and crates.io.

Have a look at my travis builds you can see linux and osx build just fine.

Describe the bug I install navi v2.0.3 via homebrew, and I'm running the fish shell. It looks like it's not finding the cheat files, as any input (git, ls) causes a panic.

To Reproduce

1. Install using brew install denisidoro/tools/navi
2. Run navi
3. Enter git, press enter.

Expected behavior Built-in git cheats are resolved.

Screenshots

$ brew install denisidoro/tools/navi
==> Installing navi from denisidoro/tools
==> Downloading https://github.com/denisidoro/navi/releases/download/v2.0.3/navi-x86_64-osx.tar.gz
Already downloaded: /Users/austinjones/Library/Caches/Homebrew/downloads/cf9715a19022091baf31700a252c6b4051a927200d9466b9e5a540310f6c9195--navi-x86_64-osx.tar.gz
🍺  /usr/local/Cellar/navi/2.0.3: 28 files, 2.1MB, built in 3 seconds
$ RUST_BACKTRACE=1 navi                                                               1858ms  Wed Mar 11 15:21:02 2020
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /rustc/f3e1a954d2ead4e2fc197c7da7d71e6c61bad196/src/libcore/macros/mod.rs:15:40
stack backtrace:
   0: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
   1: core::fmt::write
   2: std::io::Write::write_fmt
   3: std::panicking::default_hook::{{closure}}
   4: std::panicking::default_hook
   5: std::panicking::rust_panic_with_hook
   6: rust_begin_unwind
   7: core::panicking::panic_fmt
   8: core::panicking::panic
   9: navi::cmds::core::main
  10: navi::main
  11: std::rt::lang_start::{{closure}}
  12: std::panicking::try::do_call
  13: __rust_maybe_catch_panic
  14: std::rt::lang_start_internal
  15: main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Versions:

• OS: macOS Mojave
• Shell: fish, version 3.1.0

I wonder, how can I use the --path option to load the default folder and other folders?

Something like:

    navi --path '~/.cheats:<default_cheats_folder>'     # uses custom cheats

Is the <default_cheats_folder> available somewhere as a variable we could use?

Describe the bug In fish, navi works as expected for some variables in commands, while for others, it just inserts query instead of prompting for a selection. It is not clear to me what the discriminating factor is.

To Reproduce Steps to reproduce the behavior:

1. Set up navi in fish as described.
2. Open navi via Ctrl-G.
3. From the default cheats, select the docker-compose up -d <service_name> cheat that ships with navi.
4. See that this gets expanded into docker-compose up -d query.

Expected behavior navi should prompt for a service name.

Versions:

• OS: Linux (Gentoo, but shouldn't matter)
• fish v3.0.2

$ bash <(curl -sL https://raw.githubusercontent.com/denisidoro/navi/master/scripts/install)
Downloading https://github.com/denisidoro/navi/releases/download/v2.20.1/navi-v2.20.1-x86_64-unknown-linux-musl.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 2005k  100 2005k    0     0  8846k      0 --:--:-- --:--:-- --:--:-- 8846k
navi

✔ Finished
✔ navi is now available at /home/azureuser/.cargo/bin/navi

To call navi, restart your shell or reload your .bashrc-like config file

Check https://github.com/denisidoro/navi for more info


$ source ~/.bashrc

$ navi
navi was unable to call fzf.
                Please make sure it's correctly installed.
                Refer to https://github.com/junegunn/fzf for more info.

then after installing fzf: sudo apt install fzf

I get this error:

$ navi
invalid preview window layout: up:2:nohidden
invalid preview window layout: up:2:nohidden
invalid preview window layout: up:2:nohidden
invalid preview window layout: up:2:nohidden
invalid preview window layout: up:2:nohidden
invalid preview window layout: up:2:nohidden

Description

$ ./target/release/navi

thread 'main' has overflowed its stack
fatal runtime error: stack overflow
[2]    96826 abort (core dumped)  ./target/release/navi

Reading the core dump, it looks like an infinite recursion on src/commands/core/mod.rs:38:

#30 0x000055e1546993c7 in navi::commands::core::init (fetcher=...)
    at src/commands/core/mod.rs:18
#31 0x000055e154699776 in navi::commands::core::init (fetcher=...)
    at src/commands/core/mod.rs:38
#32 0x000055e154699776 in navi::commands::core::init (fetcher=...)
    at src/commands/core/mod.rs:38
...
#4145 0x000055e154699776 in navi::commands::core::init (fetcher=...) at src/commands/core/mod.rs:38
#4146 0x000055e15469a25d in navi::commands::core::main () at src/commands/core/mod.rs:71
#4147 0x000055e154609423 in navi::commands::handle () at src/commands/mod.rs:16
#4148 0x000055e1545e7b4a in navi::main () at src/bin/main.rs:28

Full backtrace can be found at https://pastebin.com/sL3SN4nR

Versions:

ubuntu 20.04 LTS (I think) $ uname -a Linux 5CG0183BJ0 5.15.0-53-generic #59~20.04.1-Ubuntu SMP Thu Oct 20 15:10:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ zsh --version zsh 5.8 (x86_64-ubuntu-linux-gnu) $ ./target/debug/navi --version navi 2.21.0

Maybe it would be better if could customize the look (nvai UI) I'll give an example here (sorry, maybe my english is not good.)

This is the apt file for the navi community

When running ``navi, the interface will display a lot ofaptcode parameters. Although it is possible to make navi only show memo about apt by typingapt```.

I have a suggestion here

For example, by combining the tags apt into a column, the top display bar can be customized in height and display the corresponding content (abbreviated content)

The user will enter the file apt.cheat corresponding to the label apt in the navi interface through the "Enter key", or other custom keys, and display it in the navi interface (complete content)

The user's operation method is the same as the current one, select up and down keys, and run through the "Enter key". Of course also shell widgets are supported, via ctrl + G. These are the same.

The advantage of this is that: The user adds many different memos, and has many notes, it will be more clear.

This can be understood as another new navi appearance Users can choose to turn it on or off in the configuration file.

navi is a great work in my opinion, 10K stars are really too few!!! Thanks to the navi author and other friends for their contributions. I hope that more and more people pay attention to navi and it will get better and better.

Describe the bug The free Katacoda playground is still being referenced in this project's README.md documentation; but, O’Reilly has killed this service: https://www.oreilly.com/online-learning/leveraging-katacoda-technology.html

To Reproduce Click the this playground link in the README.md section of README.md.

Expected behavior Katacoda playground for installing and using navi.

Screenshots

Versions: All

Additional context It looks like Killercoda may be trying to do something very similar to what Katacoda was before being acquired by O’Reilly, even including support for importing Katacoda scenarios.

I have not personally played with Killercoda; it was just the most promising replacement for this use case that I found after sorting through results of a quick Google search for Katacoda alternatives.

Describe the bug See title. I receive no error from the tool. I don't know how to troubleshot it.

To Reproduce

navi --tldr docker

Expected behavior Show some cheats.

Versions:

• OS: macOS
• Shell Version 3.2.57
• navi: 2.20.1
• fzf: 0.33.0