Re: [bug-gtypist] ideas, implementations, patches.

[clutton]

It seems I started using the workflow by trial and error approach. I
was thinking that bug-gtypist email is someone real email, and I was
wondering how you guys make discussions and which IRC is it.

Anyway, thank you for being nice with me after those strange emails. :)

About one patch per feature, discussion, fixing. - sure, it always was
like this.

I'll start with figuring out relationship about auto* and curses.

Header is not important (it could be <curses.h>, <ncurses.h>,
<ncursesw.h>), what is important is the library we are link to.
I might be wrong, and soon I'll find out, but if this is the case,
header inclusion and auto* detection could be rewritten in more simple
and decent way, some BSD use workaround for building gtypist, they have
library libncursesw.so/a but don't have header ncursesw.h, only
ncurses.h which is simlink to curses.h, ncursesw was developed like
drop in replacement, same definition, different behaviour.

My interest in gtypist is its console nature. There are a lot of nice
and cute projects with ncurses, and making gtypist one of them is
priority for me.

signature.asc
Description: This is a digitally signed message part