Bear with my characterizations, I expect to post, reply, reply again, and then edit the second reply, and then probably post a fourth message to summarize.

I noticed that a percent symbol I used as part of a reply was missing. "Oops!" have to escape that, I originally thought with the backslash, but instead I needed to double it by using "percent-percent" and that worked.

Later I re-edited my edit because I corrected something and I reminded myself "double percent's" and (swear word) it put up the double! So I iterated and by that point it seemed to recognize the single use. But ... I did my first edit because it obliterated a single use ....

So as I say. This post will contain a test single percent, and then a double percent.

Reply #1 will just be a simple reply using the same test cases.

Reply #2 will be an advanced editor use reply using the same test cases.

Reply #3 will be a summary.

And I'm sitting here ready to eat crow and just finalize by clicking [SOLVED] if I'm all full of (junk) when the testing is complete.

Single percent %
Double percents %%

---------- Post added 09-02-15 at 10:47 AM ----------

Well both cases worked in my original

Single percent %
Double percents %%

Reply #1 worked also.

Advanced editor.

Single percent %
Double percent %%

Solved! Or I assume either it was some anomaly, or I'm just crazy.

Or the actual syntax of +%u had some impact to the case. That would be PLUS PERCENT LOWERCASE-u

Yup, see Problem displaying % character in posts and within code tags.

Quick reply/edit eats a percent, "advanced" mode does not.

2 members found this post helpful.

i noticed this random phenomena too.

a lot of my solutions using something like date +Y-%j get messed up.

See this thread
The deletion of percent signs happens in the Quick-editor, not in the Advanced-editor.

Sorry, I marked as solved but didn't state any conclusions. I did see the other thread, I think also referenced earlier, and see that the subject was addressed already.

is there any way to solve it?
http://www.linuxquestions.org/questi...7/#post5440794

It's a known issue that will be addressed in a future code upgrade.

--jeremy

Better sooner than later, please Jeremy: this bug could even hurt a poster's reputation (I mean, real reputation).

For instance in this post, becameSo readers maybe thought: either Didier can't write a simple shell script or he didn't take care of trying it before posting.

PS I realize that such a change on a website with a very high load needs thorough testing before being put in production "in the wild". I volunteer to participate to these tests as an end user who can devote some time to such a task.

1 members found this post helpful.

Didier is right to highlight the risks here. Having the percent signs silently ripped from a ${parameter%word} or ${parameter%%word} substitution in a posted shell-script example could potentially do much more harm than just making the poster look like an idiot.

This is somewhat contrived and not a particularly good/safe coding style to start with, but take the following example of a not entirely unreasonable installation routine (minus the echo's which I've thrown in just to be 100% safe):
Stripping those percent signs could be quite catastrophic if the poster or reader didn't catch the omission!

I'm happy to report that a fix to this issue has been rolled out. I appreciate the patience. A big thanks to Stuart Langridge for the pointer that ended up leading to the solution.

--jeremy

2 members found this post helpful.

Thanks!