Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#625 closed Defect (Fixed)

/me command outputs without translating \001 into CTRL-A

Reported by: bluknight-colloquy@… Owned by: timothy
Component: Chat Core (IRC) Version: 2.2 (Mac)
Severity: Blocker Keywords: /me ACTION
Cc:

Description

currentl nightly build (2D40) has broken /me support -- outputs to channels as:

<user> \001ACTION waves\001

Change History (13)

comment:1 Changed 13 years ago by Phil Larson <phil@…>

Not seeing this on my end.

comment:2 Changed 13 years ago by akempgen

works for me, too. what encoding are you using? what server is that? any other info you have?

comment:3 Changed 13 years ago by anonymous

This was discovered on a private server, using Lossless ASCII. I'll get more information tonight when I'm off work and can access the system running the affected version.

comment:4 Changed 13 years ago by timothy

Wow, I think this is a bug. I never thought about Lossless ASCII in this case. I am not sure what to do... Might need to remove Lossless ASCII.

comment:5 Changed 13 years ago by anonymous

This happens for me as well. To clarify this has happened with some previous builds, but I can't say for sure when it showed up. But what happens is:

  1. I type "/me does an action"

2a. I see "username does an action"
2b. The rest of the channel sees "username \001ACTION does an action.\001"

This is with Western (ASCII) encoding, connecting to us.undernet.org servers. However, when connected to a private, fairly hacked up PIRC server, it comes through fine.

comment:6 Changed 13 years ago by anonymous

okgurl: how come your /me is all fucked up?
Kar98: dunno, is it?
okgurl: <Kar98> ACTION high-fives Smitten
Kar98: well, that's fucked up
Kar98: stupid thing

Encoding non-lossy ASCII
Version 2.1 (2D41)

comment:7 Changed 13 years ago by anonymous

Still have this problems with the current build, can it be some switch in a pref. file?
2D16 is behaving normally, anything above produces the \001\ACTION stuff

comment:8 Changed 13 years ago by eldang@…

I've started having this problem since last week's update, and changing the encoding doesn't fix it. It also shows up fine in my own window - it's only users on other clients that see the ACTION.

comment:9 Changed 13 years ago by timothy

  • Resolution set to fixed
  • Status changed from new to closed

This is a problem with non-lossy ascii. I have removed this encoding in [3339] and it will default back to UTF-8. Non-lossy ascii should have never been in the list for this reason.

comment:10 Changed 13 years ago by eldang@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

I get it with any encoding - UTF-8 is what I've always been using, and prior to last week's release I never saw the bug, but now I do, regardless of what encoding I have set.

comment:11 Changed 13 years ago by rinoa

  • Resolution set to fixed
  • Status changed from reopened to closed

Please do not reopen a ticket until you test the fix, which hasn't even been released yet.

comment:12 Changed 13 years ago by timothy

Using Colloquy set to UTF8 this is what gets recienved by a telnet user:

:xenon!n=timothy@c-67-180-226-148.hsd1.ca.comcast.net PRIVMSG #colloquy :ACTION tests

With the 0x1 control chars being actual characters.

comment:13 Changed 13 years ago by timothy

Using Non-lossy ASCII the telnet user does see \001.

:xenon!n=timothy@c-67-180-226-148.hsd1.ca.comcast.net PRIVMSG #colloquy :\001ACTION tests\001

Note: See TracTickets for help on using tickets.