Blank spaces in an echo before text in trigger context are stripped
Bug #1225591 reported by
Vadim Peretokin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mudlet |
Fix Released
|
Medium
|
Chris |
Bug Description
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 modification - it breaks a lot of alignment in echoes.
This is on current in git only and not 2.1.
Changed in mudlet: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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 15.09.2013 07:54, schrieb Vadim Peretokin:
> 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 modification - it breaks a lot of alignment in echoes.
>
> This is on current in git only and not 2.1.
>
> ** Affects: mudlet
> Importance: Medium
> Status: Confirmed
>