5

This is a continuation of my question Recent change in treatment of backticks in comments?, but as that one is , I think it better to ask a new question.

As explained here by Jeff, backslash escaping within inline code in comments is now disabled except for the backtick. While this is great, the problem is that all the old comments are affected, too. Over at tex.sx, we got used to having to write `\\(` in a comment to get \(. The result of the recent change is that now there are many instances of \\( in old comments where it should be \(. (I had already expressed the opinion that it would be bad to make changes to old comments; I'd prefer if they're left alone.)

Can this be fixed, please?

Improve this question

1 Answer 1

Reset to default
2

Well I replaced all seven of the comment instances where \\( or \\) occurred on Tex.. not exactly an epidemic, is it?

One example here:

Is there a test for the different styles inside maths mode?

I guess I'll try meta.tex too.

Improve this answer
8
  • @Jeff: Thanks a lot! You're right, seven is a lot less than I expected; I see you found some more on meta.tex. There you see that the same problem is with \\[ and \\]; can you replace those, too (both on tex and meta.tex)? Another thing: Your replacement of the triple backticks didn't work for ```., and it seems that you didn't apply it to meta.tex. In my comments that's about 7 instances; maybe there are more.
    – Hendrik Vogt
    Feb 15, 2011 at 9:16
  • @Jeff: Sorry, one more thing: What has happened to my comment at that same link on meta.tex in which it says "(With the highlighting, I like $ much better than ` (` and ` )`.)" I'm pretty sure I typed `\\(`, and now it looks as if I typed \` (\`. It not so nice that the changes affect old comments; only some are distorted, but I did put some effort into them looking good.
    – Hendrik Vogt
    Feb 15, 2011 at 9:20
  • @hendrik different issue. Spaces are not allowed as the start or end character in inline code blocks now. Do not include them, or it won't work. Your comment had spaces as the start or end character in the code block.
    – Jeff Atwood
    Feb 15, 2011 at 22:46
  • @hendrik I replaced for \\[ and \\] as well. Are we done now?
    – Jeff Atwood
    Feb 15, 2011 at 22:46
  • Thanks, Jeff, I really appreciate your help here: Even that comment with the funny spaces is fixed; great. So with fixing we're done, I think. Here's a test: a space in the end of inline code is OK, as \ shows. Please do not change this! It's our last workaround to type \ . But can you please tell me where I can find the details on how backticks in comments work right now? And when there's another change, wouldn't it be a good idea to leave the old comments unaffected?
    – Hendrik Vogt
    Feb 16, 2011 at 14:39
  • @Jeff: It still seems that all the fixing related to my question above is done, thanks. However, I just saw that there is another issue, namely that the enforcement of backslash escaping of backticks has more negative effects (my comment of Jan 4 at 17:19, currently the 4th from below). My main point is to underline the last question in my previous comment.
    – Hendrik Vogt
    Feb 16, 2011 at 18:32
  • @Jeff, sorry for keeping nagging: Here I observed some quirky behaviour in inline code in comments. If you have <br> then you can also have <br>s without a space. Is this a bug or a feature?
    – Hendrik Vogt
    Feb 17, 2011 at 11:28
  • @Jeff: Whereas, if you have <br /> then you can't have <br>s. Weird! I'd really like to know what exactly is possible and what is not.
    – Hendrik Vogt
    Feb 17, 2011 at 11:29

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .