Run last printed command

[denisidoro]

Run last printed command

[enisozgen]

I'm not sure that would work because export won't apply to your main shell. It will apply to the bash shell that was triggered when calling the script.

So the second time one runs navi, the variable will be undefined.

As you say it is not possible to do it with export. I did it just as an example, it's not possible to do it since command opens different shell processes at background.

[denisidoro]

Maybe #37 solves the same problem and we can close this issue? What do you think?

[aminehmida]

I think what you want to do it is to put the command in the bash readline buffer so you have a chance to edit it before you press enter.

I am working on similar project related to AWS
This is very easy to do in zsh using print -z.

Unfortunately, I couldn't find a way to do that in Bash cross-platform (Linux/Mac OS)
Here is an issue in stackexchange maybe you will have better luck than me.

[welcome]

Thanks for opening your first issue here!

[denisidoro]

I'm not sure I got it. Your concern is with the --- syntax?

[enisozgen]

I copied line from there https://github.com/denisidoro/navi/blob/master/cheats/docker.cheat#L40

As brief, I have just make new feature request like navi lastcommand which allows user to run last printed command via navi --print.

These command can be easy and safe for the peoples which is using the tool.

[denisidoro]

I'm not sure that would work because export won't apply to your main shell. It will apply to the bash shell that was triggered when calling the script.

So the second time one runs navi, the variable will be undefined.

[forbesmyester]

It seems somewhat related... I want to run: . $(navi --print) But this doesn't seem to work (when the printed stuff includes export statements).

Whereas if I do . $(echo <what navi printed out>) it actually does work. Am unsure about what is happening in the middle, I haven't done enough digging to satisfy myself that it's a navi bug or a bug in the script navi is executing itself. Only adding it here as it may help with this issue

[enisozgen]

Thank you for solution. Also, it gives ability to change the command before execution.

1. I did small test about to being sure and found small problem. Cheatsheets which expect interactive input like type, port, name fails because of input not provided.

 Unable to fetch suggestions for 'type'! 

You can try this case via:
Ctrl-g write kubernetes type or netstat than press ENTER

2. Just small warning about keybinding. Ctrl-g is already binded key for zsh. I never used it but just I am informing here

bindkey | grep get-line
"^[G" get-line
"^[g" get-line

3. bindkey '\eg' _call_navi didn't worked for me! I used bindkey ^g _call_navi NOTE: This can be related with my machine.

[denisidoro]

Closing in favor of #37