Jump to content

deanishe

Community Hero
  • Content Count

    5,284
  • Joined

  • Last visited

  • Days Won

    314

deanishe last won the day on May 20

deanishe had the most liked content!

About deanishe

  • Rank
    Workflow Expert / Moderator

Contact Methods

  • Twitter
    @deanishe
  • Website URL
    https://www.deanishe.net

Profile Information

  • Location
    Essen
  • Interests
    Go, Python, beer

Recent Profile Visitors

20,203 profile views
  1. Oh, yeah. I was thinking more generally. It's just kind of ingrained to hit ⌘← to go to the start, even when just ← will do. If sending the same query to different workflows is something you do a lot, why not implement a Hotkey that simulates ⌘←, ⌥⌦? That should cover the majority of cases.
  2. Wouldn’t work, imo. If I want to search Google for “world map”, I’m going to start seeing a load of search results for “world” from the workflow whose keyword is “map”, which isn’t what I want at all. This is exacerbated by the fact that a lot of workflows/users have one-letter keywords. It’s not exactly a great chore to hit CMD-LEFT to move the cursor to the beginning of the query, either.
  3. That's not what it's for. It doesn't solve the problem of not being able to assign the same Hotkey in different workflows, but it's very handy for context-dependent behaviour in a single workflow. It doesn't force you to recheck. It allows you to do different things depending on which app is active.
  4. Yup, you're right. I was wrong. Sorry, That notwithstanding, as you say, the script won't run without at least one argument. I don't know. What are you trying to do?
  5. The workflow is set up so that you must enter a query before it will run the script. And the script itself won't work without any input (it requires at least one argument). If you're trying to figure out how a workflow works, you can't just look at the workflow in Alfred Preferences or the source code. You need to consider both.
  6. That is correct. I haven't made a release with the new feature yet. I'm still ironing out bugs and want to add another feature or two before the next release.
  7. You don't because that would be very bad from a security perspective. Either you use AppleScript: do shell script "/Applications/Marta.app/Contents/MacOS/Marta" with administrator privileges Or you edit your sudoers configuration, so you don't need to enter your password to use sudo. The former is a better idea, security-wise.
  8. Does Spotlight find things on that volume? That’s always the first thing to check because Alfred uses the same index.
  9. The only sensible thing to do would be for Apple to include Py3 in the next release of macOS, as Py2 will be EOLed next spring. I don't at all trust them to do it, though, based on how criminally out-of-date they let some of the UNIX libraries on macOS (OpenSSL, for example) become.
  10. Yes. It should work without an arg. They've added async and await to the new version of JS/ECMAScript/whatever it's called, haven't they? The more mainstream method seems to be Promises, which kinda suck, imo. I don't really follow you here. There isn't any concurrency in the script, is there? So what's the difference to regular synchronous code?
  11. Those aren't errors, they're warnings. They don't matter. It looks like you don't have Zotero or the Bibtex plugin running (or whatever it is the workflow is supposed to connect to). But I don't really know. I've never used the workflow and I've never used Bibtex. You should really ask the author on GitHub.
  12. Jakub, unfortunately "it doesn't work" and "Error in workflow" are not actionable descriptions of an issue. Please read the stickied post on posting useful error reports. You're much more likely to get a useful answer.
  13. The workflow is hosted on GitHub, so the GitHub issue tracker would be the most obvious place.
×
×
  • Create New...