Then the behaviour is undesirable as it breaks echoes and causes more
trouble than it is worth, unfortunately. This side-effect is not good.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1225591
Tit
There's only one type of wrapping in Mudlet and this applies to
everything.
Am 15.09.2013 12:38, schrieb Vadim Peretokin:
> Are you sure this didn't relate to Mudlets word wrapping of the MUDs
> text?
>
> I think that is what was the intention - when there is a long line and text
> is wrapped, spa
Are you sure this didn't relate to Mudlets word wrapping of the MUDs
text?
I think that is what was the intention - when there is a long line and text
is wrapped, spaces before it should be deleted. But it should not affect
any of the scripting API. I remember now the issue was with help indexes -
I think there is a misunderstanding. I'll investigate this.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1225591
Title:
Blank spaces in an echo before text in trigger context are stripped
Status
The reason is that people wanted Mudlet to skip leading spaces when
lines are being wrapped -> some Achaea help text was unaligned and
people claimed that all other clients wrap without leading spaces.
As echo(" 1\n 2\n") wraps the line after the first \n, this is the
direct consequence.
Am
Public bug reported:
Steps to reproduce:
make a new trigger
put echo("\n hi\n hi") into it
output will be:
You see exits leading northeast, east (open door), west (open door), northwest,
up, and down.
hi
hi
Blank spaces before text in the echo are being stripped, and this is an
undesirable
6 matches
Mail list logo
