[GH-ISSUE #2] Please allow to display line breaks #3

Open
opened 2026-10-15 13:26:23 +00:00 by bsakaguchi · 7 comments
Owner

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.

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.
Author
Owner

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

<!-- gh-comment-id:2561879423 --> @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.
Author
Owner

@Jijiza34 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.

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

<!-- gh-comment-id:2562000126 --> @Jijiza34 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. 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".
Author
Owner

@cloak1505 commented on GitHub (Oct 31, 2025):

@Jijiza34 Someone made a fork with a toggle that does this: https://github.com/Giglio256/PromptInspector-VisibleLineBreaks

<!-- gh-comment-id:3471114315 --> @cloak1505 commented on GitHub (Oct 31, 2025): @Jijiza34 Someone made a fork with a toggle that does this: https://github.com/Giglio256/PromptInspector-VisibleLineBreaks
Author
Owner

@Giglio256 commented on GitHub (Nov 1, 2025):

@Jijiza34 Someone made a fork with a toggle that does this: https://github.com/Giglio256/PromptInspector-VisibleLineBreaks
That someone is me from my new account. I am Jijiza34. ChatGPT5 made it possible.

<!-- gh-comment-id:3476646639 --> @Giglio256 commented on GitHub (Nov 1, 2025): > [@Jijiza34](https://github.com/Jijiza34) Someone made a fork with a toggle that does this: https://github.com/Giglio256/PromptInspector-VisibleLineBreaks That someone is me from my new account. I am Jijiza34. ChatGPT5 made it possible.
Author
Owner

@cloak1505 commented on GitHub (Jan 9, 2026):

SillyTavern devs actually listening to people and not being stuck-up challenge (IMPOSSIBLE)

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

<!-- gh-comment-id:3727566162 --> @cloak1505 commented on GitHub (Jan 9, 2026): > SillyTavern devs actually listening to people and not being stuck-up challenge (IMPOSSIBLE) 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".
Author
Owner

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

<!-- gh-comment-id:3728048241 --> @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.
Author
Owner

@Cohee1207 commented on GitHub (Jan 10, 2026):

Open Source Maintainers Owe You Nothing

<!-- gh-comment-id:3733300750 --> @Cohee1207 commented on GitHub (Jan 10, 2026): [Open Source Maintainers Owe You Nothing](https://mikemcquaid.com/open-source-maintainers-owe-you-nothing/)
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
SillyTavern/Extension-PromptInspector#3
No description provided.