smarg19

To everyone who still has interest in this workflow:

I am sorry that it no longer works. I no longer need or use the workflow. I developed it when I was in graduate school and writing all the time. I have since left academia and haven't really needed this (or my other workflows) in years. However, I do still love this little workflow and would love to get it healthy again, but it has been years since I've fiddled with Alfred workflows. If anyone wants to become the new maintainer, I would be happy to spend a weekend afternoon or an evening pairing with someone to get it updated and fixed and then hand over the Github repo. Let me know if you are interested.

A new workflow that has quickly become a firm favourite: Search OmniFocus.

 

Because it directly accesses OmniFocus's sqlite database files instead of using AppleScript to talk to the application, it's insanely fast. This makes is so much more useful than other OF workflows.

 

Insanely fast.

Had actually thought about building something essentially just like this a while back. Thanks for the rec!

I'm not exactly following. In Zotero, what field is the URL stored in?

What do you mean by "if Alfred can find and export a citation based on its URL"? Do you mean use ZotQuery to find a particular citation via its URL and then from ZotQuery export that citation? If that is what you mean, then this could be possible, I just need to know more about what these URLs are.

Yes. I have just fixed it. Will hopefully be able to push the new version this weekend.

Did you install the Satimage package? It's a prerequisite of those features. You can start the installation via the wfy:install keyword.

If you already have it installed, it would suggest that Evernote has changed something about its underlying notes structure, that will require me to figure that out. Can't give a firm deadline on that, but I will get to it.

Joh, Sorry. Just came across this here. I see that you have posted in the workflow thread as well. I have been talking with you primarily via GitHub Issues. Just wanted to acknowledge to Vero and others that this is being worked on.

Can you open Alfred Preferences, go to the Slackfred workflow, turn on debugger and then run this. That may help me narrow down what is happening.

Hit the same problem. The issue is that the codebase is behind your GitHub code. The slackfred-search.py file attempts to import requests and then tries to use it once for a GET requests. The other time, you use the web.py module from the Alfred-Workflow library. Your GitHub code doesn't have this issue. All you need to do is update the Packal download with the up-to-date codebase.

- - -

PS. Nice workflow!

Is it possible to restrict porn and filthy content from showing up?

Not in any sensible way that I can of. I personally don't really see any of that, but I'm mostly searching for TV episodes and movies. Is there some way to tell easily? I could filter results, but I would need to know what to filter on.

Some details:

Pandoc: pandoc-1.13.2

Pandoctor V1.0.5 downloaded from http://www.packal.org/workflow/pandoctor

Alfred: v2.5.1 (308)

in Folder "Workflow Data" there is a single folder: "com.hackademic.pandoctor". In that folder are two files:

- user_ignore.json

- user_templates.json

 

There's no cache directory in Alfred 2 Application support dir.

 

Anything I've missed?

 

Thanks again for your swift responses.

ske

Ok. I know I've been MIA, but life...

Anyways, I've given this a think and I believe I understand the problem. At some point, you *did* choose template as an option and you failed to pass an argument. When you tried to run this conversion, pandoc and therefore Pandoctor failed. However, there is a bug such that this failure wasn't properly handled, and this attempted run was retained in the cache. So, the "template=" option was retained in all subsequent runs. 

This is a bug. Thank you for finding it. And I'm quite sorry that it took me this long to figure it out. To fix the problem, go to "~/Library/Caches/com.runningwithcrayons.Alfred-2/Workflow Data/com.hackademic.pandoctor" and delete "runner.cache" then run a new conversion. When I get free, I will work on a fix for the bug and push an update.

One thing to note on using a reference.docx file, tho: be sure to pass the full path to the correct document (not a relative path, like in your example above) as the argument for the option. Or else this will cause pandoc to fail as well. You can get the full path by navigating to the file in Alfred and using the Copy Path to Clipboard function in Alfred's file browser.

Hi, 

 

I'm running pandoctor but cannot pass the configuration process. After hitting enter once I type dr:config I get the following message: <?xml version="1.0" encoding=   And, of course, pandoctor is not configured.

 

Is there a way to solve this?

 

I downloaded the workflow from Packal (I have version 1.0.5).

You need to run the command with Alfred's debugger on and post the results so I can have a better idea of what broke.

One common issue tho:

+ do you have pandoc already installed?

I am in the middle of some hectic work, but I will check in on this workflow hopefully sooner rather than later. Could someone post a list of the outstanding/remaining issues, so I know what to look for when I get back at it?

