>On Fri, Oct 3, 2014 at 3:25 PM, CustaiCo
>wrote:
>> The XBell() call currently used when a bell is recieved sends a message
>> to the X server, but if the X server doesn't know how to sound it,
>> it just gets ignored and I have not been able to find anywhere in x.org's
>> code a way to configur
When I try to run a python program that uses urwid[1] to provide a
curses ui is, strange things happen. All the text is messed up, which
continues after exiting the program. A comment in the AUR verifies that
someone else has had the same problem.[2] This does not happen in st
0.4.1.
To reprodu
Hello,
On Fri, Oct 3, 2014 at 3:25 PM, CustaiCo wrote:
> The XBell() call currently used when a bell is recieved sends a message
> to the X server, but if the X server doesn't know how to sound it,
> it just gets ignored and I have not been able to find anywhere in x.org's
> code a way to configu
The XBell() call currently used when a bell is recieved sends a message
to the X server, but if the X server doesn't know how to sound it,
it just gets ignored and I have not been able to find anywhere in x.org's
code a way to configure the action that the server does.
However, if you use XkbBel
On Thu, Oct 02, 2014 at 05:23:39PM -0700, Kartik Agaram wrote:
> > Here is a list of things I think are suckless-specific in practice:
FRIGN did cover it in detail but I'd like to point out some further
details that I've noticed.
> > - C code (most often) written in a plan9 like style.
If you wa
On Thu, 2 Oct 2014 17:23:39 -0700
Kartik Agaram wrote:
> > - Most often only one C file.
one C-file per program.
The most important part is forgotten though: We not only write mostly C,
but also try to use POSIX(01-08)-interfaces and established extensions.
Concerning the C-standard, we favor
