Quassel IRC

Yes, this is still valid; Easiest way for me is to fire up ii and e.g. `echo -e 'foo\010bar\007' >in`.

MR 153

I’ve written a patch to replace the control characters by an UTF-8 character that represents them visually.

Also, these are in-depth details on the steps to reproduce the issue, just in case:

1. From Quassel, connect to the room #quassel-issue158 in FreeNode.
2. Install ‘ii’.
3. Run it. For example:

    $ ii -i . -s 83.170.94.214 -p 6665 -n QuasselIssue158

4. From a different terminal, enter the directory generated (‘83.170.94.214’) and run:

    $ echo "/j #quassel-issue158" > in
    $ cd \#quassel-issue158/
    $ echo -e "foo\007bar\010" > in

5. Watch the result in Quassel.

Expected result: meaninful representation of the codes.
Actual result: meaningless characters.

To print the whole list of control codes, use the following script:

    for i in {0..31} 127
    do
        hex=$(echo ""$i" "16" o p" | dc)
        echo -e "$(printf "%03x\n" 0x$hex). foo\\x$(printf "%02x" 0x$hex)bar" > "$1"; sleep 1;
    done

Run it followed by the path to the target ‘in’ file:

    $ ./script.sh "83.170.94.214/#quassel-issue158/in" 

Merged in 4676ff82af669595edaf090c97a28161d67782a1