A few days ago you lost a sizeable chunk of rep due to a user being removed. See May 25th. When you lose reputation, due to downvotes or vote reversals of any sort, we don't show you reputation increases again until your reputation earnings have exceeded your reputation loss. This is because we show your net reputation change and we do not show negative ...
This has to do with the age of the post and is in fact happening by design. When it was created in December 2018, Stack Exchange didn't support ``` code fences. It did, however, support ``` as a way of entering inline code with like breaks. That's what the answer in question was doing, purely by accident.
In January 2019, we added support for code blocks ...
At the beginning of a period--whether it be a week, month, or quarter--the stats for that period go back to zero, because they applied to the previous period, which has just ended. This is probably the only reasonable way those stats could be displayed, but I've found it confusing as well, because when one week, month, or quarter is considered to end is sort ...
That is not a bug, it is by design.
What is happening is you are posting a very short answer with a link and the system is picking that up automatically as a low quality / link only answer.
When you post a link answer you MUST include the relevant content from the link in the answer and leave the link as a reference.
To be fair to you, I had no idea this ...
I usually double-up the indent for each level of bullet point you're under. So here that's an indent of 8 spaces. And it previews correctly.
1. Update your `/etc/default/grub` accordingly:
Update your /etc/default/grub accordingly:...
I solved it by indenting the code block by four spaces, which subordinates it under the ordered list:
1. update your `/etc/default/grub` accordingly:
The issue of the Preview showing something different than the post in the end of ...
If you find a bug in the Ask Ubuntu / StackExchange platform, you open a meta post here on https://meta.askubuntu.com and detail the specific issue you're seeing and use the 'bug' tag. This will draw attention to the issue for SE developers and staff to look at.
HOWEVER as it currently stands, you have not detailed the issue you're experiencing and don't ...