mirror of
https://github.com/SillyTavern/Extension-PromptInspector.git
synced 2026-10-15 13:31:52 +00:00
[GH-ISSUE #2] Please allow to display line breaks #3
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
SillyTavern/Extension-PromptInspector#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Jijiza34 on GitHub (Dec 25, 2024).
Original GitHub issue: https://github.com/SillyTavern/Extension-PromptInspector/issues/2
The prompt inspector displays line breaks from world info as \n. This makes the text very hard to read.
Please show me the line breaks.
@Cohee1207 commented on GitHub (Dec 25, 2024):
Works as intended. Chat Completion prompt is displayed as a JSON-serialized array of objects according to the API specs, so both input and output text should be a valid JSON string.
@Jijiza34 commented on GitHub (Dec 25, 2024):
I understand that, but it doesn't change the fact that it is very hard to read. All I'm asking is an option to please display it in a more readable way, displaying line breaks as line breaks and not as "\n".
@cloak1505 commented on GitHub (Oct 31, 2025):
@Jijiza34 Someone made a fork with a toggle that does this: https://github.com/Giglio256/PromptInspector-VisibleLineBreaks
@Giglio256 commented on GitHub (Nov 1, 2025):
@cloak1505 commented on GitHub (Jan 9, 2026):
YAML display mode was implemented in response to this issue, which is sufficient for "displaying newlines". Each line is indented (because YAML), though, which would interfere with plaintext copy&paste purposes, what others might need.
Edit: Also the edge case problem where the fork is broken by literal \n in chat message makes "invalid format" deemed "too unstandard for an official extension".
@Cohee1207 commented on GitHub (Jan 9, 2026):
..And not producing invalid and syntactically incorrect JSON because "JSON with line breaks" is not a valid format.
@Cohee1207 commented on GitHub (Jan 10, 2026):
Open Source Maintainers Owe You Nothing