armenaton

What is does This Alfred workflow enables academic citing and publishing with any markdown app like iA Writer, Ulysses, or Scrivener. It does so by offering a Zotero Citation Picker for Pandoc Markdown Citations and by automatically converting Markdown files into `.docx`, `.pdf`, or `.html `with the proper bibliography. This workflow is made for academics like me who neither like Word nor LaTeX. As the name suggests, this workflow is basically a user-friendly interface for Pandoc, allowing you to make use of Pandoc's vast capabilities without ever needing to open the Terminal.

Thanks (again)! yeah^^ Well thing is, I am not really a coder, only had some computer science classes in school. Up until now; I mainly used Applescript to automate very small stuff, never wrote something with more than ~15 lines of code. Now this Pandoc workflow is the first bigger thing I am ever writing. It was fun, but as coding is neither my day job nor my side job, I don't whether I am ever going to code so much again. But if I do, I will strongly consider using a language other than Applescript. More than one time, I ran into some really unnecessary problems due to it.

So I want to use Applescript (osascript Script Action) to read some variables from the workflow environment. While everything works smoothly, I encountered an issue when the variable included special characters, in my case the German Umlaute (ä ö ü). Via some testing, I could isolate the issue to this: set original to "ä" --this string has also been saved as {var:test} in the Alfred Workflow Envrionment set no_encod_specified to (system attribute "test") set utf8 to (system attribute "test") as «class utf8» set utf16 to (system attribute "test") as Unicode Text return original & " " &

Is there a reason to do so with one Scripting action but not the other? It took me actually a while to figure out Alfred does this, as I kept looking for errors in my code. Also makes some further actions a bit intransparent, e.g. Alfreds Conditional Utility does not recognize the line break as \n, but (seemingly) only in its "invisible" form.

I have found a bug with the Run Script Action when using osascript. The "result" command always passes on the String with a linebreak at the end, although there shouldnt be one. The problem does not occur when using the Run NSApplescript Action with exactly the same one-line-command. I have put together a small demo showing the problem: https://www.dropbox.com/s/tsk88mnwyojmgdt/demo.alfredworkflow?dl=0

Great, now it works, thank you so much 🤗

Ah I see. Wasn't aware of those, will do, thanks. I see. Okay, now running it now results in another error: "Error running filter pandoc-citeproc: Could not find executable pandoc-citeproc" I assume it's because Alfred now knows the path to pandoc, but not to pandoc-citeproc? If so, how do I tell Alfred that it is simply also located in usr/local/bin/? Tried do shell script, somehow didnt work either... (And I composed the command in AS because I was more familiar with AS)

I tried both. (And I tried running with bin/bash and bin/zsh, also tried argv and {query} and deselecting/selectign escaping characters) Ah, I didn't knew Alfred had its own Debugger. Okay, I tried it and it reports as only Error "/bin/bash: pandoc: command not found". So I guess you are right about PATH? How do I tell Alfred the right PATH then? (sorry, it's my first time with bash) Sure, here is the workflow. Thanks for taking a look! https://www.dropbox.com/s/72fdcj3c8an9xcv/pandoc.alfredworkflow?dl=0

Hi, I am trying to build a workflow that converts a markdown file to a Word document with pandoc. The workflow creates a long string that serves as the pandoc command with all the arguments. Now when I take that string and simply run it in the Terminal, it all works wonderfully. So does running the string in the Terminal Command Action. Now I obviously would like to replace the Terminal Command Action with the Run Script Action, only now the workflow does not work anymore? I deactivated all escaping (just like in the Terminal Command) and just have "{query}" as input, s