Flow.Launcher
Flow.Launcher copied to clipboard
Custom Query Shortcut
- Expandable Shortcut
- some environmental variables. e.g. clipboard
Do we want to reference to variable? So probably a later shortcut can reference back to an earlier shortcut (then we need a move up and move down button).
It will be interesting if we introduce variable like {{clipboard}}
is this how you would use env variables?
some environmental variables. e.g. clipboard
How do you use this with clipboard?
Shortcut is not being saved.
Oh forget to add jsoninclude i guess. Thanks for checking.
some environmental variables. e.g. clipboard
How do you use this with clipboard?
I manually set {clipboard} to be the content in clipboard.
some environmental variables. e.g. clipboard
How do you use this with clipboard?
I manually set {clipboard} to be the content in clipboard
Can you show me a screenshot how it's setup?
some environmental variables. e.g. clipboard
How do you use this with clipboard?
I manually set {clipboard} to be the content in clipboard
Can you show me a screenshot how it's setup?
https://github.com/Flow-Launcher/Flow.Launcher/blob/0c75dfe46fc9a0116f6c69f9aec0397298df0a96/Flow.Launcher/ViewModel/MainViewModel.cs#L679
just write {clipboard}
in the expanded query.
some environmental variables. e.g. clipboard
I thought you added this user side that allows expanding of env variables?
some environmental variables. e.g. clipboard
I thought you added this user side that allows expanding of env variables?
oh that might be interesting as well. We can add that feature
Shortcut is not being saved.
@taooceros
Can Plugins create shortcuts? If so, shortcuts shouldn't be limited to pure string replacement. They should have the ability to call a function like string foo()
.
And what if user wants to search the shortcut word rather than triggering the shortcut? Like if I want to search ab
but there's a shortcut ab->123456
. What if I want to search a file or whatever else called "ab"? Maybe this is a inappropriate shortcut but we should consider this case.
Can Plugins create shortcuts? If so, shortcuts shouldn't be limited to pure string replacement. They should have the ability to call a function like
string foo()
.
I didn't get the idea? you mean let plugin provide variable?
And what if user wants to search the shortcut word rather than triggering the shortcut? Like if I want to search
ab
but there's a shortcutab->123456
. What if I want to search a file or whatever else called "ab"? Maybe this is a inappropriate shortcut but we should consider this case.
I guess that's user choice? We can always require prefix $
for shortcut though, but I think it is convenient to do a full string replacement if user only type shortcut.
I didn't get the idea? you mean let plugin provide variable?
Yes.
I didn't get the idea? you mean let plugin provide variable?
Yes.
Ah that's cool. Though I feel like it is not super easy? We may need extra api for that. Mind leave it in the future?
I tried to to finish this PR. One last thing to decide, is how to let users know there are builtin shortcuts like {clipboard}
? Just write them down in documents or put them in the shortcut list?
I tried to to finish this PR. One last thing to decide, is how to let users know there are builtin shortcuts like
{clipboard}
? Just write them down in documents or put them in the shortcut list?
I thought they are currently displayed like this in this PR?
What plans do we have for adding built in variables apart from clipboard?
What plans do we have for adding built in variables apart from clipboard?
Not yet.
Explorer plugin doesn't play well with {
, getting exception when I type {cli
, need to fix that in Explorer.
What plans do we have for adding built in variables apart from clipboard?
Not yet.
So what else can we do with this functionality? Clipboard access can be done better with the Clipboard plugin I feel.
Explorer plugin doesn't play well with
{
, getting exception when I type{cli
, need to fix that in Explorer.
Maybe it is related to the vscode workspace plugin (default action word {
). I remember I had similar issues when testing along with the plugin.
What plans do we have for adding built in variables apart from clipboard?
Not yet.
So what else can we do with this functionality? Clipboard access can be done better with the Clipboard plugin I feel.
This design is to provide functionality more than simple static string replacment. I don't have any good idea about what else we can do with it yet.
Maybe it is related to the vscode workspace plugin (default action word {). I remember I had similar issues when testing along with the plugin.
Nah, actually reproducible with Dev branch.
This design is to provide functionality more than simple static string replacment. I don't have any good idea about what else we can do with it yet.
Feels like half-baked at the moment because users wouldn't be able to add new ones in and clipboard access can be done with the clipboard plugin. What about pulling it out to a separate pr?
This design is to provide functionality more than simple static string replacment. I don't have any good idea about what else we can do with it yet.
Feels like half-baked at the moment because users wouldn't be able to add new ones in and clipboard access can be done with the clipboard plugin. What about pulling it out to a separate pr?
Maybe we should discuss it later, when other problems of this pr are fixed.