Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the "town hall" (meta-discussion site) for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on "Show source" feature would make sense to me

Parent

"Show source" feature would make sense to me

+2
−0

I dimly remember that once, on Wikipedia, there was a button "Show source".

Would be nice to have that here, to learn about what is possible from examples, without opening things for edit and then accidentally modify it.

Would be of special interest for comments, looks like they don't have (and need) all functionality available for questions and answers.

Should be easy to implement using the code already available for "edit" but just blocking "save" and enable "show" for any user, even those without permission to "edit".

History

1 comment thread

Can't you do that thru your browser? (3 comments)
Post
+3
−0

The solution in RokeJulianLockhart's answer is useful in some specific cases, but is not a general solution so I would still like to see the feature request implemented. There are a few problems here:

  1. As mentioned in a comment under the answer, MathJax (for those communities that have it enabled) shows in rendered form rather than as the raw text. I regard this as a bug with the edit history. This was raised previously on GitHub.
  2. For the first entry in the edit history (the original wording of the post) the raw text is shown, as desired. For any later entry the diff is shown (the before and after text, with indications of what was added and/or removed). This gives no way to see just the raw text.
  3. As shown by the same comment thread, it is not intuitively obvious that this edit history method is possible to someone viewing a post.

Ideally I'd like the see the raw text available from the edit history for any edit (to address 1 and 2) but also available from the post directly (to address 3).

History

1 comment thread

This bug may be tracked. (2 comments)
This bug may be tracked.
Mr. Beedell, Roke Julian Lockhart (RJLB)‭ wrote 4 months ago · edited 4 months ago

MathJax (for those communities that have it enabled) shows in rendered form rather than as the raw text.

trichoplax‭, what Monica Cellio‭ cites at comments/thread/11199#comment-27735 may be relevant. Specifically, github.com/codidact/qpixel/issues/1116, which requests MathJax source.

trichoplax‭ wrote 4 months ago

Thanks for reminding me about that. I've now linked to it from point 1, since it would solve that point completely.