Activity for John Doe
-
John Doe created ticket #84
Suggestion: "Start Program or apply different action to the current file" should remember start mode for the command.
-
Slow deletion
-
sure, here you go. i personally just put the older version of terminus into /share/fonts as separate font and set up xorg to read it instead of newer one. this way i have fontconfig providing new one for everything and x11 version for worker. you should probably just experiment with xft and english/japanese characters combo - if we can specify a list of fonts for fontconfig to lookup characters from there should be no problem, end users will then be able to use whatever characters they want. also,...
-
so, continuing with this - is there a way to select multiple xft fonts? edit - just comma with no space
-
there's also some sort of a bug with japanese characters. every program that uses xft displays them properly for latin fonts worker shows squares instead quriously, japanese characters are displayed normally if you select japanese font, and latin fallback is displayed normally as well, but you can't configure the fallback! without xft worker shows blank space instead of any characters on up to date terminus
-
so, continuing with this - is there a way to select multiple xft fonts?
-
The thing is, it happens only about 1/5 of all times dialog is spawned(and also only with double dialogoue popup, single popups work fine). So on a first glance it screams some sort of synchronisation issue. Perhaps dialog window is processed by the window manager before the window property is set? Is it created with the property, or do you have separate function for setting that? Otherwise i don't know anything about awesome or worker internals, but probably the problem is with awesome.
-
The thing is, it happens only about 1/5 of all times dialog is spawned. So on a first glance it screams some sort of synchronisation issue. Perhaps dialog window is processed by the window manager before the window property is set? Is it created with the property, or do you have separate function for setting that? Otherwise i don't know anything about awesome or worker internals, but probably the problem is with awesome.
-
Yep, comma separated font name input does work nicely, thank you. I didn't really have a problem, just thought this might be some obscure bug you haven't encountered. Maybe you should put the info about comma separated syntax on the font configuration page in documentation(unless it's some very common x11 knowledge)? Some people who don't know about it might be going crazy over this.
-
possible issue in window spawning
-
longstanding unicode problem
1