Create a plain text internal link inside a table
I am trying to create a plain text internal link inside the table to the already existing thought "Sacramental Atlas - 1888"

We see that the auto detect thought finds a match for "Sacramento Atlas". Showing the dotted line under the text. When we place the cursor in the table cell we see the pop-up menu with the found thought highlighted. "Sacramental Atlas".

Next we type the hyphen and YEAR. ( - 1888 ) And the auto detect finds that also as an already existing thought.

Good so far!
Now we want to link to that existing thought. This is where everything fails.
- We click on the Pop-up dialogue menu and select Link "Sacramento Atlas - 1888".

And what happened? Nothing! The cursor jumped off somewhere, who knows where? And we have no visible link!
Next

- We try it again (Because these things seems to require doing it more than once in v.15)
- Before theBrain takes us serious, that we really would like to link to the full highlighted existing thought, .this happens instead, And for some reason it decides to only create the link for partial of the name and year.

Please see video: Thought link is wacko
Also,
- When trying to link the thoughts in a column to the "Selection list pane", the commnad to "Add to Selection List" does not work while the thoughts are in cells of the table column. The thoughts must be copied out of the table and pasted as a stand alone list outside the table and only then can they be selected for the selection list.
- And also, now I have found a workaround for getting a hyperlink within a table cell. After creating the intended plain text outside the table, I can create a internal link to the plain text and after creating the title link, I can now paste that text with the link into the table cell. It's definitely a regression from v. 14 but it works until you get this fixed.

- While using v.14 we could select the thought inside a table cell and hold Ctrl and it would be added to the Selection panel. In v. 15 that no longer works. This is a huge recession of an existing feature now it is just ridiculous that amount of time wasted. Unless you have a better solution that I am not aware.