Jump to content

luckman212

Member
  • Content Count

    163
  • Joined

  • Last visited

  • Days Won

    6

luckman212 last won the day on August 1 2020

luckman212 had the most liked content!

About luckman212

  • Rank
    Member

Recent Profile Visitors

1,746 profile views
  1. Yes @godbout opening Xcode is another reliable way to trigger this for me too. @Andrew it's most noticable on a cold start (after a fresh boot) of a "large" app like Xcode or Microsoft Excel. Another app that I can definitely repeatedly trigger this with is Setapp. I know this is a bit low-tech but I couldn't figure out another way to capture this, so I recorded a couple of seconds with my phone, so you can get an idea of what this looks like... Setapp... https://user-images.githubusercontent.com/1992842/117302537-bce67e80-ae49-11eb-859a-13400dbecc57.mov
  2. @Vero I know what you mean about newlines being treated differently by different OS'es e.g. Mac vs Windows. But if we confine it to just macOS (since we're only talking Alfred here) the definition is pretty clear: it should be 1 + the count of the "0A" hex bytes in a block of text (excluding a final trailing newline if there is one). I'm looking for the same output that would be shown by this bash script: wc -l <<< "${clipboard%$'\n'}" Not sure what page width has to do with it? I'll give you a simple use case (this happened to me yesterday which is what prompted me
  3. @giovanni Thanks but that's not the same. Having it display in the clipboard viewer gives you the ability to quickly flip through history items and see the count, vs having to place items in the clipboard first and then run a workflow.
  4. Currently, the clipboard viewer (very helpfully) shows the word and character counts: Just a suggestion: it would be useful to also display the line count here, if possible!
  5. Just wanted to post a little note on this: I discovered an option I wasn't aware of today in Alfred's Appearance > Options area: I thought maybe this would have some effect on this problem, but alas I tested it and they are both affected by the thread lock. I'm now using Alfred v4.3.4.1229
  6. Hi @Andrew - I just tested & the menubar hat goes zombie as well (other menubar icons are ok). So whatever's going on with this thread locking is across the board.
  7. I just tested it after changing the hotkey to ⌥A — same issue.
  8. Yes, other hotkeys e.g. ⌘-space or F8 (which toggles my crosshairs from PixelSnap) continue to work fine during these unresponsive times. So it's not F-keys. It's only Alfred that gets hung up for some reason.
  9. macOS 11.2.2 Alfred 4.3.2.1221 When hitting my main Alfred hotkey (F11) his window usually appears instantly. But, I've noticed that during certain conditions, such as shortly after launching a slow-to-open app from the Dock (Excel, Photoshop, etc) the Alfred window does not appear. Instead, it seems to hang until the foreground app is in the "ready" state. (Not sure technically what this is called, but essentially it's ready to receive input - mouse clicks, key events, etc). This can also happen if the foreground app gets busy, doing some long running task etc.
  10. @gingerbeardman Hey 👋 Happy Friday! I wasn't referring to your workflow actually. I was talking about Red Sweater's Usable Keychain Scripting (download).
  11. By Jove you've done it! Thanks again for this 🎉 P.S. to anyone else who happened to download the test workflow above, I noticed a bug in it this morning- $RANDOM is 16-bit only (0-32767) so the jibberish output only contains words beginning with the letters {a,b,c}. Pretty boring. Newer versions of Bash support $SRANDOM which is 32-bit, so changing the shebang to #!/usr/local/bin/bash and RANDOM to SRANDOM will "fix" it. Also, swapping in gnu-sed for the built in macOS sed speeds up the loop by a factor of 2 for me. Here's an updated version in
  12. Thank you @Andrew ! Yes that's going to be very useful indeed. Much appreciated. Question: will it accept "0" as the wrap parameter? (disable wrapping completely). That would be nice- in case of a very long line, it could just disappear into the right edge of the largetype boundary.
  13. Is anyone else having this problem? Sometimes I feel like this xkcd https://xkcd.com/979
  14. Thanks Vitor. I'll try to present some better info. For now, I'm experimenting with accomplishing this using Hammerspoon, seems that might be more efficient.
  15. In case anyone wants to really get nuts with fine-tuned URL scheme management, I suggest checking out Finicky. It's up on GitHub: https://github.com/johnste/finicky It lets you route URLs to different apps using rule-based logic. So you could make URLs containing *.google.com open in Chrome, and still keep Firefox as your default browser (example).
×
×
  • Create New...