Jump to content

Pennyworth

Member
  • Content Count

    44
  • Joined

  • Last visited

  • Days Won

    1

Pennyworth last won the day on May 31 2015

Pennyworth had the most liked content!

About Pennyworth

  • Rank
    Member
  1. Wow! This is incredible! It's really the little things in life that matter most. Thank you so much 🙏
  2. I'd like to design a workflow where I use a keyword to trigger opening the Alfred 'Snippets' preferences. Ideally it would even open a specific Snippet 'Collection'. Thoughts? Use-case: I use a Snippet Collection called 'Emoji Pack', but I often search for emojis by different keywords than what is originally labeled in the emoji pack, so I find myself often going in and adding extra keywords to certain emojis that I refer to by non-standard names. By creating a custom workflow for this, I can do this much faster.
  3. Follow-up question @dfay or anyone else: how would I create a 'Trigger All' action that opened every URL that the List Filter contains? Let's assume I have 4 websites I'd like to open at once, and then a 5th option that says 'Open All', how would I create that 'Open All' option, that would trigger all Open URL actions within that List Filter?
  4. Interested in this as well! @luckman212 let us know!
  5. Thank you for the suggestion @dfay! I accomplished this using a List Filter and the Conditional utility. Worked like a charm!
  6. I currently have a workflow I made called 'DailyDigest', which consists of a keyword named 'daily' triggering 5 separate 'Open URL' actions (of sites that I'd like to visit once a day). I've attached a screenshot of this basic workflow. It works well, but now I'd like to evolve it to the next level. Ideally, I would type the same keyword ('daily'), but this time it would reveal all 5 URLs in a list within Alfred, and offer a 6th option: 'Open All', which would open all at the same time (as it currently does). Even more ideal, each URL would have its own custom favicon.
  7. Yes, seems that way. Makes me wonder how Alfred's workflow action can get the job done faster than the system.
  8. It takes about the same if I open a URL through the shell/Terminal directly or through the Alfred workflow/keyword.
  9. I tried removing the '--profile-directory' argument from the bash script and it still lags by 2 seconds more than Alfred's Open URL action.
  10. "Noticeably" is probably an overstatement, but there's definitely a 1-2 second lag when opening URLs via /bin/bash instead of Alfred's native URL Opener (basically instantaneous).
  11. I should also add that using a scripting language to accomplish this is noticeably slower than Alfred's "native" 'Open URL' action. I wonder if this could be sped up somehow...
  12. Thank you @deanishe, this solved my issue! The formula is: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome {URL} --profile-directory={profile_ID} Unfortunately the simpler 'open -a' command won't work when using the 'profile-directory' arg, hence the long application file path.
  13. I use various Google Chrome user profiles ("People", per Chrome's parlance) to keep my personal and work browser environments separate. This means that if I open a Google Docs link tied to work on my personal Chrome user profile, then it will say "You don't have access". I therefore have to always make sure my active Chrome window is of the profile for which I'm logged into an account of. At the same time, I have many simple Keyword --> Open URL workflows. How can I have an 'Open URL' action open not just in a specific browser, but a specific user profile of that browser? Is the
  14. That makes perfect sense. Anyway, thank you for all your help. You may as well add this workflow to your list of workflows! I'm sure there's a good overlap between Alfred user and iStat Menus users. Becoming so accustomed to Alfred over the years, I felt like a dunce still using my mouse to check on stats from the menu bar.
  15. Thank you again for this helpful follow-up script! I really appreciate your help. I ran your script and it showed that my 'Sensor' menu bar item actually goes by "CPU PECI {temp}" (PECI being the "Platform Environment Control Interface", which is the thermal management controller that reports temperatures). I simply swapped out your line with "CPU PECI" and it fuzzy-matched! I did the same for date/time, simply using ":" and it fuzzy-matched as well! (Otherwise, your script reports the menu bar name as a dynamically updated name of whatever time it is in the moment it's queried.)
×
×
  • Create New...