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
Discovered as part of #13 - which allows you to introduce this state entirely within BT - although I think anyone who edits the org file externally will encounter this issue.
If you create a complex heading that has a link and text, it renders fine in the tree:
However, editing the entry will break the structure:
Proposed Solutions
Accept as-is - the title will always be a full link - maybe add a warning that saving will change the heading irrevocably
Make the heading read-only if it's not in standard BT format - in which case, you can still edit the description field without affecting the heading
Add a toggle button which allows for editing in org syntax or plain-text syntax, which the caveat that plain-text will wipe out custom syntax (and would then default to org editing if this scenario is encountered)
The text was updated successfully, but these errors were encountered:
I like the third option. The note field is already, by default, plain text but at some point I'd like to support a more naive user friendly markup editor. So being able to switch back and forth makes sense.
BT Version: 0.9.6 / Chrome
Problem
Discovered as part of #13 - which allows you to introduce this state entirely within BT - although I think anyone who edits the org file externally will encounter this issue.
If you create a complex heading that has a link and text, it renders fine in the tree:
However, editing the entry will break the structure:
Proposed Solutions
The text was updated successfully, but these errors were encountered: