nikipore

Hello everybody,
 
I just got Alfred 2 today and I thought that the time has come to set an end to the scandalous situation that there is no access to Firefox bookmarks (screenshot):
 
https://github.com/nikipore/alfred-firefoxbookmarks
 
It's written in very basic Python. If anyone wants to join in, there are a couple of things one might do from here:
Quicksearch support display Favicons - EDIT: done better configurability (e.g. the place where places.db resides) - EDIT: done  
EDIT: In the meantime, I've mashed up an IMHO quite useful and generic Python module which takes care of the nuts and bolts of the Alfred API (encoding issues, working directories according to the Workflow Best Practices, plist parsing, XML result compilation, ...). If you wish to use or improve it:
 
https://github.com/nikipore/alfred-python
 
Cheers
Jan

Hello everybody,
 
I just got Alfred 2 today and I thought that the time has come to set an end to the scandalous situation that there is no access to Firefox bookmarks (screenshot):
 
https://github.com/nikipore/alfred-firefoxbookmarks
 
It's written in very basic Python. If anyone wants to join in, there are a couple of things one might do from here:
Quicksearch support display Favicons - EDIT: done better configurability (e.g. the place where places.db resides) - EDIT: done  
EDIT: In the meantime, I've mashed up an IMHO quite useful and generic Python module which takes care of the nuts and bolts of the Alfred API (encoding issues, working directories according to the Workflow Best Practices, plist parsing, XML result compilation, ...). If you wish to use or improve it:
 
https://github.com/nikipore/alfred-python
 
Cheers
Jan

I suggest to introduce a "streaming" mode which sets up the communication Alfred <-> subprocess via stdin and stdout of the subprocess. It would be optimal if the encoding was specified explicitly, I propose normalized UTF-8 (not Mac UTF-8). Since the stdout route subprocess -(stdout)-> Alfred is already there, this would symmetrize the communication.

Open man pages with name and section filtering.
 
The 'man' keyword exploits the x-man-page: protocol handler, so will default to opening in Terminal.app but can easily be switched to iTerm2.app. 'hman' opens pages in your default browser, and 'pman' opens PDFs in the default PDF reader.
  Download / Source
 
 
Usage
man open(1)  # open a specific page
pman style   # open a PDF of the style(9) manpage
man open     # search all sections for pages matching 'open*'
man *open    # search all sections for pages matching '*open*'
man 2 open   # search section 2 for pages with 'open' in the name
 
Enjoy.

I understand the way that escaping and arguments work. I think the hope there, and with string normalization, is to make alp behave a little better when there are special characters thrown into the mix, as I've been advised will happen with one of my own workflows. I'm not sure that it's the best technique, and I haven't done much testing yet, but it's a tilt at the ole windmill. The other element of the logic is that I'd like to reduce the amount of docs-Googling brand-new workflow developers have to engage in. Thanks for the reminder about changing the repo name.
 
Again, it eliminates the need to search the docs for the right formatting codes, which I can personally never remember, and standardizes the way timestamps are used as UIDs for the benefit of Alfred's sorting mechanism. Most of the module boils down to things that anyone could do on his or her own—in fact, all of it does; there's nothing totally "new" in here, as far as I can tell, just a collection of useful "old" tasks made simpler. E.g., yes, anyone could write the ctypes interface to the Keychain functions; the point is that now no one has to.

Hi,
 
I've created a basic workflow that searches the system's menu bar. After having used Sublime Text's command palette I wanted to have a similar system-wide functionality. EDIT: For people that haven't worked with Sublime Text's command palette: the command palette allows you to fuzzy search the entire application menu by keyboard. This saves both time on hunting down the right menu and saves you having to remember all sorts of keyboard shortcuts. For a brief introduction on Sublime Text's command palette see https://tutsplus.com/lesson/the-command-palette/
 
EDIT: Better use ctwise's "2.0" workflow http://www.alfredforum.com/topic/1993-menu-search/ [old download is still available at http://dl.dropbox.com/u/6259900/Menu%20bar%20search.alfredworkflow]
 
The current workflow does not do any fuzzy searching and every keystroke executes the entire script again. My preferred fix to this would be to have a script input that is only executed once, and have Alfred do the subsequent fuzzy matching based on the initial result.
 
Jeroen van der Neut
@jvdneut

Modeled off the red and black from the title pages of old books.
 
Screenshot: 
 

 
Download:  http://cl.ly/MWjz

I made a workflow to kill processes quickly.
 
You can grab it (and read more about it) on GitHub.
Direct download link.
 
Here are some highlights:
Autocompletes process names Learns and prioritizes processes you kill frequently Shows icons when possible Shows CPU usage Shows process paths Ignores case Screenshot:

Enjoy, and feel free to share any feedback you have.

Hi, attached is a workflow for Droplr app (download)
 
"Upload" keyword and then type the name of the file you want to uploaddi
 

Or use as a file action inside Alfred's file browser
 

 
Btw, a little Droplr tip, you can hotlink any image on d.pr by appending a "+,png" at the end of the URL.
 
Enjoy

Ok, just pushed another update. Let me know if it changes anything.
 
It now works perfectly OMM for Python, bash, and every other process I've tried it with.
 
I don't have MacPorts to test with, but at this point I can't repro any issues.
 
Thanks for your help!

Try with anything other than bash and let me know if it works for you. I think the problem is that bash has a hyphen at the beginning of the process name and killall is trying to interpret that as a flag (even though it's in quotes). Any ideas?
 
Thanks for your help with testing this!

Oops, thanks for pointing that out. Forgot quotation marks, so processes with spaces in the name didn't work. Should be fixed now.

Ok, @nikipore, I updated it to use `kill -9` by default. Feel free to re-download.
 
You can still kill all processes with matching names by actioning with command-return.

Cool for the kill -9 part, much safer now. The command-return part is very nice (the best of both worlds), but is broken for me (it shows up, but no action results).

@ngreenstein: I mean that you might have several processes sharing a name; say you have three bash sessions, and only one of them hangs (CPU ~100%), would you want to kill'em all, or just the bad one?