TBH, I haven't looked at this code in a long time, but the speed is almost certainly not a Python issue. It's likely a toolchain issue. I believe that each time, the workflow reads BibDesks cache files. It would probably be better to have a background process that updates a SQLite database against the cache files, and then the workflow itself reads and queries against the db.

Poke me sometime during the summer and I may be able to do that.

There's a bug in the code.

You're calling wf.send_feedback() in search(), but you also call it in prepare_feedback() if there's an error. So when the workflow wants to display an error, it wrongly outputs the XML twice.

 Good catch. Dumb bug. Will fix and update ASAP.

You will need to use a little code to get the text from the web. I know Python best, you could conceivably use anything that Alfred supports.

Setup

Create a Keyword Input (use cas as the keyword, require a query). Connect this to a Run Script Action. I would then write a script that uses something like this Python module to get whatever data you need. Pass that to a Copy to Clipboard Action and your done.

Obviously, the work-intensive part is writing the script, but that Python module seems to have that part pretty well figured out.

Possibly you should require an IQ test on certain workflows. Maybe a secret sub-forum where people like me can't access. 

 

In my haste I forgot to install pandoc.

Haha. If you knew how many times I've done stuff like that you'd realize why I can't require an IQ for workflows; I wouldn't be able to use them myself

Glad you figured it out tho. And TBH, this will help me to deal with this problem when it (inevitably) occurs again.

Pandoc is wonderful and powerful. And if you really start to use it, you should honestly check out my blog post on this workflow, where I explain Templated Commands, which are the real power-user feature of the workflow (the GUI for one-off conversions is the "normal" use case) as well as my Pandoc Templates (on GitHub). I have a nice Word DOCX template and a CSS file so that you can preview in Marked. With templated commands and the reference.docx file, I've basically got my pandoc workflow down to one step (run the Pandoctor templated command).

It looks like the dr:config didn't work fully. You only have outputs and inputs here. You should also have options and arg-options. Delete this file. Then re-run dr:config. Have the debugger on with "Interesting Information". As a quick check if the second run did something more, look at the file size before you delete and the file size after dr:config is re-run. If bigger, then try to convert again. If the same, post the debug output here.

Ok. TBH, Pandoctor's code base was/is slightly in flux. It appears that I have stored the Options data under a different name. To determine what that is, you need to open this file: /Users/drlulz/Library/Caches/com.runningwithcrayons.Alfred-2/Workflow Data/com.hackademic.pandoctor/pandoc.cache

It is a pickled file, so opening it in a text editor like Sublime. Paste that text (it will look sort of like gobbedly gook) here. I'll check it out.

Post debugging output?

What are the files in the workflow data directory? It appears that one of the paths is empty. Those paths are stored in a JSON file in the data directory. Find that file and paste in the contents.

There seems to be an issue with the XML output. Can you try re-downloading from Packal first?

Python with BeautifulSoup is definently the way to go. It's sleek, intuitive, and fast. You're close with your python example, so I'd stay the course.

Reading through the BS documentation will help get a sense of what's possible. Also, check out other's workflows. My LibGen workflow is right along this path. When I get some free time, I'll give you more specific feedback. But it really does look pretty good already.

This is truly odd. I have a clean install working perfectly on my machine. I'm going to need *all* the information to get to the bottom of this. So, what version of Pandoctor do you have? What version of Alfred? How did you download the workflow? What is in the workflow directory? In the data directory? In the cache directory?

Try to re-install Pandoctor from Packal. I'm not certain why it's stuck. I just downloaded a fresh version from Packal, and it works well for me. So let's try re-downloading.

Go the workflow's data directory (~/Library/Application Support/Alfred 2/Workflow Data/com.hackademic.pandoctor/). Is there a file called user_defaults.json? If so, open it and send me the contents. If you haven't selected template in the options stage of the conversion, then it must be in your defaults.

Have you added template to your defaults at some point? Either that, or you selected it as one of your options, but you didn't supply a value (in this case, the path to the template).

However template= got into the command, that's what is breaking Pandoctor. So, if it's in defaults, we just need to remove it. If you selected it, just don't do that without entering a path.

Also, have you created any templates, in the Pandoctor sense? FWIW, that is really the best way to use Pandoctor. Create a template command with exactly the flags that you need, and use that, rather than creating one of the fly. TBH, the on the fly conversion is there for simple stuff. My rule of thumb is, if you start selecting lots of options when running an on-the-fly conversion, you should probably just make it a template.