On Monday, March 2, 2020 at 12:10:38 PM UTC-5, andyjim wrote: > > On Monday, March 2, 2020 at 10:07:00 AM UTC-5, Thomas Passin wrote: >> >> >> The line of "=" characters marks a section break, the text in brackets >> becomes the title, and the date speaks for itself. The number of "=" >> characters in a line doesn't matter as long as 1) the line starts with an >> "=" and 2) there are at least some minimum number of them. >> >> As I see it, when you want to convert one of your text files to >> zettel-hood, you would go through the file and add these section breaks as >> you go. Then paste the entire thing into a Leo node (or import the file >> into a node), hit a hot key, and the system would split out all your >> zettels, in order, with the titles as the headlines. They'd all be at the >> same level of indentation. After that, you could move them into the ZK, >> add organizing zettels, link them, add citations, etc to your heart's >> delight. >> >> Does that sound like it would work for you? >> > > Yes it does. > So prepping a file consists of adding the separators, [title in brackets] > on first line, a space and then the 'created' date (where I see you used > the same YYYY-MM-DD format that is my preference. > Will the system then zettel-ize it with a UID? And where will it place the > title (within the zettel that is)? >
The easiest thing to do (and the way I have been visualizing it) is to use the [title] for the headline of the zettel node. You'd want to keep it short and (if possible) informative, but you should do that anyway. The date could be separated by any amount of whitespace, as long as it's on the same line. A date could even be optional. The node identifier would be the node's gnx, as my zettel-insert-node (CTRL+F8) command already does. There's no need to have another uid. It would be possible to build a new command that captures a node's gnx to the clipboard so you can paste it where ever you want, but I don't know that would worth binding to a hot key. BTW, about these "commands" I keep mentioning. Each of them consists of code bound to a name. If you have used the emacs editor you will recognize how to use them. You hit Alt-X, or click in the "minibuffer" line at the screen bottom, then type in the name of the command. It does completion, so type, for example, "ze" then hit TAB, and a panel will show you all the commands that start with "ze". Type enough more characters then hit tab again to complete one of them. Then <ENTER> executes the command. That's how you can use commands that are not bound to keys. If you go to my zettel2.leo example file, and try the above, you'll see the following commands: zettel-goto-node zettel-insert-node zettel-insert-time Those are the commands in the @command nodes. > And can the 'created' date be automated? Well, that would be nice, but > since I need to type in the created date anyway I might as well make a > :created: YYYY-MM-DD line. > And if the system extracts the title for the heading, perhaps I need to > copy the title into the 'body', below. Or it could even differ from the > heading if there is any reason to do that. Can you have multiple identical > headings in an outline? Actually, yes, I've already discovered that you can. > > So this gives a way to set the heading from within the zettel, removing a > step from the process. A bit less overhead, at least when I bring a zettel > in that way. > > In the example you posted, "Salmon with Whole Lemon Dressing" is the > heading, and also the title in the rendered pane. But in the body pane, > what follows the id is "Salmon Lemon Dressing", so the rendered title is > the same as the heading, but not the same as what is in the body pane. > -- 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/87b38c4d-6290-4da0-8490-ee8d56264557%40googlegroups.com.
