Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Pennyworth last won the day on May 31 2015

Pennyworth had the most liked content!

About Pennyworth

  • Rank
  1. Yes, seems that way. Makes me wonder how Alfred's workflow action can get the job done faster than the system.
  2. It takes about the same if I open a URL through the shell/Terminal directly or through the Alfred workflow/keyword.
  3. 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.
  4. "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).
  5. 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...
  6. 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.
  7. 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 there a way to accomplish this?
  8. 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.
  9. 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.)
  10. Thank you so much! This is amazing! I don't know the magic behind much of this, but it works perfectly! Just bought you a beer via PayPal! 🍻 I've gone ahead and replaced /CPU/ with /Memory/ and /Battery/ for the other menu bar items and those work great, but still can't figure out what iStat calls their menu bar items for 'Sensors' and 'Time'. Wonder how I could do that? Alternatively, can the line let matchiStatsItem = props => { return props.name.match(/dateandtime/) } be modified so that it's a "fuzzy match"?
  11. Ah, that's what you meant by 'it doesn't work.' Understood. I'll email Bjango to see if they can help. Alternatively, do you recommend any Alfred workflows for revealing the system stats that iStat Menus exposes? I'm mainly interested in: battery health/cycles/condition RAM 'pressure'/swap/% utilization per process CPU % utilization per process GPU Status (integrated vs dedicated) temps for CPU/GPU/ports fan speed CPU/GPU/system wattage
  12. Thank you @deanishe for your help! Your sample script is a helpful start. However, when I run it, it merely selects one of the iStat Menus menu bar items and releases. In other words, it doesn't "open" the menu bar item. I would think that modifying 'click' to 'open' in Line 2 of your script would accomplish this, but there apparently is no 'open' command in AppleScript. Is there a way to 'open' the menu bar item instead of merely clicking/selecting it? Another approach I tried is to write a 'delay' line to give me time to press the down arrow key to 'open' the menu bar item, but this doesn't work, because the delay happens sequentially after the click event.
  13. I'm a heavy user of Bjango's iStat Menus, using it to check my system stats frequently. I also happen to be a heavy Alfred user, making my mouse trips up to the menu bar for iStat Menus feel really infuriating. I'd ideally like to open iStat Menus menu bar items using Alfred keywords. For example, if I type in "cpu" in Alfred, it will open the CPU stats from the menu bar, "ram" for "RAM", etc. I've searched everywhere for a workflow like this but can't find anything. I've conducted some research, mostly around how to get a readout of what menu bar items are called by the SystemUIServer, so I can call them with a script, but even that has been fruitless. I also stumbled upon Menu Bar Activate, which lets users activate the menu bar with a hotkey. However, this does not allow activating the right-side of the menu bar, with all the menu bar 'applets'. I haven't found a way to "reverse engineer" this workflow to access those 'applets'. Any help would be greatly appreciated!
  14. I've searched high-and-low for a memory status workflow but found anything. I'd like a workflow to view swap memory status and page-ins/page-outs. This is a key performance indicator to me and something I check on often. A total memory status readout would be ideal (which would include Memory Used, Cache, App Memory, Wired Memory, Compressed Memory, and possibly the new Memory Pressure figure), but just swap memory is what I need most. Alternatively, how would I be able to build this myself? (screenshot from iStatMenus) PS I know that in more recent versions of OS X, memory management has been optimized and Apple now uses the concept of "Memory Pressure" to indicate RAM load, but I still look to swap status to see why my system's behaving a certain way. Correct me if I'm wrong on that.
  15. Thanks Derick! This works well, except sometimes the print dialogue comes in before the page can render in Safari Reader, despite the delay code.
  • Create New...