On 2013-01-22, at 09:05, mauro tonon wrote:
Also, awk can't know beforehand if the input string is UTF-8 encoded
or not, so the only thing it can do is to count bytes
Or take the Plan 9 approach of always assuming UTF-8.
-Truls
Speaking of the devil; if a string contains an invalid UTF-8 char, substr
gets a really wierd behavior: $ echo | ~/program/9base/awk/awk '{s =
sprintf(asdf%casdf, 195); printf(\%s\\n, substr(s, 6, 4)); print s;}'
asdfÃasdf
Try changing the second and third arg of substr (set length to 1 and
Sorry, forgot to put [dwm] in the subject.
On 22 January 2013 18:18, Chris Down ch...@regentmarkets.com wrote:
Is there some way to have the focus follow the client being moved when
calling tagmon? I guess I misunderstand the code.
From what I can see, selmon-sel contains the selection,
Hi,
I am running dwm 6.0 (and I tried also without any additional patches and
using the default configuration file) and when I install the newest version
of the Google Talk plugin, open a hangout in Google Plus and select Screen
sharing a window appears for a fraction of a second and then the
Do you have an strace from the plugin?
On 22 January 2013 20:09, Jarosław Rzeszótko szty...@gmail.com wrote:
Hi,
I am running dwm 6.0 (and I tried also without any additional patches and
using the default configuration file) and when I install the newest version
of the Google Talk plugin,
Hi,
I attach straces from dwm (crash) and from awesome for comparision (no
crash). The turning point seems to be the attempt to clone some
process and then the program crashes with the select call visible in
the strace (this is the last call before a segfault, then the program
and strace exit).
Hi,
The plugin also outputs some debugging information to the console,
maybe this will be more helpful:
The program 'GoogleTalkPlugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
(Details: serial 503
On Wed, Jan 23, 2013 at 01:08:15AM +1100, Sam Watkins wrote:
anyway, I say stick with counting bytes, for better performance!
Performance before correctness! Yay!
Whilst we're at it why don't we just always return 0, for better
performance...
On 22 January 2013 22:08, Sam Watkins s...@nipl.net wrote:
anyway, I say stick with counting bytes, for better performance!
