[1] https://community.rapid7.com/community/infosec/blog/2013/01/...
451 karma · joined July 23, 2010
[1] https://community.rapid7.com/community/infosec/blog/2013/01/...
If you do want something from the AUR, are customizing one of the official packages, or are trying your hand at packaging something else, editing PKGBUILD files and using makepkg manually is pretty straight forward once you've done it once or twice.
The community is very helpful and responsive...on the forums, mailing list, and on IRC. Feel free to stop by if you ever want to give it another shot and get stuck.
Blackboard has pledged that they would not enforce those patents against Open Source projects [1][2], but pay services might have trouble coming their way...which would explain the lack of innovation/modernization in the area.
[1] http://www.blackboard.com/about-bb/patents/patent-pledge.asp...
[2] http://www.blackboard.com/about-bb/patents/frequently-asked-...
I'm starting to think it would be nice to have a service where people could share invite codes and keep track of which ones have been used.
I'd like to build some small shelves off the sides of the top level to add some speakers, but beyond that I've been extremely impressed with making the switch.
http://www.wolframalpha.com/input/?i=fifth+heart+curve
...and the 3D surface is there too:
Googling for "command line journal", unfortunately, is not the right way to search for such a beast...
$ cd ~/.vim/
$ git init
$ mkdir {autoload,bundle}
$ wget -O autoload/pathogen.vim http://www.vim.org/scripts/download_script.php?src_id=12116
$ git add autoload/pathogen.vim
$ git commit -m 'add pathogen.vim plugin'
Then, you can just extract each plugin under that bundle directory, or if they're managed by the same version control software you're using, you can use something like git submodules to track the plugins automatically. Add this to the top of your ~/.vimrc file: filetype off
call pathogen#runtime_append_all_bundles()
filetype plugin indent on
...and you're off to the races. Let's say you want to add NERD_tree: $ git submodule add http://github.com/scrooloose/nerdtree.git bundle/nerdtree
$ git submodule init
$ git commit -m 'add nerd tree plugin as submodule'
From then on, you'll be able to track upstream changes to the plugin, and everything is self-contained so you don't have to worry about copying all the files into /doc, /ftplugin, /syntax, etc. The one thing you'll want to do is generate all of the help docs after you have your plugins installed by loading up vim and running: :call pathogen#helptags()
The list of what I use goes a little something like this:@ pathogen - to cleanly organize all of your plugins
@ bufexplorer - to explore your open buffers
@ command-t - a better fuzzy finder for opening files
@ endwise - add proper end statements for ruby code
@ fugitive - fantastic git wrapper
@ matchit - jump to matching brackets or logical statements
@ nerdtree - navigate and manipulate files
@ pastie - post code to pastie.org
@ repeat - adds the ability to repeat functions with .
@ speeddating - Ctrl-A/Ctrl-X manipulate dates properly
@ surround - alter stuff that surrounds text like quotes and html tags
@ taglist - helpful source code browser
Beyond that, I have a bunch of syntax files for various languages and file formats.
Realistically though, if you're just starting out. Learn how to use the editor first, then if you notice certain use cases that you don't have with built-in features (and there are a TON), then start looking for plugins to make your life easier. There's a lot you can do with custom settings and functions in your ~/.vimrc file too, so it will take time (years) to build up what works best for you. Be patient, it's worth it!
If you're curious, you can always find gems by looking through other people's configs: http://github.com/elasticdog/dotfiles
I'd say the user interface needs some work, but the hardware is great and it was really fun to see people's reactions around the office! (the mustache was my idea)