You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you add an url with '/#', the preview shows the string that follows the # as a tag.
Moreover, the href in <a> tags contains <span> tags that should not be there.
Example of one of the links after being processed by t2t: <a href="http://www.mywebsite.org/<span style="color:red">#foo</span>/bar">http://www.mywebsite.org/<span style="color:red">#foo</span>/bar</a>
Visual:
When I disable the hashtag recognition in util/markup.py, the bug goes away, except that the full url is still not recognized as such correctly:
Trying to fix this problem by adding a '/' in the right regex in external/txt2tags.py makes the whole (from beginning to end) url to be marked as such, as it should be, but the hashtag is still recognized as a hashtag and the problem regarding spans in hrefs is still there.
Versions:
RedNotebook version :
Operating system and version: 2.29.6 (current master)
Os: debian 11
The text was updated successfully, but these errors were encountered:
Describe the bug
When you add an url with '/#', the preview shows the string that follows the # as a tag.
Moreover, the href in
<a>
tags contains<span>
tags that should not be there.Example of one of the links after being processed by t2t:
<a href="http://www.mywebsite.org/<span style="color:red">#foo</span>/bar">http://www.mywebsite.org/<span style="color:red">#foo</span>/bar</a>
Visual:
When I disable the hashtag recognition in util/markup.py, the bug goes away, except that the full url is still not recognized as such correctly:
Trying to fix this problem by adding a '/' in the right regex in external/txt2tags.py makes the whole (from beginning to end) url to be marked as such, as it should be, but the hashtag is still recognized as a hashtag and the problem regarding spans in hrefs is still there.
Versions:
The text was updated successfully, but these errors were encountered: