While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations:
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Discord is about to require age verification for everyone
- JSAUX announce a charging-friendly Steam Deck travel case
- System76 plans for COSMIC include Vulkan, HDR, gaming improvements and more
- Steam Beta fixes games from large libraries on Linux / SteamOS showing as not valid on current platform
- Hollow Knight gets a patch adding 21:9 & 16:10 resolution support and more
- > See more over 30 days here
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
A small bit of JavaScript will quickly check over the text, to see if there's enough matching opening and closing quote tags:
[quote] [/quote]As I've noticed a few users quote, then go to edit it (possibly to cut something out?) and then screw up the BBCode resulting in semi-broken looking posts. It will just flag up a quick warning that the formatting is messed up.
Example:
Last edited by Liam Dawe on 11 Feb 2026 at 11:43 am UTC
Absent a WYSIWYG post editor that takes care of keeping the quotes tags balanced at all times, one solution for posts like your example might be auto fixing. If there are quote tags in the post, but one is unclosed, just insert another close immediately after the existing one. I bet in 95% of cases, that's where it belonged anyway.
Last edited by FeRDNYC on 12 Feb 2026 at 4:48 pm UTC