In the process of automating deployments at Tattoodo I found myself having to integrate with CodeKit. After scouring Google for a tool that could automate the compilation, reading a list of files and such from CodeKit, I came to the conclusion, that so such tool exists.
I would hereby like to introduce codekit-compiler, a python hack which will read codekit’s config file, and compile the files using the sameish tools.
Currently it only supports
.less compilation, and
.js minification, which is only some of what CodeKit can do, but it’s enough for me, for the time being.
I’ll be using it as an intermediate step, before rolling a friendlier compilation/minification step.
Usage: Download the script, run it from a directory where
config.codekit is located, hope it doesn’t break. You’ll want to either change the path to
uglifyjs or run
npm install less uglify-js to install them locally.
I would like to thank the people who made CodeKit, for storing their configuration file as JSON. Makes reading it all the much easier.
Feel more than welcome to send a pull request, rewrite this as a gulp/grunt task.
Today I’m adding two plugins, which promise to aid in frontend development. vim-css-color and splitjoin.vim.
vim-css-color will show the used color when editing css (or css like files).
splitjoin.vim enables one to split a single line block (think if or html tag) into multiple lines with
gS and join a multi-line block with
The current .vimrc file.
Today I’m going to add vim-gutentags to my
It promises to simplify the cumbersome maintenance of ones
tags file, which in turn enables you to use vim’s tags features such as
C-] for go to tag,
t to go backwards in the tag-stack and so fourth.
Installing the plugin with NeoBundle, I ran into an issue, which has been reported by someone else. I updated this issue, and am about to start working with
The .vimrc at this point.
This morning, I thought about how to get to know vim. As in really know it.
I’ve been using vim for many years, but there are many things I don’t use because I don’t know about them.
So I’m going to try changing something every day and write about why, so I’ll learn about it in the process.
If you use vim (or another editor), and like me don’t really know it, you should consider doing the same. For science!
I experienced ctrl-p lagging while indexing my projects lately. Luckily it could be solved by changing the indexer to ag and matcher to a python based one.
Details of how can be found at super fast ctrlp article from Patrick Donelan.