Argh. A thing I hate about rich text editors is when you apply markup to a region, and you then want to insert a character right after the marked-up region (like a comma after a link) but it decides it decides to attach the markup to that too and you're stuck trying to kind of shake it off like mud from your boots.

@cwebber You know, clear back in the Word Perfect days of MS/DOS and early Windows, there was a concept of "show codes" (or something like it) and it essentially let you edit in a view that let you see all the markup (or whatever they called it). It made it super simple to correct mistakes like that or other formatting errors. It was very convenient, and I've never understood why I haven't seen it in any other WYSIWYG type editors.

@cstanhope @cwebber Most rich text editors should have a command for clear or remove formatting on a menu somewhere and/or a shortcut key, that you can use in that situation to get back to unformatted text.

When I use an editor like that (rarely), I usually start off with some extra carriage returns at the end to avoid that.

@leadore @cwebber Yep. Extra carriage returns are mandatory. So bizarre the workarounds we create to use these "intuitive, easy to use tools".

@cstanhope @cwebber IIRC the early HTML editors if ~20 years ago had this feature

@veer66 Yeah, staring at raw XML is pretty rough. The Word Perfect view didn't expose the structure at that level. It was a little more abstracted, and you could quickly navigate between elements which were represented as single navigable objects.

@cstanhope @cwebber a friend was a legal secretary in the days of Word Perfect's demise and said she would never use anything else because the ability to fix the underlying markup was critical for accurate legal documents

@cwebber ugh and sometimes they have heuristics or other weird rules to glob stuff into the markup

glad the last big document I was lead on we could do in LaTeX

Sign in to participate in the conversation

Octodon is a nice general purpose instance. more