Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

plaintext-node contains <rich_text> ... </rich_text> (xml saved in directory structure) #2573

Open
klartext opened this issue Sep 26, 2024 · 2 comments

Comments

@klartext
Copy link

cherrytree 1.1.4
Arch-Linux

Describe the bug
A plaintext node has the text wrapped into <rich_text> and </rich_text>

To Reproduce

  1. Create a plain text node, save the Tree as multiple files in hierarchical folder structure.

  2. Then look what's in the file.

Note
So far this has caused no problems in working with the file.
Nevertheless this looks like an inconsitency, which may cause problems in certain situations.

@giuspen
Copy link
Owner

giuspen commented Sep 28, 2024

That's right, currently even the plain text is inside a rich text capable slot, just without any tag applied.
So it is as expected.
I can consider removing the wrap before saving to file if that would be useful to cross edit with another text editor but that has to be done only while cherrytree is not running as monitoring the file for changes is not currently something cherrytree does in the multifile (it can do so if enabled in the preferences dialog for the single file document type).

@klartext
Copy link
Author

Removing the XML-wrapping completely (not just replacing the rich_text tag with a plain_text tag or similar things), would be great.
If it's just a plain text file (assuming utf-8 here) that is used for plain text documents, that would allow painless editing of the files - without the fear of messing things up

And as you assumed correctly, I think about editing files directly with my favourite editor.
If cherrytree would allow starting the favourite text editor, that would be nice, but if it does not, it's also ok.
For versioning I use just git on the directory that contains the info-trees.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants