A-Qute blog

Instalar Jekyll (y Ruby) en Windows

A.Q. — Tue, 29 Sep 2015 00:00:00 GMT

Pequeña guía para tener una instalación de GitHub Pages en Windows, para testear Jekyll antes de "pushear" los cambios. Recomendado cuando estas haciendo un theme de un blog o creando un sitio.

Instalar Ruby

Se necesita Ruby y Ruby Dev-kit para poder instalar los "gems".

Primero descargar ruby de Ruby Installer. Al instalar, checkear la opcion de "Add Ruby executables to your PATH".

Note

Al 2016-02-09, GitHub Pages usa la versión 2.1.7; la mas cercana listada es la 2.1.8. Podes descargar el instalador de Ruby 2.1.7 en los archivos cosa de asegurarte.

Del mismo sitio, descargar el Ruby DevKit correspondiente a la versión. La descarga es un archivo descomprimible .exe. Descomprimirlo en alguna carpeta sin espacios (por ejemplo: C:\Ruby\DevKit\).

Para "unir" el devkit e instalarlo, seguir los siguientes pasos:

con la línea de comandos ir a la carpeta (cd path\carpeta\)
Ejecutar ruby dk.rb init, esto auto-detecta las instalaciones de Ruby y añade a un archivo de configuración necesario para el próximo paso.
Ejecutar ruby dk.rb install para "unir" el DevKit.

Note

Si da error de "Comando no encontrado" verificar que en el PATH este como [path\a\ruby\]bin\ (notar barra invertida final)

~~Si vas a necesitar "Syntax Highlighting" y elegiste pygments, tenés que instalar Python (para Jekyll 2 o inferior).~~

Al 2016-02-09, GitHub Pages solo acepta Rouge para "Syntax Highlighting" (escrito en Ruby).

GitHub Pages local: instalación de Jekyll y complementos

En Windows no se puede instalar el gem de GitHub Pages por que tira error al querer instalar RDiscount, porque (según cita):

(RDiscount) It uses a POSIX function that is not available under Windows, even if you adjusted most of it.

(Luis Lavena en Super User)

Info

Al 2016-02-09, GitHub Pages solo acepta kramdown; desconozco si sigue tratando de descargar RDiscount (parece que si).

Por esto, es mejor instalar bundler (gem install bundler) y usar un gemfile (llamado "Gemfile") en donde se encuentra el proyecto, listando lo de arriba con las versiones que se usan:

    source 'https://rubygems.org'

    require "json"
    require "open-uri"
    #get versions specific to github
    versions = JSON.parse(open("https://pages.github.com/versions.json").read)

    gem "jekyll", versions["jekyll"]
    gem "jekyll-coffeescript", versions["jekyll-coffeescript"]
    gem "jekyll-sass-converter", versions["jekyll-sass-converter"]
    gem "kramdown", versions["kramdown"]
    #gem "maruku", versions["maruku"] #jekyll 3.0 uses kramdown
    #gem "rdiscount", versions["rdiscount"] #we cant install it in windows
    #gem "redcarpet", versions["redcarpet"] #no support in GH pages (2016-02-09)
    #gem "pygments.rb", versions["pygments.rb"] #no support in GH pages (2016-02-09)
    gem "rouge", versions["rouge"] #for code highlighting
    #gem "RedCloth", versions["RedCloth"] #textile, no support in GH pages (2016-02-09)
    gem "liquid", versions["liquid"]
    gem "jemoji", versions["jemoji"]
    gem "jekyll-mentions", versions["jekyll-mentions"]
    gem "jekyll-redirect-from", versions["jekyll-redirect-from"]
    gem "jekyll-sitemap", versions["jekyll-sitemap"]
    gem "jekyll-feed", versions["jekyll-feed"]
    gem "jekyll-seo-tag", versions["jekyll-seo-tag"]
    #gem "ruby", versions["ruby"] #avoid problems in windows
    gem "github-pages", versions["github-pages"]
    gem "html-pipeline", versions["html-pipeline"]
    gem "sass", versions["sass"]
    gem "safe_yaml", versions["safe_yaml"]

(idea del código de jamesjoshuahill)

Se instalan los gems (con bundler) yendo al directorio con el Gemfile y ejecutar bundle install.

Puede haber problemas con el certificado de https://rubygems.org. Si no se quiere probar, instalar (eliminado rdiscount, sin documentacion) los gems con el siguiente comando (al 2015-09-28):

gem install jekyll:3.0.2 --no-rdoc --no-ri jekyll-sass-converter:1.3.0 --no-rdoc --no-ri jekyll-textile-converter:0.1.0 --no-rdoc --no-ri kramdown:1.9.0 --no-rdoc --no-ri redcarpet:3.3.3 --no-rdoc --no-ri RedCloth:4.2.9 --no-rdoc --no-ri liquid:3.0.6 --no-rdoc --no-ri rouge:1.10.1 --no-rdoc --no-ri jemoji:0.5.1 --no-rdoc --no-ri jekyll-mentions:1.0.0 --no-rdoc --no-ri jekyll-redirect-from:0.9.1 --no-rdoc --no-ri jekyll-sitemap:0.10.0 --no-rdoc --no-ri jekyll-feed:0.3.1 --no-rdoc --no-ri jekyll-gist:1.4.0 --no-rdoc --no-ri jekyll-paginate:1.1.0 --no-rdoc --no-ri github-pages-health-check:0.6.0 --no-rdoc --no-ri jekyll-coffeescript:1.0.1 --no-rdoc --no-ri jekyll-seo-tag:0.1.4 --no-rdoc --no-ri ruby:2.1.7 --no-rdoc --no-ri github-pages:45 --no-rdoc --no-ri html-pipeline:2.3.0 --no-rdoc --no-ri sass:3.4.21 --no-rdoc --no-ri safe_yaml:1.0.4 --no-rdoc --no-ri

El error de certificado es un similar a:

[!] There was an error parsing `Gemfile`: SSL_connect returned=1 
errno=0 state=SSLv3 read server certificate B: certificate verify 
failed. Bundler cannot continue.

Se soluciona de la siguiente manera:

descargar el archivo cacert.pem y guardarlo en (por ejemplo ejemplo) C:\RailsInstaller\cacert.pem.
Settear el SSL_CERT_FILE usando la línea de comandos: set SSL_CERT_FILE=C:\RailsInstaller\cacert.pem. Se puede dejar "permanente" poniendolo en el PATH.

También se puede hacer por proyecto:

Guardar el archivo cacert.pem en el proyecto.

A list item with a code block:

ENV['SSL_CERT_FILE'] = File.expand_path(File.dirname(__FILE__)) + "/config/cacert.pem"

Correr Jekyll

Seguramente va a tirar un error de encoding, estilo:

jekyll 2.4.0 | Error:  incompatible character encodings: CP850 and UTF-8

para solucionarlo ejecutar en la línea de comandos chcp 65001 antes de ejecutar Jekyll.

En la carpeta donde se tiene los archivos:

Si se usó el fix de OpenSSL, hay que usar bundler: bundle exec jekyll serve
Si no: jekyll serve

Abrir en http://127.0.0.1:4000/

Fuentes:

Cambios --------- #. 2016-02-09 actualización a GitHub Pages usando Jekyll 3

Pelican to Nikola (and tutorial)

A.Q. — Sat, 11 Jan 2014 00:00:00 GMT

When I was thinking of moving my blog to this new domain, I thought of using Pandoc as the converter¹. I even created pandy for that. But then I run into the "problems" (ok, I was kind of lazy) of generating RSS, listing posts with certain tags or categories (which I ended up not using), the index and archive, idealizing of using plugins, etc. and gave up.

In the beginning, I would continue using Pelican as is it's easy and customizable, even though it doesn't have Pandoc² support. But later I would be lazy to move to another system (not that I blog much, but I like Pandoc's markdown).

Acrylamid

In my searching, I found Acrylamid which looks pretty good. It's like the programmer/hacker blog generator, where you can do many things, including using template syntax inside your post. How cool is that?. It also has incremental builds, which means that it won't regenerate the whole site/blog again after a little edit, but only what it was changed.

Other cool things include:

different meta tags: you can choose between MultiMarkdown (like Pelican), YAML or rst.
the draft status is a boolean. Yay!.
you can include template syntax inside your posts and you can even use the configuration variables!
automatic summary/intro
user custom acronyms and abbreviations in a text file.
the views things that looks cool that I couldn't understand first but then I got the hang of it (they are very customizable)
colored command line output. THANK YOU!
out of the box pingbacking to other blogs and twitter posting.
info about the blog: how many published, drafts, tag usage count. Also when was last compiled, cache size...
execute shell commands in the post: like listing a directory, include another file, etc.
serve the site with a command
post-processing filters

It doesn't have categories (but by using views seems like it's posible), automatic galleries creation (but you can use template syntax inside the post, so is covered) and the theme creation it's not so automatic: you must list all the files that the theme uses inside an __init.py file.

I really wanted to use Acrylamid, even without the missing bits, but it was kind of "complicated" to set up on Windows if you wanted to use python-magic (at least I have problems with it). I skipped that part but for some kind of reason I was getting errors with the locale setting. I tested it with "Linux locale" and "Windows locale" and both threw me errors.

Nikola

Then I remembered I once stumbled upon Nikola, originally created by an Argentinian guy, so yeah, I had to try it out :P.

It does have Pandoc support; but it's not as "feature rich" (or easy customizable) as Pelican, and the documentation it's not so "complete" if you will. There are a couple of things that are not documented and you must find it in the Google Groups, GitHub or looking in the code. And also, not so feature-cool like Acrylamid. However, I think it's on a good track and it's the newest of the three.

It has cool things too:

incremental builds (like Acryamid)
automatic gallery creation
categories (like Pelican)
easy themable (like Pelican)
serve the site with a command and it has "Live" re-rendering
retired posts (so no 404 errors)
redirections (in case you can't use .htaccess)
deploy commands (a bunch of commands to run, so you don't have to script it)
post-processing filters
internationalization support (the site/blog interface can be in many languages)
password protected posts/pages
"Schedule" posts/pages
Wide range of (3rd party) comment systems and AnnotateIt support.
reStructuredText Extensions (if you use that).
Support for Twitter cards
raw post/page support (to show the source in text)

The draft state is applied in the "tag" metadata instead of a separate one, and they are deployed by default; it has no color support for the command line (but I think it's in the talks) and the "show source of the post and copy it" it's enabled by default.

The moving

Install Nikola

You start first by getting Nikola and installing it. By default, it uses Mako as the template engine, but it has support for Jinja2. You can read about the dependencies in the documentation page and if you want, you can use pip install -r requirements.txt or requirements-full.txt for the whole thing.

If you are running Windows, you must download and install the compiled versions of lxml and pillow. You can check in their PyPI pages or you can go to http://www.lfd.uci.edu/~gohlke/pythonlibs/ and get them there. Remember to download and install according to your Python version and architecture (32 or 64 bits).

Initiate

To initiate or create an empty site with the default settings and folder structures, run either nikola init path/to/mysite or, if you want some demo content, nikola init --demo path/to/mysite.

Convert metadata

Pelican uses the Multimarkdown style of metadata while Nikola uses something similar: the same syntax but with .. in front.

An example would be:

Title: nice title! :D      # Pelican
.. title: nice title! :D   # Nikola

You can do that by hand or download my python script to take care of that. It also moves "draft" status to Nikola's tag, and Pelican's summary to Nikola's description (activated by default).

Note

Nikola doesn't have/see the "modified" meta key internally, but you can have it like a custom key. You just access it differently in the themes.

Translations

If you have posts or pages translations you must pay attention: Nikola handles the translations differently from Pelican. While in Pelican you only set the same slug or title in the posts, and have different file names (I think); Nikola relies on the file names.

The easiness of this depends on your setup, but you must end up with something like: nicefile.md for the post in default language, and nicefile.md.es (spanish content) for the translated file.

The cool thing of this is that you don't have to duplicate the meta tags. For example, you just create the "tags" meta key in the default language but don't specify it in the translated one. So when you update, you do only in the "master" or "parent" file and the "child" just copies it.

If you don't feel like having duplicated metadata between files, and after you renamed and converted them, you can run this python script to delete them. Remember this is optional (or at least it didn't break my setup).

Images paths

The syntax on this is also different but it can be easily done with search and replace. You can use whatever you want, like grep. If you are on Windows, I recommend grepWin if you want something with a GUI. This changes from setup to setup, but my settings were:

For markdown syntax:

Search (|filename|../../images/
Replace (/images/

And for HTML:

Search <img src="../../static/images/
Replace <img src="../images/

Links between posts

Again, this is totally different between the systems and it's going to be very easy or really difficult depending on your setup: Pelican uses the filenames for linking content while Nikola uses the slug of the post.

If you have the filename like the slug (or very similar) you can search and replace again. Like:

Search: $\|filename\|(.+)\.md$
Replace: (link://slug/$1)

I recommend doing it after the images, and you must check the links afterwards.

Plugins syntax

I didn't use many plugins that used syntax in my posts, just only one: interlinks. This was easilly done with search and replace.

Other Nikola stuff

Locale in Windows

If you are going to use the internationalization in Windows, you must configurate your LOCALES as (example):

LOCALES = {'en' : 'English_United States', 'es' : 'Spanish_Argentina'}

It doesn't matter your Windows language setting, I think it only accepts english locales (I tested it with Windows in Spanish and it worked).

Linking internally

If you want to link to another post, tag, archive, etc.:

gallery: link://gallery/gallery_name
tags index: link://tag_index
tag's page: link://tag/tagname
tag's RSS feed: link://tag_rss/tagname
blog's index page: link://index
index [NUMBER] page: link://index/NUMBER
per-year archive: link://archive/
posts of [YEAR] link://archive/YEAR
blog's feed: link://rss
other post: link://slug/the-nice-slug

Pandoc

As Pandoc uses the extension to recognize the input, you must configurate that extension in the COMPILERS option in the configuration file. If it's not found, it uses Markdown as default.

While it worked for me using markdown, it didn't exactly work with some others, like Mediawiki. I don't know why.

Posts folder and subfolders

Nikola preserves the folder structure of the posts in the subfolders. If you have file_g.txt inside folder_abc, that structure is kept in the output. It can be good if you want to use it as categories in the output. There is no way to configurate it in the configuration.

In Pelican you can have many subfolders and sort of categorize your posts as you wish, and the output is configurated (by default, by date) as you want.

Testing

Initially your posts go to a posts folder in your root and the pages in story. The images folder would go to files. You can configurate all of this in the configuration file.

After configurating your conf.py, which is very well commented, you can try it.

Build the site with nikola build. Then you can drag and drop pages to a browser or use the serve command: nikola serve and pointing your browser to http://127.0.0.1:8000

Because I hate opening an HTML block tag and the markdown inside is not parsed. I know, it's said in the markdown reference, but hey: it's 2014 and I need that. But I still love the admonition implementation in Python-Markdown ↩
Which now I see it looks pretty easy to implement. Oh well. ↩

GitHub Pages for projects

A.Q. — Wed, 01 Jan 2014 00:00:00 GMT

Simple steps to create GitHub Pages for projects/per repo (not user nor organization) plus some other stuff.

The steps are for CLI and for GitHub for Windows (TortoiseGit is "similar" to Git CLI) and Git beginners oriented, who search for easiness and not so much fuss. However, if you're confortable using SVN, you can use it (see clients in GitHub).

Abbreviations and vocabulary:

git CLI: Git used in a terminal/command line.
GW: GitHub for Windows.
Tortoise: TortoiseGit.
Server: Where things are "hosted" (like GitHub). This doesn't exist in Git, but this is how beginners can understand better (remote repository).; "Central server" if you're comming from SVN.
repo: To make things easier, take "repo" like "principal or remote repository" or "server" (see definition).
origin: This is how you name the original "remote repository" and by convention the 'primary' cetralized repository.
c-p: commit followed by push

Programs for Windows

In the beginning, having Git in Windows was hard (because it was created by and for Linux) but now there are many options. Usually, if you are only going to use GitHub, GW is recommended. However, if you want to use Git for other things (like creating "servers" locally to play or test) I recommend TortoiseGit + msysgit (git CLI) instead:

you can use it for other things and not only for GitHub ("reads" the github:// protocol)
you don't have to mess around with the PATH if you want to use git CLI (it installs in %appdata% and you can't only include bin\)
msysgit comes with "git Bash"; a cool CLI with colors that shows in which branch you're in; what is more, you can customize it with .bashrc.

Create repository

In GitHub, create a repository with the desired name. You can log in and go to https://github.com/repositories/new o clicking in the "book".

"Activate" GitHub Pages

It automatically activates when you create a branch called gh-pages.

From web click in branch master; in GW click in master at the top. Search for gh-pages and press create branch. With CLI would be (previously cloned, look below):

$ git checkout --orphan gh-pages    # branch local

Info

--orphan creates a branch separated from the rest of the repo (without parents). First, the branch is created locally and then sent to origin (steps below).

Get it in desktop (to work with it)

From GitHub click in Clone in desktop (that GW or Tortoise will recieve) or from CLI:

$ git clone https://github.com/user/nice_repo.git

Prepare gh-pages branch

Switch to gh-pages. In CLI, if you used the above command (git checkout --orphan gh-pages) it switches automatically, otherwise git checkout -b gh-pages to switch and create a local branch called "gh-pages".

Info

When switching branches, Windows Explorer "refreshes" the folder with the content of the selected branch.

Delete all the files (because they're from master and we don't want them) and we c-p.

$ git rm -rf .                      # delete everything
$ git commit -m "Initiating gh-pages"
$ git push -u origin gh-pages       # send branch to origin

gh-pages as default and delete master

This is optional, depends on your workflow or usage idea. If you're only going to use gh-pages, you can use it as default and delete the master branch.

To make it default (and not use master), in GitHub, go to settings > (settings >) Default branch and select gh-pages.

To delete master you must have gh-pages as default. Then, go to the branches listing and click in Delete branch. With CLI:

$ git branch -d master     # delete local
$ git push origin :master  # delete from repo

It's alive! (Testing file and upload)

Create an index.html, add it and c-p.

$ git add .                   # adds all
$ git commit -am "First commit to pages"
$ git push origin gh-pages

(-a is an abbreviation of add)

Wait a couple of minutes and check if index is uploaded in: http://user.github.io/projectName/

Custom domain

As you probably don't want to enter to http://user.github.io/projectName/ because is too long or it's kind of unprofessional, GitHub allows you to assign a custom domain/subdomain to it.

You only need to create a CNAME file which has the domain/subdomain that you want to use, in the root of gh-pages and change the DNS in host/registrar:

With a root domain (www.example.com): create a new A record with the IP to 204.232.175.78.
With a subdomain (sub.example.com): create a CNAME record that points to GitHub user subdomain (user.github.io). This allows the DNS to adjust automatically to GitHub's IP; you can use a A record but it won't update automatically.

404 pages! (Everyone loves error pages)

It's easy too: create a 404.html in gh-pages's root and done (don't forget to add and c-p).

Changes

2014-01-02 Rewritten to be more explanatory.

Windows 7: Arreglar los iconos en Explorer

A.Q. — Thu, 12 Dec 2013 00:00:00 GMT

Con esta era de usar programitas varios para sincronizar, otros para control de código, y otros que no puedo recordar ahora; es necesario tener los overlay icons en Windows Explorer:

Personalmente se me desaparecían y, aunque limpiara la cache de los programas, nunca aparecían. Hay algunos que podes vivir sin ellos, pero otros no. Capaz instalaste un programa y te desplazó los de otro.

¿Pero cuál es el problema? Que los genios de Microsoft limitan la cantidad de iconos que se pueden usar a unos meros 11 iconos totales para el usuario. WHAT THE HELL.

Para arreglar el tema hay que pasar por el registro. Entrá al bonito regedit y navegá hasta HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ShellIconOverlayIdentifiers\. Antes de tocar mano, hacete un backup del .reg.

La idea es que de los 30 que debes tener, solo elegis los 11 mas importantes. ¿Cómo decidis la importancia? renombrandolos, porque Windows los elige por orden alfabético. Poneles números adelante o "z", "x", "y", esas letras que no se usan. Yo prioricé algunos de TortoiseSVN, un par de Dropbox, y el resto como sea el orden.

Una vez que estás feliz, reiniciá el explorer.exe: Administrador de tareas > matar explorer¹. Después lo inicias en Nueva tarea (o si queres desloguearte y loguearte, si queres reiniciar también, pero no hace falta).

Fuente: oliverpearmain: Dropbox and TortoiseSVN icons overlays in harmony

Kill, kill, kill! ↩

pandy

A.Q. — Wed, 11 Dec 2013 00:00:00 GMT

pandy is a command line wrapper for pandoc + cool stuff (if you use markdown -> html)

Basically takes a file/folder, input the markup to convert from, the output markup and runs it through pandoc.

Usage

To use the script, just call it with something like:

pandy source format_from format/s_to [other options]

Features

A bit easier syntax around pandoc commands (I can't never remember them)
Output folder keeping or not the folder structure
Source can be a file, a folder or a .list containing file paths
Formats: some of them have abbreviations (see below)
Output format: you can have more than one! just separate them with spaces
You can create a nice book (html, just adds navigation links between files). If you don't like/want "Next-Prev" navigation links, you can use the file's title. It creates a nice simple index file or you can include your own.
Use a config file: so you don't have to remember all the arguments or write a "wrapper" script for a "wrapper" script :)
[TOCME] support. That means that a file that has it, will have a TOC. No more separating files: these ones with TOC, these ones without, and finally place them in the same folder.
If you use markdown and convert to HTML there are some goodies for you! abbreviations (real abbreviations, like that they are parsed and not ignored as pandoc does) and admonitions.
"WikiLinks" for your custom index file!

For more information and explanation, go to pandy project page.

svnlog: make changelog from SVN

A.Q. — Mon, 02 Dec 2013 00:00:00 GMT

svnlog is a python script to create a changelog from a repository log.

Examples of output (default):

2013-11-25:
    changed arguments (better handling)
    fix: output path with one file
    fix: finding <h1>

2013-11-19:
    fixed: now files are saved according to source dir tree
    + option to save files in one depth dir

2013-11-19:
    + relative links for book

You can group that too:

2013-11-25:
    changed arguments (better handling)
    fix: output path with one file
    fix: finding <h1>

2013-11-19:
    fixed: now files are saved according to source dir tree
    + option to save files in one depth dir
    + relative links for book

It has some basic options:

Show author with --show-author or -a
Show revision number with --show-rev or -r
Show time with --show-time or -t
Prefix with a char using --prefix
Reverse the order (default: new to old) with --reverse
Specify date or a range (ISO 8601) with --date. You can leave the second date empy (date1:) to include today
If you are better with revision numbers, you can specify one or a range with --revision. You can leave the second revision empty (rev1:) to include HEAD revision
Group the dates with --group
Also group revisions with --subgroup
Or group dates but show it inline: --inline

Just make sure you have a SVN CLI in your path and then run svnlog with the options you desire

pymd: wrapper for Python Markdown

A.Q. — Sun, 17 Nov 2013 00:00:00 GMT

Hey!

pymd is now available in PyPI. That means that you can install it like pip install pymd :)

pymd is a command line wrapper for Python Markdown library but having a full HTML file instead of only what it's originally parsed.

Features

Batch process files (in folder or in a .list) with .md, .txt or .markdown extensions
Specify an output folder (with automatic creation)
Includes all the extensions installed by Python Markdown and you can even specify your own!
Merge files into one big HTML or create a little book with navigation links. You can even create your own index!
CSSed: leave the no-so-ugly embeded CSS (you can even switch between sans and serif fonts) or link to one of your own if you prefer.
Headers for files! So you can share the same metadata (like your beautiful name and the creative title of your work) in all the files or when you merge the files and forgot to include the main title of your project.
Wiki links: [](file|path) -> [title linked file](output_path)
Made with love <3

Find more information and examples in pymd's project page

foobar2000 theme: Tomorrow Night Bright

A.Q. — Thu, 07 Nov 2013 00:00:00 GMT

Playing with foobar2000's Default UI, I made this minimalistic/simple theme with Tomorrow theme colors (Night Bright version).

Screenshots

You've got the menu + playback controls in the same line. Underneath, seekbar + playlist dropdown. In the status bar is the time, rating (view) and volume.

There four views/tabs in total:

"Now" has the active playlist, grouped by artist (in blue) + album (green). Tracks only show their title (red) and comment (orange).

"Lyrics" has the cover art and the lyrics.

"Meta" is the playing track details.

"Library" is self explanatory.

There's no playlist list (only the dropdown) because I couldn't find one that prevents me from accidental deletion :P. If you want to manage them, go to View > Playlist Manager

Requirements

Place the EsPlaylist configuration (foo_uie_esplaylist.dll.cfg) in [foobar_home]/configuration and the theme (tomorrowbright.fth) where you please.

Import the theme (Preferences > Display > Default User Interface > Import theme). In the playlist, right click > grouping > inline - Tomorrow night bright. In the lyrics panel, edit the preferences (panel preferences) and change the highlight color to RGB 236,206,88 (yellow).

The "headers" colors (in playlist, the %artist%, %album%; and in "meta", the "metadata", "location", "other"...) is configurated in Default User Interface > Colors and fonts (if you don't like violet).

If you want to change the control buttons, you must use 16x16 .ico files.

The Windows theme is SlanXP2 for 7, that's way the DUI looks better than defaults.

Box: WebDAV access

A.Q. — Sun, 04 Aug 2013 00:00:00 GMT

To access to syncing servicies via WebDAV, and see them in a file manager without installing the client -> wait to load -> index -> do the sync dance just to get one file¹, it's priceless².

I decided to do this because I wanted to do something that needed a FTP. Lately (or always was like that), you can't create a FTP account only, you must create a web site first. Not interested. I don't have a server/computer (proyect pending) acting as a server and install FileZilla. Damnit. I remembered the sync servicies that I have an account with and jumped into using them.

I chose Box. I thought into uploading the files via the web interface, given that the synchronization is a bit bad, but I realized that SugarSync has the "SugarSync Drive" feature, that allows you to access your file through a file manager. I started to search if Box had something similar.

It has FTP access but only for paid accounts. Then I read about WebDAV. Tried to configurate it and, after struggling for minutes, here is how to do it in Windows (7)

Windows Explorer

In "Computer" (the old "My PC"), go to Map network drive

Select the drive (doesn't matter apparently), check Reconnect at logon. Click on Connect to a Web site that you use to store...

In the new popup window, select Choose a custom network location

Now the fun part that gave me headaches: the address.

You can input:

For the whole folder/account: https://dav.box.com
For specific folder: https://dav.box.com/dav/FOLDER

New popup window for log in. Enter the Box user/e-mail and password.

Optional, in the next window rename the folder:

And here is the hardwork done:

If this doesn't work for you, you can use CarotDAV (to view al the servicies in one portable program), the famous Total Commander or BitKinex.

BitKinex

Download BitKinex. Install normally, but I recommend (because I read somewhere) uncheck the "I want to configure data source now" option (apparently does nothing)

Once initiated (yes, it looks very small for some reason), look for Http/WebDAV, right click > New > Http/WebDAV and enter a name.

The address is similar to above: dav.box.com, select SSL. Enter user and password:

I also read (optional) that you can include a path in the Site map (don't know why, didn't noticed a difference). You configurate it going to Site Map (under where you're now/Server) and adding/modifyng the path with /dav, picking Directory WebDAV-compliant

And done, you just doble click it to connect:

Source: Box zendesk

The mayority of people use the servicies as file hosting ↩
literally. Nowadays, the operative systems have the feature built-in (more, less or not bugged) ↩

proDO: super simple bug/issue tracker

A.Q. — Fri, 26 Jul 2013 00:00:00 GMT

Atención

Si no te interesa la historia del por qué se escribió el script y/o no queres saber sobre programitas, adelantate hasta acá

Background

Cuando desarrollas o escribis código (o palabras, por qué no) necesitas algún tipo de bug/issue tracker. Eso es normal para proyectos grandes o con varias personas, pero al ser un solo individuo o el proyecto es chico, todas las opciones son como mucho.

A algunos no les importa e instalan grandes bug trackers, otros usan algo mas simple. Otros vamos por la old school y escribimos en papel. Otras escribimos en un .txt, que puede ser un simple archivo o con esos ToDo.txt/taskwarrior¹.

Si el proyecto es medianamente grande (más grande que un mero script), escribo en papel. Si es algo simple/un script, anoto las cosas dentro del archivo, como varias personas.

El problema que tengo es que me gusta listar todas las cositas esas con el numero de linea y/o click que me lleve a tal. No todos los editores lo hacen por default (creo que las grandes IDEs), seguro hay un plugin que ni ganas de configurar. Se puede hacer una búsqueda, que es lo mas cercano a lo que quiero.

Uso dos editores de texto dependiendo del trabajo que tengo que hacer: Sublime Text para trabajos "grandes" (por alguna razón) y Notepad++. En ambos se puede hacer búsquedas por proyecto/archivos abiertos, la diferencia es que en Sublime Text te abre una pestañita de miercoles con los resultados (not fun), y Notepad++ te los muestra en una ventanita dockeable (good):

Qué no me gusta de esto? La forma en que te lo muestra² y el hecho que Notepad++ tiene otro tipo de regex que, según expertos, es mas pobre.

Lo más lógico es usar grep. Si usas Linux, ya viene por defecto, sino con algo como Cygwin en Windows (u otras variantes). Hasta le podes poner colorcitos pero solo a una cosa (el string encontrado). No está mal tampoco pero no es muy limpio³:

Si no te gustan las terminales/lineas de comandos pero queres usar grep, hay varios programitas que te dejan (hacer una especie de) grep⁴.

Tenes Agent Ransack, donde quedaría asi:

Para este tipo de trabajos no me gusta por que tengo que clickear archivo por archivo (not fun).

Y grepWin, donde hay que tener cuidado de clickear solo en "Search" y seleccionar la opción de "Content"

Este no estaba tan mal, pero eso de abrir programa > rellenar datos no me convencia mucho. Por lineas de comando solo podes poner el path y qué buscar (que no esta mal) pero quiero que, por lo menos, esté seleccionado el "Content".

Say hi to proDO

Como estoy aprendiendo Python y mas que nada lo estoy usando para hacer varios scripts⁵ y reemplazar/dejar de dar vueltas con los batch, me decidí a hacer el mío.

Con los ejemplos anteriores, queda asi:

Pero si tenes colorama instalado queda asi (con mas onda):

Datos:

Solo busca las palabras TODO y FIXME (es case insensitive: también podes poner ToDo, todo, tODO, etc)
Por default, al correr el programa te lista los archivos desde donde corre el script ⁶, ignorando los .bak
Se puede especificar la ruta a buscar, corriendo proDO.py -s/-source [rutita linda]
Se puede eliminar las lineas con: proDO.py del/d [archivo] [linea] (automaticamente hace un backup (.bak) del archivo por si se pone loca)
Si necesitas ejemplos de lo de arriba o queres mirar qué linda hice la ayuda: proDO.py -h
Si no queres escribir proDO.py (la extensión es importante en Windows), podes crear un "wrapper batch": en (ejemplo) proDO.bat poner: proDO.py %*. Guardás y listo, ya lo podes llamar como proDO

Decarga y más información en la página de proDO

Que esta lindo, es para linux o con Windows + Cygwin, pero es mucho trabajo para configurarlo para esto. ↩
Mentira, me acordé después de hacer el script. Lo testeé y no anda mal. Sólo que no se puede buscar por proyectos, asi que hay que escribir el path en la búsqueda o abrir todos los archivos. ↩
Se puede limpiar/formatear con awk, pero tuve problemas con Cygwin que no traía el ejecutable para la herramienta (!) ↩
No sé exactamente la diferencia entre grep y buscar dentro de los archivos (con regex), yo lo uso intercambiablemente. ↩
por que se me complicó con eso de buscar una IDE para la parte gráfica. ↩
en Linux es más fácil (por lo menos en xfce): botón derecho > terminal. En Windows tenes que apretar shift + botón derecho. ↩