robwalton

Member
  • Content count

    19
  • Joined

  • Last visited

  • Days Won

    2
  1. I've uploaded a new version v0.9.2 to packal and github. This fixes a race condition where toggling view state failed while Ulysses is launching.
  2. Hi dfay, It looks like your commands to create a new sheet either from text entered in alfred or from a file would be pretty easy to integrate---I guess having captured the content for the new sheet we might pop up my workflow's 'ug' list filter to select the group in which to create the sheet. If you tried to create a new sheet with no content, it might create an empty sheet and then open it. Not sure that the append to file one is really ready yet though (as you say)! This is the one I'd really like (I'd love a quick way e.g. to add an item to the Agenda sheet I keep in some groups). Along this line I could imagine a command to add to a group's 'inbox' sheet. The first time this was run in a group it could create a sheet and capture the x-callback reply with the id of the sheet. Steps and troubles: 1. would need to write and then register an os x url handler to act as the x-callback client that ulysses would call after creating the sheet 2. would need to re-register the url handler when workflow is updated (and make sure old one isn't hanging around) 3. would need to maintain a mapping of group to id of group's 'inbox' 4. if the group's path changed its mapping would become stale 5. subsequent requests to append to a group's 'inbox' would use the stored id This solution (or simpler variants of it) seems like it would be hard to get working reliably without turning into actual work! And it still wouldn't be very complete.
  3. @dunkaroo, awesome, thanks.
  4. Hi @nikivi & @dunkaroo especially, I've uploaded a new version to packal and github. By default groups are now opened in two pane view (Sheets) and sheets in 1 pane view (Editor only). There are two commands to change these 'u:setgroupview' and 'u:setsheetview'. For this to work Alfred needs accessibility access: the workflow pops up a message if it does not. Release notes: @katie, didn't get to better searching yet, but it shouldn't be a biggy.
  5. P.S. @deanishe your workflow http://www.packal.org/workflow/stackoverflow-search is awesome.
  6. Thanks for the quick reply and the info. The first sounds like a pretty useful trick. --Rob
  7. I've started writing a macOS URL handler to trigger Alfred workflows via external trigger blocks. When I went to register it I noticed there is already an 'alfred' url handler registered: alfred://what_goes_here I can't find any documentation about it though. The closest I found was here: https://www.alfredforum.com/topic/7285-x-callback-url-for-alfred-remote, but I didn't see the indicated schemes registered (or any info on what to do with them). So... Is the alfred:// url handler supported? Thanks, Rob
  8. Hi @poritsky, Your workflow looks super useful but unfortunately the link is broken. I made one last year too but it doesn't search inside sheets like yours: https://www.alfredforum.com/topic/9662-ulysses-workflow/ http://support.hogbaysoftware.com/t/alfred-2-workflow-for-taskpaper-3/2481
  9. Thanks @dunkaroo, would be cool to see this working, but the link is broken unfortunately.
  10. Hi @Lecter, Thanks for the feedback. I also use the 'domail' command a lot. The blank lines are a bug which snuck in. It also fails if either Mail or TP is not open, and annoyingly brings in the entire thread rather than just the most recent item. Will fix at some point! This would be a handy feature and if I get my head into working on this again I'll probably add it. It could even copy in any highlighted text. Not totally sure that everyone would get the mnemonic 'dou' though.
  11. Hi @katie, glad you like it! I'm finding it pretty handy too. Firstly, have you tried the 'uo <search term>' command which takes the search term and opens up ⌘O in Ulysses with it? It would be nice to have this work directly in Alfred though. I left it out because I couldn't find an easy way to access the text surrounding the search term. Have just spotted that Spotlight does not do this, so I guess its not a deal breaker. If I get to it, I think I would remove 'us' (sheet) command which can be found with the 'u' command anyway and turn into a search command. Alternatively could keep it and call the new command 'uf' (find). Any thoughts?
  12. Hi guys, Thanks for the suggestion @dunkaroo I've come up with two options: 1. Send cmd-3 and then cmd-2 after a .5s delay. This always ends up in the 'sheet view' as we'd like. 2. Use the applescript (probably superseding suggestion to use hamerspoon). This will cause Alfred to prompt the user to give Alfred Accessibility access to OSX the first time its run: on run argv #activate application "Ulysses" delay .4 tell application "System Events" to tell process "Ulysses" tell menu item "Sheets" of menu "View" of menu bar item "View" of menu bar 1 if value of attribute "AXMenuItemMarkChar" is not "✓" then click end tell end tell end run This again suffers the delay as Ulysses will ignore the 'click' until it has opened the sheet or doc and switched to 3 pane (not sure why it always does this). Given the need to give Alfred (and any workflow installed) Accessibility access turns me off. I've uploaded to git a version with the first approach wired in. (Would add a u:setview command before releasing on Packal). Let me know if it works! --Rob P.S. Any way just to upload quick workflows on the forum. Github releases seem a bit heave for this type of thing!
  13. (Duplicating my response to your question on github here) Hi Nikita, This is a good idea; doing it this way would keep you at the context level you've already entered via Alfred. Ulysses has no apple scripting or callback support for the mac version. If you want to tinker with the workflow's interaction with Ulysses its not too involved. I just tried getting Alfred to send a cmd-2 after opening the sheet or group. At first glance it works great, but actually Ulysses has an odd system in that this command toggles between which-ever view you had selected and 'sheets view' (cmd-2). I can't see a way around this except to read the state of a menu command (i.e. where the check mark is). This seems only to be possible if your global accessibility commands are switched on (http://stackoverflow.com/questions/69030/in-applescript-how-can-i-find-out-if-a-menu-item-is-selected-focused); not sure I'm keen to pursue this route though if it really needs to be on. If you can work out series of manual interactions with Ulysses that always selects what we want, then I'd be pleased to add it to the workflow. I can't see one though. --Rob
  14. I've put an Alfred workflow for Ulysses up at packal.org/workflow/ulysses. The page includes a download link, full instructions and an image. Please give it a go. The commands are briefly: Get help Use the keyword: u:help -- Show a brief summary of commands Open group or sheet Use the keywords: u -- Open group or sheet (cmd-return to drill down) ug -- Open group (cmd-return to drill down) us -- Open sheet Pop open Ulysses Open dialogue Use the keyword: uo -- Search for within Ulysses’ Open dialogue Configure view to open u:setsheetview -- Set the view for opening sheets with (defaults to 'Editor Only') u:setgroupview -- Set the view for opening groups with (defaults to 'Sheets') The source is on github. --- Rob
  15. A new version 0.9.3 up at packal.org/workflow/taskpaper. This includes: There is a discussion thread on the TaskPaper forum.