mudlet-makers team mailing list archive

[Heiko <1099688@xxxxxxxxxxxxxxxxxx>]

You haven't explained how you'd solve my 3 open questions.


Am 26.02.2013 23:08, schrieb Jeremy Akers:
> Again, you asked for an RFC, and I provided one.  I never said my game
> supported it.  In fact RFC 654 doesn't require support from the game
> side, because it specifically says:
>
> "The guiding rules are that:
>
>        1) if neither data receiver nor data sender wants to handle output
>        horizontal tab characters, the data receiver must do it,"
>
> Mudlet, in this case, is the data receiver.  It should be able to handle
> them.  All you'd need to do is add a configuration option where users
> can specify how many columns they want for a tab stop.  Supporting tabs
> is not difficult.  All you have to do is pad spaces until you reach a
> number of spaces that is evenly divisible by the number of columns in a
> tab stop (Which should default to 8, unless otherwise configured by a
> user).
>
> "Backspaces, VT100 control codes etc. are all
> things that have no room in modern clients because they are yesterday's
> tech and have no room in users actually use modern clients."
>
> I'm sorry, but you can't be serious.  MUDs are built on ancient
> technology *by definition*.  And this is supposed to be a MUD client.
> They use TELNET as their primary protocol.  For you to say you don't
> want to support TABs because it's "yesterday's tech" given the context
> makes me LOL a little bit.
>
> There are likely tons of MUDs out there using tabs.  Web browsers
> support it, CSS supports it, ever other MUD client supports it... I just
> don't understand the push back for supporting it.  Especially since it
> would be quite simple to properly support.  And I don't mean just
> replace tabs with N characters.  Replace it with the appropriate number
> of characters so that it evenly pads out to whatever the tab stop is as
> defined by the user.
>

-- 
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