-
Notifications
You must be signed in to change notification settings - Fork 21
Option for retain_last_search to include arguments #220
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
By command, you mean the remote command that is to be launched by the SSH server once connected, or the command line used to launch PuTTY itself? |
I mean the command line launched to use PuTTY itself. For example, I might open an ssh session to 192.168.1.1:
Then if I want to open another PuTTY session to 192.168.1.1 (for tailing a log or something) I would want to just:
At the moment I have to:
|
Keypirinha's |
I'm using the PuTTY plugin (with a different label). I am not using sessions, hence why I am looking to have not just the last command remembered but the arguments too. This could apply to running any application with arguments, not just PuTTY |
Then just rely on the |
I already have history for PuTTY sessions, having to hunt for the session in a list isn't what I'm looking for (especially since it isn't in 'most recent' order), I just want to be able to hit my Keypirinha shortcut and hit ENTER and have it run the last thing I did. Is the source to Keypirinha avaiable somewhere, it sounds like a simple change? |
You do not have to "hunt" for the item with the args, just use the appropriate search term or associate a keyword to the desired item. I suggest you read carefully at least this part of the documentation. |
The argument is not pre-populated, therfore I have to find it (hence "hunt"). Testing this just now shows I need to enter enough of the argument for it to appear and then use the arrow keys to highlight it (in which case I might as well re-type the whole argument). To elaborate, after running: This means:
or
The benefit to me of having the last command pre-populated is that:
Is there anything more I can do or explain to help? |
To add, I deal with a large number of similar (but different) commands that change frequently, so making a keyword for each one isn't practical. |
No it's just that I fail to see what more could be implemented here. KP already offers what you asked but in different ways than what you are used to have with Launchy or Win+R:
Those two cases work regardless of the presence of arguments. Also, both can be achieved with pretty much the same number of keystrokes as long as you manage to use the right search term to differentiate them. Now, if you feel like you would have to use the If every solution I offered so far does not fit because you think your use case is too extreme ( |
That was helpful, I was not aware of the While not ideal, it could work if I could tweak it a bit:
This still feels like an awkward way of aproaching what I am trying to achieve, part of the benefit is being able to alter the last command only slightly (or fix a typo). For example, with my proposed modification, if I launch KP and run Alternatively, if I launch KP and run It seems like adding an option to keep the last arguments as well as the last command would be a simple change, is there a reason you're averse to this? Is it difficult change, not something you want to implement or something else? If it is something I can achieve with a plugin I will certainly try, but I was under the impression I wouldn't be able to do this in a plugin. |
This is the default and only behavior of the history list ATM. Last executed items come first in the list.
It is already possible to alter the args of an item by searching for it, either in normal mode or in history mode, then press Really I fail to see what change there is to be done here. Everything you asked so far is already doable in KP (and documented) except the special feature to launch KP in history mode directly, that I mentioned in my previous comment, and that I'm willing to implement if needed. |
My problem with KP cannot be fixed by any work-around provided, it can only be solved by populating the LaunchBox with the previous command in full, including command line arguments (or replacing me with someone else, but then it wouldn't be my problem...) To say this problem does not exist, is not important or can be solved by another (longer) way is ignoring my very real problem. I do not understand why this feature is unacceptable while in #219 you are happy to add a seemingly similarly trivial feature (other than that is a plugin while this is core app). From #219:
I am saddened by this as it is probably the only remaining feature of KP that is missing for my use (that I cannot add myself via a plugin) and am reluctant to switch to another package (such as Wox or Executor; most launchers have this feature) as I would be giving up on some niceties that KP has; however I don't have much choice. I wish I had some idea as to what the objection was -- it seems you are aruging that this feature already exists? Or am I expected to make some financial contribution? Do I need to contibute some new plugins to be taken seriously? I also wish this project was open-source so I could make the change required without miscommunicating further (is it closed-source with any particular reason, such as monetization further down the line?) Please help me understand the rationale even if you're unwilling to make the change. |
Again, there is the history mode for that already. And I offered you to implement a
Nothing prevents you to roll your own plugin. But as I already suggested, I would first try to learn about the tool I use instead of arguing by making incorrect statements, and by doing so, demonstrating you haven't even tried the existing features. Keypirinha is very much perfectible and as a matter of fact, this project has shown itself to be very open to suggestions. But it is also based on strong design choices that makes it quite different than Launchy, Wox or Executor you mentioned. It is very probably why it will never be as popular as a launcher like the so heavy and buggy Wox. I appreciate you took time to insist on your initial (biased) idea while trying to remain polite. In turn, I tried to emphasize you didn't grasp how to use this tool yet (you made that obvious really). |
Apologies, I realize I may have overlooked a way this could work. I didn't want to have two bindings, one for bringing up KP normally and one for the last command, however if I don't bind the normal KP launch key and instead bind your proposed |
You will be able to bind your current Just to clarify, the new Considering the initial issue and the workflow you described vs. the current design, this is as close as it can get. Would that be an acceptable solution to the initial issue? |
This sounds like almost exactly what I am looking for. When in the history, it doesn't allow me to enter a new command (as if I wasn't in history mode). Is there a solution to this? The goal is to be able to perform one of 3 things after launching KP with a hotkey (and the
The last one is the most frequent use, so it would be desirable to achieve this without using a different hotkey to launch KP or extra keys (such as prefixing my command with Possibly an option to return from history mode a non-keyboard shortcut key is pressed? |
|
Fantastic, thanks! |
I'm so confused; I think I have the identical problem as syserr0r but don't understand how it was resolved. It appears to me that Keypirinha doesn't save argument history for apps. I regularly want to repeat the same app+argument combination but it seems that Keypirinha only recalls the app command, not the arguments. Am I missing something? |
For me, |
Thanks so much for replying. For me, when I select apps that I used arguments with, not only do the past arguments themselves not display in the history list, they are also not remembered when I hit tab. Nor are they recalled if I press enter on an item in the history list. The app command just gets executed without an argument. Is this how it works for you, or are your app arguments remembered? |
Oy, I finally found the damn setting in the apps settings that for some reason isn't the default behavior. I needed to set |
I don't use that, this is my current config:
This may be because the only real app I call arguments with is putty/ssh which might be handled differently? |
I frequently open multiple PuTTY sessions to the same host and when using launchy it would remember the whole command (ssh 127.0.0.1) so all I needed to do was press
Enter
; with Keypirinha it only remembers the command not the arguments (ssh) so I need to enter the full host again.It would be great if Keypirinha had an option to remember the arguments too (as far as I can tell this does not currently exist)!
The text was updated successfully, but these errors were encountered: