40-02

Download: 
 
https://dl.dropboxusercontent.com/u/4345768/markdown-toc.alfredworkflow
 
Usage:
 
    Select markdown document, and select [Markdown TOC] then toc contents are copied to Clipboard. 
 
Markdown:
 
 
Output: 
 
   Default depth of section is 2. 
 
     
 
 
 
 
 

Overview

Workflow to display recent Finder files and folders featuring:
5 default categories 2 custom categories Favorites, including a file action Keywords and hotkeys for Favorites and all categories apart Interaction with Open/Save dialogs and Finder Go To Folder Preview, reveal, open or use Alfred file actions Usage

Show Alfred and type the keyword rec:



You can also use the category keyword if you prefer to access the recent files directly, without an initial menu:
Now: keyword now Folders: keyword fol Applications: keyword apps Documents: keyword docs Downloads: keyword dow Custom Category 1: keyword c1 Custom Category 2: keyword c2 Favorites: keyword fav In addition, there is a hotkey for the keyword rec, Favorites and all categories apart.

Note that all keywords, as well as the hotkeys, can be changed (go to Alfred Preferences > Workflows).

Finally, once inside a category you have the following actions:
Return key: open the file or folder Command key: reveal the file or folder in Finder Option key: pass the file/older path to an open/save dialog or Finder window Control key: add/remove an item to/from Favorites Shift key: preview (Quick Look) the file or folder Custom Categories

You can set up to two custom categories:
Show Alfred and type the keyword recpref Select a category to configure and press return key Type an unique category name with at least 3 characters Type one or more (separated by comma) file types e.g.: com.adobe.pdf,public.plain-text To find a file type you can use Alfred Metadata Analyzer.

To remove a custom category press command key while highlighting one of them in recpref.

Favorites

All files or folders set as a favorite item will remain in the list no matter how old they are.

To add an item to Favorites just highlight a file or folder, hold control key and press return key.

To remove an item go to Favorites, highlight an item, hold control key and press return key.

You can also add items utilizing Alfred File Action (accepts multiple files).

Note that Favorites has also its own keyword (fav) and hotkey.

Interacting with Open/Save Dialog or Finder

You can pass a recent file or folder path, or an item in Favorites, to an open/save dialog or even the current Finder window to go to that folder:
when an open/save dialog is displayed type the keyword rec or any other category keyword find an item (a file or folder or an item from Favorites), highlight it, hold option key and press return key wait a bit so the workflow can load and paste the item path Default Folder

The workflow remembers the last path used per application. To use the feature just type the keyword df when an open/save dialog is displayed.

If the workflow was never used for the application, or the path does not exist anymore, then the keyword rec will be automatically triggered so you can select a path from a file or folder.

There is also a hotkey to make things even faster.

Make sure to give the feature time to process because e.g. if you hold keyboard keys way too long then the feature may not work as expected.

What’s new
Up to 2 custom categories (keyword recpref) Downloads category Keyword for each category Hotkey for each category Multiple files in Add to Favorites file action Changed Auto-path to Default Folder (keyworod df) Changed Just Now category to Now Added Help (keyword rechelp) Update to Alfred 2.3 features Several internal improvements  
Download
 
Version 4.3 beta 2 (removed Alfred 3 references) Release date: 12 Jul 2020 Requires Alfred 4 Download  
Version 4.2 Release date: 19 Jun 2016 Requires Alfred 3 Download  

Pandoctor
An Alfred GUI for Pandoc
Version: 1.0.5
Download from Packal
View on GitHub
Read a slightly fuller version on my blog
Introduction
Pandoctor is a relatively simple, easy-to-use way to bring the high-powered functionality of Pandoc to you. For those new to Pandoc, Pandoc is "the universal document converter". It is an amazingly powerful utility that allows you to convert structured text from a ton of possible input formats to an even larger number of output formats.
A potential downside to Pandoc, however, for many users is that it is entirely a command line utility. This means, on the Mac, you have to open Terminal to use it. For many Mac/Alfred users, this is at least slightly daunting. Yet I believe that this should not be a deterrent to more people coming to use the power of Pandoc. This is the reason for Pandoctor. Now, Alfred users can enjoy the comfortability and familiarity of the Alfred interface to manage Pandoc. Here's how:
Pandoctor is accessed via File Actions. The basic file action is "New Pandoc Conversion", which will kick off a series of interactive Alfred menus to create your Pandoc conversion. Once you have chosen the file you want to convert and selected the file action, Pandoctor works in 4 stages:
specify the text format of the chosen file chose the output format you want for the converted file chose any options you want for the conversion process run Pandoc to convert the input file using your chosen options Luckily, Pandoctor is built to move you through these four steps seamlessly and without any interaction on your part aside from selecting and setting the formats and options you want. Let's walk through the steps.Configuration
When you first download Pandoctor, you will need to configure a few settings. Luckily, Pandoctor takes care of this for you. All you need to do is use the dr:config keyword to get everything set up. Once you see the completion notification, you can start using Pandoctor for real.
Running a new Pandoc Conversion
Using the File Action
If you've configured, you begin Pandoctor by using Alfred's file navigation abilities to find the file you want Pandoc to convert for you. Once you've found the file, enter Alfred's File Actions pane for that file (by default this is →). Then find Pandoctor's "New Pandoc Conversion" file action:
>
Selecting the Input Format
This tells Pandoctor to begin a new conversion on that file. Once you select "New Pandoc Conversion", Pandoctor will automatically ask you to choose the format of this input file:
>
Pandoctor tries to be smart about formatting, so it will pre-fill the search bar with what it believes to be the file's formatting. However, if you need to, you can simply delete this and start searching yourself. You will see that Pandoctor displays the full name of the input format as well as a short description to help you discern between similar formats (such as the 4 types of Markdown Pandoc accepts).
Selecting the Output Format
When you choose the input format, Pandoctor will then automatically ask you to select what format you want the outputted, converted file to be:
>
You have access to the full range of possible output formats from this selection. You can use the arrow keys to navigate down, or start searching for your desired output format by name:
Selecting any Options
As soon as you select the output format, Pandoctor will ask you what Options you want to add to this Pandoc conversion:
>
Pandoctor UI
There are a few elements to the UI that require more explanation. First, you see that some items have the inner rectangle filled, and others do not. This is your visual cue to determine which options are active for this conversion (filled) and which are not (empty).
Pandoctor Default Options
When you first come to this "screen" or "window" (not sure what to call individual Alfred windows/pop-ups), you will see that some options are already filled, even though you didn't select them. These are Pandoctor's Default Options. The file (pandoc_defaults.json) specifying which options are by default always on (filled) can be found inside the workflow's folder (if you need to open this folder, you can do so easily using the dr:help keyword and selecting Root). This file also has comments for most options, which gives some information about them (Obviously, for detailed information about Pandoc's options, visit the User Guide). When installed, Pandoctor has 4 default options on:
parse-rawDescription: "Parse untranslatable HTML codes and LaTeX environments as raw HTML or LaTeX, instead of ignoring them." smartDescription: "Produce typographically correct output, converting straight quotes to curly quotes, --- to em-dashes, -- to en-dashes, and ... to ellipses." normalizeDescription: "Normalize the document after reading: merge adjacent Str or Emph elements, for example, and remove repeated Spaces." standaloneDescription: "Produce output with an appropriate header and footer (e.g. a standalone HTML, LaTeX, or RTF file, not a fragment)." User Default OptionsIf you want to set your own default options (overriding these), you can use the dr:defs keyword. This will provide a "window" similar to the standard Options window, but without anything selected. Here select whatever items you want to be on by default for any new conversion.
Selecting any Options, pt. 2
Back to the Options Selection, tho. You will also see that that there are 2 basic types of options:
Boolean Argument Selecting Boolean OptionsIf you select a Boolean option, it will simply "turn on" (the rectangle will be filled) and this screen will refresh. For example, here's this screen right before I choose to "turn on" the strict option:
>
and here's what the screen looks like as soon as it refreshes after I selected that option:
>
Selecting Argument Options
So, "turning on" Boolean options is simple. Argument options, however, require a bit more work. As the name suggests, this type of option requires more information (an "argument"). (Again, if any of this is confusing, I would highly recommend reading through Pandoc's User Guide). This means that you will need to tell Pandoctor what you want the "argument", the information, to be. So, whenever you select an Argument option, you are taken to an intermediary "screen" where you can supply the needed information. For example, if I were to select the toc-depth argument option, I  would then fill in the information (I want the Table of Contents in the converted file to only go 4 levels deep):
>
Once you fill in the information, press return (i.e. "Set argument value of chosen option") and return to the base Options "screen".
Finalizing Options
Now, as soon as you have set all of the options you need, you only need to select the top item on this "screen": Done setting Options?. This will close this screen. As I've noted before, if you instead select an option, this screen will merely refresh.
Pandoctor UI, pt. 2
A small UI note: there is always a "header" for every list that Pandoctor displays. However, there are 2 different kinds of headers:
informational and non-selectable interrogative and selectable The purely informational headers have the little i in the center. These headers are found when selecting input and output formats. They cannot be selected; they simply tell you what that "screen" is. The interrogative headers, however, can be selected. These have the ? in the center. You will use these to "close" the screen you are viewing.Running your Pandoc Conversion
Returning to the flow of the conversion, you have just finished selecting all of the options for your Pandoc conversion. As soon as you hit Done setting Options?, Pandoctor will begin processing the conversion. This process can take a bit of time (particularly when generating PDFs), but when it is complete, you will see a notification in the top right of your screen:
That's all there is to it really. In 4 simple steps, you can convert just about anything. However, for those more inclined toward "power-use", there are a few other abilities under Pandoctor's hood.

Ignoring Options
First off, Pandoctor offers the ability to "hide" or "ignore" certain options in the Select Options screen. Pandoc itself offers a lot of options, and always seeing them all is often unnecessary. If there are any options that you never use, you can simply remove them. To do this, you need to use the dr:ignore keyword.
This will bring up a "screen" almost identical to the Select Options screen, but here you are choosing what options are hidden from that other screen. Once again, the two icons are informative. If an item is filled in, this means that it is going to be ignored:
>
Otherwise (not filled in), it will appear in the standard Select Options window:
>
As with the basic window, you can search here or just use the arrow keys. Select all of the options you want to ignore, and when you are done, select Done setting Ignore? to exit.
Template Commands
For those who use Pandoc frequently, you will likely use the same basic command over and over again. If that's the case, Pandoctor has a "power-user" feature just for you. In addition to the "on-the-fly" conversion available via the "New Pandoc Conversion" file action, Pandoctor also hase a "Templated Pandoc Conversion" file action:
>
This action grants you access to any and all Pandoc template commands you have set up. Before I detail how to create a new template, let's briefly discuss the elements of a template. Pandoctor ships with a file in the workflow directory that has some sample templates. This file is titled pandoc_templates.json. If you open this file in your text editor of choice, it will look just like this:
Sample Templates
 

/* PANDOC TEMPLATED COMMANDS The [font=courier new,courier,monospace][/font]defaults[font=courier new,courier,monospace][/font], at initiation the [font=courier new,courier,monospace]parse-raw[/font], [font=courier new,courier,monospace]smart[/font], [font=courier new,courier,monospace]normalize[/font], and [font=courier new,courier,monospace]standalone[/font] options, are found at [font=courier new,courier,monospace][/font]pandoc_defaults.json[font=courier new,courier,monospace][/font]. HOW TO CREATE TEMPLATE: + take your CLI pandoc command (e.g. "pandoc -s -S --toc -c pandoc.css -A footer.html README -o example3.html") + convert all "short option + space + argument" to "long option + '=' + argument" (e.g. "pandoc -s -S --toc --css=pandoc.css --include-after-body=footer.html README --output=example3.html") + split all options into list of individual options (e.g. [pandoc, -s, -S, --toc, --css=pandoc.css, --include-after-body=footer.html, README, --output=example3.html]) + remove initial call to [font=courier new,courier,monospace]pandoc[/font] and replace input text path with [font=courier new,courier,monospace][/font]{input}[font=courier new,courier,monospace][/font] variable (e.g. [-s, -S, --toc, --css=pandoc.css, --include-after-body=footer.html, {input}, --output={input}.html]) + make sure every option is a JSON string (e.g. ["-s", "-S", "--toc", "--css=pandoc.css", "--include-after-body=footer.html", "{input}", "--output={input}.html"]) + give it a memorable name + determine if you want to automatically add your default options to the command or not. In order to make your templates more extensible, you can use any of 3 built-in variables that relate to the file chosen to convert: * {input_file} = The full path to the file, including file extension * {input_name} = The full path to the file, without file extension * {input_dir} = The full path to the parent directory of the file For example, this template would only work if you kept a project directory that contained both [font=courier new,courier,monospace]biblio.bib[/font] and [font=courier new,courier,monospace]chicago-author-date.csl[/font] alongside your input file. { "name": "Biblio Test", "use_defaults": false, "options": [ "-s", "-S", "--biblio={input_dir}/biblio.bib", "--csl={input_dir}/chicago-author-date.csl", "{input_file}", "--output={input_name}.html" ] } */ [ { "name": "XeLaTeX PDF", "use_defaults": true, "options": [ "-N", "--variable=mainfont:Georgia", "--variable=sansfont:Arial", "--variable=monofont:\"Andale Mono\"", "--variable=fontsize:12pt", "{input_file}", "--latex-engine=xelatex", "--toc", "--output={input_name}.pdf" ] }, { "name": "Pandoc MD -> HTML", "use_defaults": true, "options": [ "--toc", "--css=pandoc.css", "{input_file}", "--output={input_name}.html" ] } ] Template ElementsAs you can see, it comes with two "default" templates, as well as one commented-out template. These are there to help you see the format of the JSON as well as Pandoctor's unique features. As the default templates show, each template must have 3 keys:
name use_defaults options The type of value for each of these is fixed. For name, you must use a string; for use_defaults, you use a Boolean (either true or false); and for options, you use a list/array of strings. The name parameter is simple; this is the name of your template (what will be displayed when you are asked to choose which template you want to use). The use_defaults parameter is fairly self-explanatory as well; do you want to automatically add the default options to this command or not? It is the options parameter where the magic happens, and this is the one that requires the most precision.As the comments in the file will tell you, you need to properly format your Pandoc command for use as a Pandoctor template. This means, each option is its own item in the list and each option is without spaces (unless properly quoted). This will require you to use the "long" version of any option along with the an equals [=]. The 3 given examples give thorough demonstration of what acceptable templates can look like.
Template Variables
In addition to these formatting requirements, Pandoctor also gives you the ability to abstract your template properly. For any template, you have access to 3 variables:
{input_file} = The full path to the file, including file extension {input_name} = The full path to the file, without file extension {input_dir} = The full path to the parent directory of the file These variables will allow you to properly use your template with any conversion. You will see that every template should use {input_file} and {input_name} for the input and output options respectively. In addition, if you specify any outside resource files, you can then use {input_dir} to ensure that the full path is properly constructed (see the "Biblio Test" example in the comments).Running a Template Command
Once you set up a template, it will make using Pandoc so much easier.
All you have to do is select the file in Alfred's file navigator, choose the "Templated Pandoc Conversion" file action, and then choose which template you want to use. That's it.
>
As with the New Conversion, the process takes a variable amount of time. Whenever the conversion does finish, however, you will see a notification in the top right of your screen:
>
Creating a Template
So, how do you set up template commands? As the Template Elements section describes, each template requires 3 things. So, in order to create a new template, you will need to create each of these 3 elements. Hopefully, however, Pandoctor makes this dead-simple to do.
To begin creating a new template, use the dr:temp:set keyword.
Setting Template Name
Type the keyword and then press return. This will immediately jump you to assigning a name for your new template. 
To assign a name, simply type the name of the template. As seen in the screenshot above, this name will be all that you will see in the Script Filter to choose which template you want to run. As an example, I created a new template called "Template Test":
>
Setting Template Defaults
Once you finish typing your template name, hit return and Pandoctor will then automatically ask you if you want your Default Options to always be added to the template command:
>
If you select True, this means that whatever options your template command has, your assigned Default Options will be added to the final Pandoc command. For example, if you have set standalone to be a Default Option, regardless of whether or not you have that option in your template command, Pandoc will still create a standalong document. If, however, you select False, only the options you have in the template will be run through Pandoc.
Setting Template Command
The final element you need to add to create your new template is, of course, the actual Pandoc command.
As the section above described, Pandoctor requires your template command options to be in a very specific format. However, must Pandoc users don't actually type commands into Terminal in this format. In order to make Pandoctor as simple as possible, I have written a script that will convert the standard, short-form Pandoc command into the long-form Pandoctor compliant format. This means that all you have to do is copy your command from Terminal and paste it into this field:
>
As it is currently implemented, there is the possibility of some bugs in the conversion process. This means it is in your best interest to double check the user_templates.json file in your workflow storage folder (you can open this folder easily using the dr:help keyword and selecting Storage). Ensure that the variables are properly used. Also ensure that the all of the short-form options where correctly translated into their long-form version. Remember, you can use the pandoc_templates.json file as a guide for the template JSON format.

I think that Pandoctor has a lot of power, and I hope it proves useful to you. For example, I wrote this entire README in Markdown and generated an HTML file using Pandoctor. If you have any problems, please let me know.
stephen
The Hackademic

I've been waiting for alfred-workflow to fix some bugs. I'll update this workflow in the next week!

Hi folks,
 
Yesterday, Y Combinator finally announced an official Hacker News API (http://blog.ycombinator.com/hacker-news-api).
 
This workflow uses this new API and lets you easily access the latest news with Alfred.
 

 
 
Feel free to give some feedback!
 
Github: https://github.com/fniephaus/alfred-hackernews
 
Download-Link: https://github.com/fniephaus/alfred-hackernews/releases/latest
 

Just updated my Open With Sublime Text 2 Workflow (that was long hidden away here) by merging in a pull request from dbingham that improved stability and handling of multiple files.
 
The workflow works either by keyword ("subl") on your currently selected Finder items or as a file/folder action.
 
Download: http://cl.ly/PW75
 
 
Github: https://github.com/franzheidl/alfred-workflows

I made a nice Alfred workflow for searching through a folder of plain text file snippets that copies the contents and then inserts it into your current focus point. Additionally, it's easy to see, search, and set Mavericks tags on the snippets. Since the whole storage of snippets is done with the file system, it makes it really easy to add and edit the snippets with other means. Go check it out!
 

Yes, it is. I'll try to get that added over the weekend. Really busy with work at the moment

I'm happy to announce that after months of development, I'm ready to make a new workflow and theme repository available to the public as an open beta: Packal. Workflows and themes are taggable and searchable. You can add in the icons, screenshots, long descriptions, and brief ones. There are many different ways to find whatever you need there. Since this is an initial announcement, there isn't much content there yet, except for the workflows and themes that a few kind testers uploaded.
 
Themes are stored as a simple application URL, which means there are no files to download, but, instead, they import directly into Alfred2. Workflows are scanned for viruses after they are submitted but before they are made available publicly. Workflow authors can easily update their workflows just by editing the page and replacing the workflow file there.
 
What is even better is that Packal has its own updater for workflows. So, you have the option to update any workflows that you have downloaded from Packal.
 
I think that these are exciting developments for Alfred, and this sort of repository is what many people have been waiting for since these forums were created.
 
One great advantage for distributing your workflows via Packal is that you do not need to maintain your own download links for your workflows anymore, so you won't need to worry about download limits on sharing services. Another advantage is that it will receive more visibility as it is a place where people can look for workflows and themes without having to page through the impressive number of posts in these forums.
 
So, please, head over to Packal, browse what's there, and, very importantly, submit your own workflows and themes.
 
--Shawn

Hi guys,
 
this workflow lets you manage your Pocket list with Alfred.
 

 
Features
Actions to copy, visit and archive, archive and delete links from your Pocket list (fn, ctrl, alt and cmd) Hotkey to add new links from Chrome, Safari or your clipboard (ctrl + L) Action to deauthorize the workflow (shift) Background cache refresh Supports notifications Uses OAuth 2.0 to authorize the workflow Saves your access_token securely in OS X's keychain  
Github: https://github.com/fniephaus/alfred-pocket
Download: https://github.com/fniephaus/alfred-pocket/releases/latest/
 
Feel free to give some feedback!
 
Cheers,
Fabio

Sure, I could extend the client, so that you can send emails.
 
How about everyone add their feature requests to the issue tracker and vote for features?
https://github.com/fniephaus/alfred-gmail/issues

It can be tricky finding workflows on the forum, so I thought it'd be a good idea to have a list of those true gems you just can't live without to help other users get themselves some great new workflows.

So let's hear about those four or five workflows that make a Mac feel broken when they're missing!

Workflow authors: no pimping your own wares; if they're that good, someone else will mention them   

Here are mine:
Dash by Bogdan Popescu. Search programming documentation with the Dash app. Couldn't code without it. So, so good. ssh by Robin Breathe (isometry). Open ssh connections without grubbing around in Terminal. MarkdownBulletin by Vítor. Convert Markdown to BBcode. Markdown rocks, BBcode sucks. Wrote this post (and all the others) with it. Chrome Bookmarks by Marat Dreizen. No more clicking around in Chrome's GUI, or trying to tell your bookmarks from your history in the URL bar. Application Chooser by Gabe Weatherhead. Search applications by tag. Don't use it often, but it's a true lifesaver when you can't remember the name of that app you rarely use but really, really need right now. As long as you remembered to tag it (which you will after the third time grubbing through /Applications looking for the darn app). Let's hear yours.

Hi folks,
 
I'm working on this new workflow which allows you to control your Gmail emails with Alfred.
 

 
Features Quickly access your latest emails with Alfred Supported actions:Mark As Read/Unread Archive Move To Inbox/Trash Quick reply Add label Automatically uses a dark or light icon set depending on your current Alfred theme Background cache refresh Uses the official Gmail API to securely access your Gmail account Uses OAuth 2.0 to authorize the workflow Saves your access_token securely in OS X's keychain  
Feel free to give some feedback!
 
Github: https://github.com/fniephaus/alfred-gmail
 
Download-Link: https://github.com/fniephaus/alfred-gmail/releases/latest

Hello!
 
I've created a new workflow to help me create RAM drives. It has these features:
- support any types: megabytes, gigabytes, clusters;
- automatically copied created ram drive path;
 
https://github.com/facetheheat/alfred_app_workflows
 
 
 
 

Workflow for Alfred 2 to copy the paths of your current files and Documents to the clipboard in a variety of formats:    * POSIX or HFS paths  * '~/'-shortened POSIX paths * quoted paths * comma- or newline-separated.   Works as a scriptfilter that gives you feedback how your paths would be copied:     All options (except newline-separation) are available as File Actions also:     More details in the README on github.   Download: http://cl.ly/YX1Q  
 
Github: https://github.com/franzheidl/copy-paths-to-clipboard

LibGen
Search and Download PDFs and Ebooks from the Library Genesis project

Version 1.1

Download or upgrade from Packal.

This is a relatively simple workflow that allows users to search the Library Genesis PDF repository.
 
This workflow has only one keyword and one action. Use the keyword libgen to begin a search. Select an item and press Return to begin a download of the file in your browser of choice. The only real oddity of this workflow is that it requires the user to type a period (.) after the query in order to initiate the search. This helps with performance.

Hopefully this will prove helpful for someone other than myself,
stephen

Browse and Manage alfred extension (Download)
 
Search and manage the installed extension.
 

 
Usage
 
alf :: display the installed extensions
alf <search> :: search extension by title, author name, and keyword

enter :: Browse the installed folder in Alfred
ctrl :: Reveal the installed folder in Finder
shift :: Execute extension with the first keyword
cmd :: Open terminal in the installed folder
opt:: Export the extension for distribusion (Default: ~/Downloads, you can refine it in export.json file)

export.json
 
The file format is as follows:
 
{
"workflow-export" :
{"directory" : "~/git/alfred-extension/managealfredextension",
"enable": true},
"source-export":
{"directory" : "~/git/alfred-extension/managealfredextension",
"enable": false}
}   'workflow-export' specifies the directory where .alfredworkflow is exported. 'source-export' specifies the directory where extension source is copied.
 
 
Version History
 
 
2.8 - July 16, 2014
 
Handles the title and author having space  
2.6 - April 11, 2013
Handle subdirectory during export 2.5 - April 8, 2013
Display hotkey informationHotkey information is borrowed from (com.help.shawn.rice) by Shawn Rice 2.4 - April 1, 2013
Fix a bug about pathname with space 2.3 - March 31, 2013
Sort title by alphabetically 2.2 - March 29, 2013
Export feature : Default directory is ~/Downloads Toggle extensions with fn modifier Fix a bug in export function 2.0 - March 29, 2013
Export feature Open terminal Support Alleyoop's auto update plugin Display 'disabled' extension 1.x - March 28, 2013
Initial version

Finally here: Update your workflows with the Packal Updater.
 
There is a longer explanation on the Packal page, so just check that one out, but I'll give you a short version here.
 
The updater will upgrade any workflows that you have downloaded from Packal when an upgrade becomes available. It cannot upgrade any workflows that you did not download from Packal.
 
When you launch it the first time, head over to the settings and configure how you want it to work. If you write workflows, then put in the name that you most often use. If you have a Packal account, put that name in there too. If you do those two things, then the updater won't try to upgrade your workflows. If there are workflows that you do not want to update if, say, you've modified them, then Blacklist them in the appropriate place, and the updater will ignore those workflows. 
 
If you're running Mavericks (or, theoretically, Yosemite), then you'll have access to a nifty little GUI. If you're not, then, well, you don't, but you can still configure and do everything from Alfred itself. See the animated screenshots below for a quick demo of both.
 
Three other notes:
 
(1) The Updater Workflow uses the Alfred Bundler, which has been receiving an overhaul. If you run into some trouble with it, then just go ahead and delete your bundler directory, and it will re-install itself. A newer version of the bundler should be coming out soon that will make some great fixes, but you needn't worry about that because the bundler will update itself.
 
(2) The Updater can send information to Packal about what workflows you have installed, enabled, and downloaded from Packal. It'll try to do this once a week if you do not disable the feature. It is anonymous reporting in that there is no way for me to figure out who you are from the data. Here's the command that I use to generate your unique identifier:
ioreg -rd1 -c IOPlatformExpertDevice | awk '/IOPlatformUUID/ { split($0, line, "\""); printf("%s\n", line[4]); }' If you just plug that into a terminal, then you'll probably see something akin to:
  .
 
(3) The Updater keeps backups of the workflows you've updated, so, if anything breaks, just open the backups folder and double-click the most recent version of the workflow to restore.
 
Anyway, go grab it from Packal, and start updating.
 
(And, as always, I think I've removed all the bugs, but, as I release this into the wild, I expect to find more. Just report them here.)
 
Lastly, the updater can update itself according to my tests. Cool, right?
 
Demo — Packal "GUI"
 

 
 
Demo — Packal Script Filter Interface
 

Hi everyone
 
Since I found many useful workflows on this forum I decided to share a couple of simple workflows I made for my Alfred app.
 
This workflow simply toggles the Natural Scrolling of OS X. I like to enable the natural scrolling only when using my trackpad and disable it when using a mouse and keyboard.
 
Just type "ns" to toggle it ON/OFF.   Download: http://goo.gl/1JhK33
 

 
 
I will post updates if there are any, feel free to post your suggestions and advices
 
Marco

View and change your network location from Alfred.
 


Installation

Download the workflow from Packal or GitHub.

Usage
netloc [<query>] — Show list of network locations filtered by <query> if one is specified ↩ — Activate selected network location ⌘+↩ — Open Network Preferences ​Note: You will probably be asked to enter your password to change the network location.
Licence

This workflow is released under the MIT Licence.

DHCP Toggle
 
Find it on:
Packal: DHCP Toggle Github: DHCP Toggle Repository Short Description
Set your DHCP Settings via Alfred.
 
Long Description
DHCP Toggle allows you to alter your DHCP settings between a manual and an automatic configuration. When you set an automatic configuration, which is normal, your computer will receive an IP address directly from the router that you’re connected to. If you choose manual, you have the option of setting your own IP address. If the router’s IP address is 10.0.1.1, then you’ll be able to get an IP with a prefix of 10.0.1 and a suffix between 2 and 255. If the IP address is already used, then you’ll have to try again. DHCP Toggle will also set your router address to the IP prefix that you use, followed by 1, which is always reserved for the router.
 
You can use this when your Internet connection is weak, or if a router is clogged, or if, for some random reason, the router doesn’t like you connecting with an automatic IP address (the original need for this workflow).
 
Commands
dhcp <arg>
 
Available arguments:
None: defaults to your default IP prefix + random number 2–255 Switch to auto: auto IP Address: 10.0.1.192 Number: 2–255, i.e. 32 Configure c Configuration
 
Default Prefix
You can set a default prefix, the first three numbers of an IP address, which will be given precedence over the other available prefixes. If you just type a three-digit number (between 2–255), then it will set your IP address to DEFAULTIP.NUMBER.
 
IP Prefixes
You can set a list of prefixes that you commonly use, and those will appear in the script filter to choose easily. If no prefixes file is found, then the following list will be populated:
10.0.0 10.0.1 192.168.0 192.168.1 192.168.2 192.1.10 You can add and remove from this list from the configuration option.
 
Passwordless Execution (sudo)
 
If you would prefer to use this workflow without a password, you can select the option to add a record to your sudoers file. The script will add the line
$USER ALL=NOPASSWD:/usr/sbin/networksetup to your /etc/sudoers file, where $USER is your username; so, the $USER will now be able to execute the command networksetup without needing to enter a password. The script checks the syntax with visudo to make sure that it doesn’t bork your /etc/sudoers file. So, it’s safe.
 
Demo
 

 
Credit
Thanks for version 2.0 goes to Pryley (Github | Alfred Forum) who opened a pull request for the added features and contributed some code.
 
Issues
Please report coding issues on the Github issue queue. Other support should be posted on the Alfred Forum thread.

Alright. There is something funky with the Applescript code en2md.scpt. I honestly don't know what it is. But, I rewrote that function as a Python script and updated to version 3.0, now live on Packal. Please update and try enmd again with the debugger on. Let me know if this works for you.

Have you seen Units? http://www.alfredforum.com/topic/2471-workflow-units-convert-currency-length-temperature-weight-and-more/

Overview
TOC Workflow creates, updates and removes a markdown table of contents that can be useful when writing a more complex document. It should work fine when exported to a html document.
Note that, due a bug/limitation of current OSX PDF print function, TOC will not work in a PDF saved/converted by most of writing applications.
How to Use
Create a TOC
open your markdown editor and type your text when you finish it show Alfred and type the keyword toc press Return key the workflow will select the text, copy it, add the TOC and anchor, then paste the text back You can also set a hotkey to create a TOC. Update a TOC
If you have edited the text after inserting the TOC then just run the keyword toc again and the workflow will create an updated TOC.
Remove a TOC
The workflow can also remove the TOC and anchors for good. It can be handy if you e.g. want to work with a cleaner text, without TOC and anchors.
To remove show Alfred, type the keyword toc, hold Command key then press Return key.
You can also set a hotkey to remove it.
Screenshots
Type your markdown text as always and don't you worry about TOC:

Show Alfred, type the keyword toc then press return key (or use the hotkey) to create a TOC and the anchors:

Preview the document to see the TOC:

Download
Before using the workflow for good make some tests and backup your texts first.
Version 1.0 29 Apr 2014 Requires Alfred 2.3 Download Now

Wikify
Your little Evernote Wiki-Helper
Version 2.6
 
Download at Packal
 
This is a workflow in progess, but Version 2.0 adds a tone of super helpful functions for dealing with Evernote for Markdown lovers. This is aimed at making it easier to create a personal wiki on your computer, using Evernote as the backbone. 
New complete documentation on my blog: http://bit.ly/1xA0D44
 
Current Features:
 
Version 2.0 adds four features to 1.2's functionality. Meaning these are the new functions:
Markdown to Evernote (mden)document-specific text snippets (use ^^^snippet^^^ syntax) auto-linking to pre-existing Evernote notes (no special syntax) auto-linking to new Evernote notes (use [[double bracket]] syntax) Evernote to Markdown (enmd) Auto-Link to pre-existing notes for Selected Evernote note(s) (wfy) Auto-Link to new notes for Selected Evernote note(s) (ensel) See the posts below for more detailed accounts of these features.  
NOTE: In order to use a number of these features, you will need the Satimage OSAX Scripting Addition. I've set it up such that this is remarkably easy to install. Simply use the keyword in Alfred wfy:install and the Satimage installer will boot up and walk you through the process.
 
Markdown to Evernote
 
The first feature allows you to write in any editor on your Mac in Markdown, and simply and easily send that data to Evernote as formatted HTML. In order to assign Note Title, Notebook, and Tags, you can use simple MultiMarkdown Headers, or simple symbols:
Title: or # for the note's title Notebook: or = for the note's notebook destination Tags: or @ for the note's tags At import, Wikify comes with a Hotkey or a Keyword to launch this functionality. Simply select your text (ctr + A) and then hit your user-defined hotkey, or pop-up Alfred and type mden, and Wikify will instantly send you Markdown text to Evernote as fully-formatted HTML.  Evernote to Markdown
 
Have you ever wanted to edit your Evernote notes in the plain-text glory of Markdown? If so, this is the feature for you. Using Aaron Swartz's glorious html2text Python script, Wikify will convert the currently selected Evernote note to a Markdown plain-text file. Wikify will save the .md file in its storage folder (~/Library/Application Support/Workflow Data/com.hackademic.wikify/). You can create a Markdown file of an Evernote note, edit it, and then send it back using the twin function. 
 
Let me know if you have any issues, and keep posted for further functionality.
 
stephen