Toffy

I use an app called RStudio: https://posit.co/download/rstudio-desktop/
 
When I hit ⌘ + C to copy some text in RStudio, Alfred frequently (but not always) activates Clipboard History merging, i.e. the text I have copied is added to the previous text I copied and I hear the Clipboard History merging alert sound. This only happens in RStudio.
 
What's causing it and how can I just copy text normally when I hit ⌘ + C in RStudio?
 
 

Hello, fans of Alfred 😁.   Recently, I developed a workflow to interact with Arc Browser's tab and space.
https://github.com/QIanGua/Alfred-Workflow-for-Arc
 
## Demo
1. Listing all tabs then jump to one you want, e.g. `tabs`
2. Listing all spaces then go to one target, e.g. `spaces`

 
 
 
Refs:
 arc extension in raycast  arc-control alfred-browser-tabs  
 
 
 
 
 

Currently we can have only one keyword in a single input, yet from time to time I need to set some aliases to that keyword. For example, I set a keyword gb to search books in Google Books. but in case that I don't remember that keyword clearly, I also set another keyword gbook to do exactly the same thing. But now I need to add a new keyword input and it's kind of troublesome to keep their icons, url, title, etc. exactly the same.  So I wonder whether you have any plan to support set multiple keywords to increase fault tolerance, just like another app xSearch, you can set multiple keywords and separate them with a comma. I feel it would be great if you add multiple keywords to web search or keyword input in the workflow.
 
 
 

@Toffy I’ll have a think about this for the next Automation Tasks release. Getting the dimensions of a screen is trivial, but getting the current screen takes a bit more effort.

If it helps, Alfred's 'Replace' workflow utility object can actually accept new lines if you alt-enter in the right field.
 
It's likely at some point I'll take a fresh look at all of the utility objects to see how they can be improved
 
Cheers,
Andrew

I appreciate the response, but it is a limitation. 
 
Of course it may slow down the query. That should be something the user is responsible for managing. 
 
Advantages of script filters showing up in the default search:
 
significantly more flexibility and power of workflows Complete control over what shows up in the default search Ability to include all searches. For example in my case, Pinboard Bookmarks. This is very important for me. Ability to customize default results by replacing them workflows. It is not a hindrance to the user:
100% optional. Imported workflows that want to be included in the default search can be dealt with in a variety of ways, such as: A warning alert that 'This workflow wants to be included in the default search. This could slow down every query, but can be turned off later. Proceed?' And it can have three options: 'Cancel', 'Import without including in default search', and 'OK'. In the 'Features' pane, there can be a new list of workflows that are included in the default search. Each will have a checkbox. At the top, there can be an off switch for disabling all of them at once. I believe this will in many cases not slow down the system at all. Has the team tested this? I find it hard to believe my computer can't handle this considering how much it does already. The user already has to manage performance anyway.  
It would be beneficial to Alfred and the community:
 
We would probably see an increase in participation and contributions. Alfred can take ideas from these contributions to further improve the product. It would be a Powerpack feature, giving user more incentives to buy. $$$ I don't think it would be difficult to implement:
As far as I understand this is just a simple restriction and would not involve any large changes. The only problem that would need to be solved is deciding how to order the results. I'll throw out some ideas, but I'm sure this calls for further discussion: Integrate them into the same algorithm based on past actions. Put them at the bottom or top of the results, with a border distinguishing them from the default results. In the workflow give options for how the results should be sorted relative to the default results.  
In conclusion, this would not affect the average user, would give 'Powerpack' users much more 'power', and is a positive step forward for both Alfred and the community.