mudlet-makers team mailing list archive

["Brian M. Workman" <1099688@xxxxxxxxxxxxxxxxxx>]

I only mentioned putting in spaces as some kind of workaround if for
some reason mudlet is drawing instead of printing ascii text. I haven't
actually looked at the source, but I might now.

The more elegant way would be to actually print the character Which
would be preferable. Unless it's stripped (which would be a strange
decision to make).

Triggering for it seems to put the onus on the user to know what they're
doing, script-wise. That seems like a power-user way to look at things.
I haven't seen a mud client not process the \t character before, but I
would imagine it would be desirable to present at least the more
commonly expressed codes. A lot of MUDders are not very technical

Telnet just prints the character instead of using spaces:
http://www.youtube.com/watch?v=oQt_mr5NMwI

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1099688

Title:
  does not resolve the \t character

Status in Mudlet the MUD client:
  New

Bug description:
  Mudlet does not seem to support the \t character (tab). On muds where
  this is used, Mudlet prints nothing. It does not indent at all. What
  is expected is either showing the tab character or 8 spaces, but
  neither happens, and things that are aligned using tabs make things
  look all wonky, like maps, etc.

  Mudlet: 2.1
  OS: OSX 10.8.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1099688/+subscriptions