cinsert() doesn't respect inserted new lines

Bug #1214836 reported by Vadim Peretokin
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mudlet
Invalid
High
Vadim Peretokin

Bug Description

See test script:

echo("\nTEST PART1: C-API echo & insert functions: <blue>STARTING<light_blue> test#1<green>...\n")
echo("<red>red text<blue>blue text<green>and some green text\n")
moveCursor(10,getLineCount()-1)
insertText("***INSERTING***<orange>orange<pink>pink<purple>purple\ncontinuing on next line#1<green>test 2\ncontinuing on next line#2<blue>test3")

cecho("\nTEST PART2: mudlet-lua cecho & cinsert:<blue>STARTING<light_blue> test#1<green>...\n")
cecho("<red>red text<blue>blue text<green>and some green text\n")
moveCursor(10,getLineCount()-1)
cinsertText("***INSERTING***<orange>orange<pink>pink<purple>purple\ncontinuing on next line#1<green>test 2\ncontinuing on next line#2<blue>test3")

echo("\nRESULT: cinsert() doesn't respect inserted new lines\n")

description: updated
Changed in mudlet:
status: Confirmed → In Progress
Revision history for this message
Vadim Peretokin (vperetokin) wrote :

The issue seems to be that it was used in a non-trigger context. insertText() on its own doesn't handle it very well, inserting boxes instead of newlines when used as such.

When used within a trigger context, both insertText and cinertText behave the same, with the exception of cinsertText() adding its value. See screenshot.

summary: - line breaks in cecho() show but the line order is reversed
+ cinsert() doesn't respect inserted new lines
Changed in mudlet:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.