:: some new features of bazinga
Some weeks went by now, and some people have started to use bazinga, what I really appreciate. And with some people switching to bazinga, there naturally follow some wishes and feature requests.
stekro, who switched to bazinga some days ago after using nanoblogger, had some good ideas I implemented. For example, he came up with the idea, that an INSERT_GPG feature would be nice. This feature now automatically exports a key from the email address given in the config. For an example of how this works, take a look at the "about me" page.
Another config feature is the new possibility to set a max value for the articles displayed on the main page. You can change the behaviour by setting the MAX_ARTICLES_MAIN configuration option to the desired value. For example:
MAX_ARTICLES_MAIN: "3"
Another feature is the possibility to put your FTP password inside your config in which case you don't have to enter it everytime you push to your remote FTP site. To accomplish this, put this in your bazinga.conf:
PUSH_PASSWD: "yoursecretpassword"
And in case your FTP server uses a different port than 21, I also added a new config entry:
PUSH_PORT: "21"
To download and use bazinga you can either visit the bazinga github page or you can upgrade to he latest version from the AUR. Just search for bazinga-git.
:: how to get multimedia keys working in dwm
After some googling I found out how to get the multimedia keys of my new thinkpad working. As you maybe know I'm using dwm as window manager, and it's sometimes a little bit difficult to get things working. (at least if you aren't nerd enough)
You maybe know, that the multimedia keys are called XF86AudioMute, XF86AudioRaiseVolume, and so on. How do we tell dwm to use this keys?
First thing you have to do is to modify your config.h. You have to include this header-file:
#include <X11/XF86keysym.h>
After that you have to specify the commands to be executed when the keys are pressed. I used amixer for this:
static const char *volumedown[] = { "amixer", "-q", "set", "Master", "2%-", "unmute", NULL }; static const char *volumeup[] = { "amixer", "-q", "set", "Master", "2%+", "unmute", NULL }; static const char *mute[] = { "amixer", "-q", "set", "Master", "toggle", NULL };
So far, so good. Now comes the part where we need the keysyms from the header file. We have to put this into the config as well:
{ 0, XF86XK_AudioLowerVolume, spawn, { .v = volumedown } },
{ 0, XF86XK_AudioRaiseVolume, spawn, { .v = volumeup } },
{ 0, XF86XK_AudioMute, spawn, { .v = mute } },
I wrote this just after the other MODKEY stuff. So far it is working for me!
:: Re-inventing the calendar, Part 1
UPDATE: There is already a calendar like this: here
Today I spent some thought about creating a new calendar system which has equally long "months". I kept the fact in mind, that a year has 365 days (except leap years) and tried to find a number, that modulo-divides by 0. Obviously, 5 did that. So I came up with the idea, that one of my "months" has to be 73 days long.
Of course, I wouldn't call my creation months (because I'm afraid of copyright issues :P), so I need another name. I thought about some good names (still am) and finally came up with the name of sects (from sections, sound better than month, right?).
Now I just have to think about how to calculate something equally to a week....