dfay

For the app cleaning function in Hazel you don't need to set up any rules - just turn on System Preferences > Hazel > Trash > Enable App Sweep

yes i agree. i got clean my mac 2 in a bundle some time ago and won't be updating. if you use Hazel, the app deletion feature is redundant, too.

Here you go -- rough draft at this point:

https://dl.dropboxusercontent.com/u/6601556/Alfred/Ulysses Sheet Actions.alfredworkflow

There are three commands:

un - create a new sheet in Ulysses

ua - set the active sheet to an existing sheet (requires manual entry of the sheet id for reasons discussed above)

up - append to the active sheet (may not work consistently for reasons unclear)

and a File Action

Add to Ulysses (active for plain text and Markdown files by default) - create a new sheet with the contents of the selected file

The latter could easily be extended to other file types with some pandoc magic.

Take a look at these for examples of how to proceed:

https://www.alfredforum.com/topic/2180-case-converter-including-title-case/#comment-12226

https://www.alfredforum.com/topic/4818-code-case/#comment-29475

(this may be the best model if you want to be able to preview the output)

Also this one that I use but which never posted:

https://dl.dropboxusercontent.com/u/6601556/Alfred/Text cleaners.alfredworkflow

x-callback is working on the Mac now as of a version or 2 ago of Ulysses....it's easy enough to create a new sheet but the ids that are used still need to be gathered manually (by option-right clicking on the sheet).  Based on the code in the ulysses search workflow, I've been poking around in the Ulysses library structure, and it seems that the ids are not contained there.  That is, when I know an id, I can search every file in the library without finding that id anywhere there.  

I've got a workflow working which requires the user to set an "active sheet" & then allows appending text to the active sheet (as well as creating new sheets, which is easy), but the goal of searching sheets and then appending to the selected sheet from the results seems impossible without a way to find the id programatically.

Well the first of those issues can easily be fixed in that workflow by changing the argument to be optional, and editing main.rb (or better copying it and making a new script filter to call the edited version) with the lines

if (search_term.length > 0)
	puts MenuItems.generate_xml(search_term, MenuItems.generate_items())
end

replaced with 

if (search_term != "")
	puts MenuItems.generate_xml(search_term, MenuItems.generate_items())
else
	puts MenuItems.generate_xml("",MenuItems.generate_items())
end

The second issue would require third-party developers to make the commands discoverable to Alfred, which hardly seems likely especially since it's only to accommodate a few edge cases.  I'd think writing a workflow to read the Sublime Text palette commands directly might be a better solution.

Who knew such a thing was possible!

still not working

Briefly,

Option1 :

The searches are stored in Alfred.alfredpreferences/preferences/features/websearch/prefs.plist

You'd need to write a workflow that calls a script to add an item to the plist.  

Option 2:

Use UI scripting (in AppleScript or JXA) to push the particular buttons etc.

I've reported it on the developer's GitHub repo for the workflow & he is going to give it a few days to see if it's a temporary outage, then start looking at alternatives.

FWIW the book command is still working.  

The crossref.org API seems to be broken  and with it this workflow.

I got very excited about Alfred remote and dictation when remote first came out. I don't think I've used it in the past year though...but there might be something helpful here:

What version of OS X are you running? (haven't seen that much Lucida Grande in a while...).  Alfred requires 10.9 (Mavericks).

Yes.  The easiest / most flexible way would be to add a Keyword object for the desired input/output, then pipe that out to an Arg and Vars object that sets the Arg to the name of the desired input/output, then pipe that to the existing scripts in the workflow.

Alternatively you could edit the scripts and hard code it there.

Here's a completely rewritten version (in Python) which combines the two workflows into one:

https://dl.dropboxusercontent.com/u/6601556/Alfred/Case Converter 2.alfredworkflow

It uses Alfred's built in Copy to Clipboard with automatic pasting to frontmost app instead of pbcopy in Bash and AppleScript pasting, which seems to give better results.  

I use the same script in Mail Act-On and it's working fine for me.

Looks like a URL encoding problem from the error messages....is this happening with every message?

Usually message:// URLs will have the full domain at the end e.g. @mail.gmail.com and the like but your example only has @AMX which would lead me to think there's something with that particular message that's breaking the script.

You can do a manual update by unzipping the .alfredworkflow file (on the command line or with Archive Utility) then copying the contents of the expanded folder to the existing workflow folder (I think....I haven't actually tried this so I'd make a backup of the old workflow to be safe).

Another option is to have the user run a separate configuration workflow - see 

for an example

You mean like the workflow debugger?

One easy option is to set up file filters for the particular directories you want to search, which may make sense if they are relatively few and fixed - https://www.alfredapp.com/help/workflows/inputs/file-filter/

Another is to use the + to add a new workflow then select Examples > Dynamic File Search -- this installs a workflow that lets you search for a directory then search within it.

Vitor is brave. I would have assumed that was a spam post & wouldn't have gone near the link.

Glad that is working for you.  To be honest, I don't think I've used the keyword version in several years.  You can also delete the two osascript lines in each of the bash scripts and just paste manually (that's actually how I use it).  Or try a shorter delay.

cool but does it really need 4.5 MB of node modules?

Sorry missed this.  I hadn't used it for a long time but tried it out with a new Sierra install and it worked fine straight away with the exception of the Today and Notification Center commands.  It's all using AppleScript to simulate keypresses and mouse clicks, so it may depend on what your keystrokes are set to.  You could try replacing the AppleScripts with Dispatch Key Combo actions - those weren't available back when I made it.  

You can fix Today and Notification Center by changing one line in the AppleScripts:

click menu bar item "Notification Center" of menu bar 2

change it to

click menu bar item "Notification Center" of menu bar 1