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 »
Users Search
Help Dashboard Sign In Sign Up
Q&A Papers Meta
Meta
Posts Tags Edits
Create Post

Comments on Viewing the potential live output when editing a question or answer.

Parent

Viewing the potential live output when editing a question or answer.

+2
−0

I have just raised a Q and A but when editing the answer (that involves a picture) there is no "live" version of the potentially finished post and this will prove to be a problem when making a complex answer especially if MathJax/Latex is used. SE.EE does support this feature and I think it's vital.

Also, there is no facility to renumber the bullet points. If you look in my answer, there are two bullet points names "1".

This is what I see when editing an answer: -

__ Well I tried to embed an image by pressing the picture button but I got javascript:void() in the bottom left corner. Yet I know java is enabled because I've just used a web page that uses it and I should know because it's one of my own web pages __

bug proposal pictures list-items
posted over 4 years ago
4y ago
user card
Andy aka‭
2299 reputation 19 75 266 282
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (3 comments)
Post
+1
−0

I recommend using native HTML for lists, and most other formatting for that matter. HTML gets around the ambiguity of what is an item and what is text following the list. The list isn't over until the </ol> tag.

For more information about formatting, see the Formatting Posts document in the site help. This is at https://electrical.codidact.com/help/formatting.

posted over 4 years ago
user card
Olin Lathrop‭
7964 reputation 18 328 951 466
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (2 comments)
General comments
manassehkatz‭ wrote over 4 years ago
copy link

Personal preference. I happen to think using markdown for everything is better - I actually wish markdown was ever so slightly more complete so that no html would be needed. I mean, 4 characters for bold (asterisk asterisk start and finish) and super easy to type compared to a minimum of 7 characters using HTML. Similar for lists - e.g., unordered lists just an asterisk and a space on each line instead of a ul tag to start/finish and li tag on each line. Doesn't get batter than that.

Olin Lathrop‭ wrote over 4 years ago · edited over 4 years ago
copy link

@manass: Markdown is simpler, but that simplicity comes at the cost of ambiguity and too many unintended markups. I also don't want to have to remember two syntaxes. Use markup if you like, but please make sure all the same formatting features continue to be available via some subset of HTML. Actually, it would be nice to be able to force markup off so that it doesn't "helpfully" decide to format when I use an asterisk, a few dashes, or whatever, for other reasons.