Jump to content


Community Hero
  • Content Count

  • Joined

  • Last visited

  • Days Won


deanishe last won the day on April 16

deanishe had the most liked content!

About deanishe

  • Rank
    Workflow Expert / Moderator

Contact Methods

  • Twitter
  • Website URL

Profile Information

  • Location
  • Interests
    Go, Python, beer

Recent Profile Visitors

26,540 profile views
  1. The fact that Alfred accepts Mr Pennyworth's 10x bigger file suggests that size isn't the issue. Especially as you say you're using AppleScript, which is notoriously poor at generating JSON. Please upload a file that triggers the issue somewhere (Dropbox?) and post a link if you'd like us to help figure out what the issue is. Without that, we're just guessing, which is a waste of everybody's time.
  2. Might be an encoding issue, then? @Bernardo_V Have you tried saving the JSON as ASCII (i.e. escaping all non-ASCII characters). In any case, I'm not sure we can say much more without the actual JSON file that's causing issues.
  3. We can't debug a workflow from a screenshot. Please upload the workflow somewhere (Dropbox?) and post a link. You can't open links with Alfred's Open File. Use Open URL.
  4. I'd report it as a bug if I were you. There was a similar limit on STDERR (debugger messages) that was removed several years ago. That said, it wouldn't surprise me if it's a deliberate limit for performance reasons: 200kB is a lot of items. In terms of immediate solutions, you could do the filtering in your Script Filter instead of letting Alfred do it, so you aren't returning as many items to Alfred.
  5. They should appear there automatically as Python writes fatal errors to STDERR.
  6. Might be Alfred permissions, then? Does Alfred have full-disk access?
  7. Sure. But if you want a workflow that will continue to work on future systems, use Python 3. Python 2 is dead. Regardless of any other qualities of the language, that makes it a questionable choice for new code.
  8. What does the debugger tell you the error is? FWIW, I'd switch to Python 3 now if I were you on account of Python 2 being dead. Then you can just do os.makedirs(os.path.expanduser('~/...'), exist_ok=True)
  9. I'm sorry. I don't follow your line of reasoning. If Alfred will always expand snippets mid-word under certain circumstances, regardless of the mid-string expansion setting, then the only way to prevent unwanted expansion is to use unique keywords that will never occur organically, like you recommend. But if unique keywords are required to get optimal behaviour, anyway, what's the benefit in turning off mid-string expansion? I know. But for me – and I suspect for a lot of other users – the option to turn off mid-string expansion is the option to tu
  10. That's what External Triggers are for. Add an External Trigger before your List Filter (or right-click the List Filter and choose "Inbound Configuration…"), then connect your "back" outputs to a Call External Trigger Output configured to call the List Filter (or its External Trigger).
  11. Why does it do that? That sounds sub-optimal. I mean, what's the purpose of being able to turn off mid-string expansion if you still always have to use keywords that never occur anywhere in a word (and not just at the start)? In @miq's case, there's no question that the cursor is in the middle of a word. It makes no difference to the text or the user whether Alfred inserted the first half of the word or they did. It seems to me, it would be better if it didn't matter to Alfred, either.
  12. They're typing "Oor" which expands to "Organisation|", then they start typing "ssystem" to complete the word "Organisationssystem", whereby Alfred recognises the snippet keyword "ssy" and expands it (to "systemtheoretisch") even though "Expand snippets mid-string" is turned off. Alfred appears not to notice if an expansion has left the cursor mid-string, so if you immediately type another snippet keyword, it will expand it even though the cursor is mid-string and mid-string expansion is turned off.
  13. Interesting. But yeah. Unicode strings are marvellous when you’re working with text content, but there’s a lot of stuff you want to treat as bytestrings (i.e. mostly text, encoding unknown), which is a PITA in Swift because it doesn’t really have bytestrings or even “char” literals.
  • Create New...