Move sequences are automatically highlighted and made clickable. If the previous move number appears earlier in the comment, the sequence continues from that move. Otherwise, it's treated as a variation from the main line. This can be error-prone with multiple sequences in one comment, so please use the Preview button to check your work before posting.
To force a sequence to be treated as a main line variation, precede it with a vertical bar
(|). The copy variation button (⧉) includes this bar automatically.
For more complex discussions, you can name a sequence by adding the name in square
brackets at the end, e.g. 15.p9 [a]. Later in the same comment, or in
any following comment, you can branch off that variation by wrapping the name in vertical
bars, like this:|a| 16.o13
The variation name must start with
a letter, contain only letters, numbers, and dashes (-), and is case-sensitive.
Comments use UTF-8 encoding, so you can include emojis 😉, non-English characters, and other Unicode symbols.
You can also use HTML entities like — for an em-dash (—) or → for a right arrow (→).
For safety reasons, most HTML tags are stripped, except:
<b>, <i>, <u> — bold, italic, underline<em>, <strong> — emphasis, strong text<s>, <strike> — <sup>, <sub> — superscript, subscript<blockquote> — indented quotes
<code> — fixed-width font<pre> — multi-line preformatted text
<br> — forces a line break
David, you are constantly making an issue of the use of the vertical bar. I have tried to understand the difference, but can not get a handle on it. For example, I copied your text as written, but deleted the vertical bar. I can click on either message, and I see no difference.
Perhaps you can create an illustrative example in this thread?
(meow)
If there is no vertical bar, it looks for step N-1 in previous text within the scope of the comment, and if it finds it, it branches from that, so that you can have intervening explanations within a branch you're exploring.
OK Alan, thanks for the words. Since you wrote the software, you naturally understand it. Your post has not cleared it up for me at all. It seems that my experiment above, where the vertical bar made absolutely no difference, was limited because I was only looking at one simple line in the post. I think that you mean that, within a post with multiple and alternate lines of analysis, the bar brings each line to the same starting point? And if no bar?
Well, that means I must try a more detailed experiment, so here goes:
(there should be no expectation for the quality of lines I make up)
The bot tells me |26. i12 would have won. For example 27. g13 28. f13 29. e14 30. e11
However, after |26. h11 27. f12 28. e12 29. g10 30. g13 black is lost.
But in case of |26. i12 white can try 27. g13 28. f13 29. e14 30. g11 31. d12 32. e10 33. d10 31. c11 32. b11 and white wins this time!
Now to repeat those comments with extra bars starting each follow up line:
The bot tells me |26. i12 would have won. For example |27.g13 28. f13 29. e14 30. e11
However, after |26. h11 |27. f12 28. e12 29. g10 30. g13 black is lost.
But in case of |26. i12 white can try |27. g13 28. f13 29. e14 30. g11 31. d12 32. e10 33. d10 34. c11 35. b11 and white wins this time!
Now with all vertical bars removed:
The bot tells me 26. i12 would have won. For example 27.g13 28. f13 29. e14 30. e11
However, after 26. h11 27. f12 28. e12 29. g10 30. g13 black is lost.
But in case of 26. i12 white can try 27. g13 28. f13 29. e14 30. g11 31. d12 32. e10 33. d10 34. c11 35. b11 and white wins this time!
And a weird one - one vertical bar at the very start, and only one more vertical bar placed in the middle of the last comment.
The bot tells me |26. i12 would have won. For example 27.g13 28. f13 29. e14 30. e11
However, after 26. h11 27. f12 28. e12 29. g10 30. g13 black is lost.
But in case of 26. i12 white can try |27. g13 28. f13 29. e14 30. g11 31. d12 32. e10 33. d10 34. c11 35. b11 and white wins this time!
This is getting tiring. Hopefully these various setups will show some differences that illuminate the situation. I won't know until I post this comment and try it out! (meow)
OK so far?
But what I am failing to see is a PROBLEM with leaving out all vertical bars entirely. It would appear that my 3rd example, with no vertical bars, simply and correctly shows different comments and different lines in the game, all using the starting position from the actual game. This seems perfectly fine to me.
So are we talking about a case where a comment is made - say moves 26 - 34 are DIFFERENT than what was played in the game, but the same poster wants to branch off - say, keep his commented moves 26 - 30, but then at move 31 we branch. Oh, but here I am still unclear, since a vertical bar at move 31 would IGNORE our commented line moves 26 - 30, so one STILL would want to leave OFF the bar?!
OK, my head is spinning. If you'd care to enlighten me further, Alan, it would be appreciated (and perhaps of use to other readers - don't know for sure; maybe I'm the only numbskull here). Maybe you can make up a few concrete examples, as I did here, to illustrate.
mc
The vertical bar means this is the first move of a variation from the game. If you add the bar to the middle of a variation, when you click on the moves you get the wrong position. Usually just one vertical bar at the first move of your comment is all you need, unless of course you want to discuss more than one variation from the game. If you click the Preview button and then click on the last move of each variation you produce, you can verify that you are creating the variations correctly before you click the Comment button.
is already making more sense to me NOW that I've done all this work, but this is what started me out on all this.
mc
If you wish to continue analyzing from move 26 WITHOUT paying attention to your proposed moves 24 & 25, then the vertical bar WIPES THESE OUT. Of course, you could have wiped them out by hand, either by deleting them or by going into the original game text and clicking on move 26.
On the other hand, if you want to include your proposed moves 24 & 25 and continue your analysis of a proposed line from move 26, then OMIT the vertical bar. Your moves 24 & 25 will still be there, and you may now step forward from move 26. This doesn't seem so bad to me. I guess there might be a possibility that Commentator will get confused by the new moves 24 & 25 as you step forward and a conflicted position may arise. Actually, I'm not sure if this is a real risk.
It DID HAPPEN back when David and Steven were analyzing a game 2442066 . Steven OVERUSED the vertical bar, and created a comment that Commentator could not step through. That was Steven's 2nd comment in that thread. He should have NOT put a vertical bar there.
All this seems to show that the use of the vertical bar is PRACTICALLY UNNECESSARY. Personally, I am not a fan; have to hunt for the key every time, and it slows me down. I believe that I have NEVER used it in any of my various comments in all these years, and there was never a problem caused by that.
I'll leave as an open question then - are their cases where using the vertical bar is absolutely necessary, as you will get messed up without it? I can't seem to create such an example. (meow)
You could avoid a vertical bar in this case if you mention the later variations first and talk about earlier variations later in the same post. This is also a good policy when talking about sub-variations of the same variation, to avoid listing the same moves twice.
The vertical bar is probably not strictly necessary if you are careful, but if you don't use it then if you click on the moves in one post and then click on moves in another post, or like Alan says if you make your own moves on the board and then click on a post, you could wind up with the wrong position. I find the bar useful just as a bit of extra security and way of organizing my thoughts.
Does this make sense to you?
Oh, how does the mouse help you with a vertical bar? You still need to hunt for it on your keyboard - mine is on the right, underneath the backspace, and requires shift. Not all that difficult, but still a task for a lazy typist. McX