On Tuesday, February 18, 2020 at 2:11:21 PM UTC-5, andyjim wrote: > > > > On Monday, February 17, 2020 at 8:08:30 PM UTC-5, Thomas Passin wrote: >> >> Sure, I understand. And I wasn't thinking about delineating the >> different pieces by date so much as automatically extracting them. Sounds >> like that won't work. >> >> However, having the dates in the zettels would have the advantage that >> they can be searched for in Leo without us having to write any new code. >> > > I am wondering: Early in this thread someone said you can, in Leo, easily > break out selected sections from a file, into a new node I believe. Maybe > that's what I should do. I have to work through these files anyway to > 'create' zettels, so why not simply do that in Leo, then format the > zettels, in Leo. No need for a parser at all? >
I'm not sure what that someone was thinking, but here's one way I've done that. Import your file, which will normally put into a single node. That node wouldn't have to be in your zettel collection. Then for each zettel, section, or what have you, you can select and copy that text to a new node, maybe a child of the entire imported node. Finally, you can copy those new nodes wherever you like. If you don't have any consistent markers within the big file to indicate sections, that's about all you can do. At least, it avoids needing to create a lot of new files and importing them. You said you have some files that contain a years worth of notes. They would be pretty large to move through in a Leo node. So an alternative would be to open the big file in a word processor or editor, select and copy text sections, create a new node for each, and paste the copied text into a Leo node. That would be almost as easy (or easier for a large file), and still avoid creating any extra files that would then have to be imported. If you want to include data such as the timestamp of any section, you can just add it into the new Leo node's text. But it would be best if you use a consistent syntax (format) for that kind of added data. Then would could write some code to pull it out and process it later. I'd suggest using my format 4, which I posted earlier. That's the format looking like this: :date: 2020/2/5 :time: 1830 Or combine both into a timestamp, denoted by :timestamp:. It doesn't matter much as long as it's consistent (and be consistent in how you write the timestamp). If it's consistent, we can always parse it out later. If it's inconsistent, we won't be able to search for or process it without manual help. > It appears you are casting your net beyond Leo a bit too, in case there is > something out there that does almost all of what we want. Brain? > MindForge? Let me know what you find. I was unable to install MindForge on > my Mac even though there are instructions to build it. Didn't work. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/97c2d871-f4ae-4212-b1d5-41b1d7acb643%40googlegroups.com.
