Finally, wrap everything up in a docker container, to make it easier for people using it - including LaTeX itself.Then I'll expand TeXDown to do all of that scripting / preparing the LaTeX source that I want.Learn much more about Obisidian so that I could make it work similar to what I have with Scrivener - that entails, of course, some tag approach as to what I want to actually include in any given LaTeX run (in Scrivener, you'd just check an "include in compile" checkbox on some node of your tree, and TeXDown will respect that that's going to change as there's not necessarily a metadata file, but I could use a project file that just links in some starter nodes in the tree).Since I'm moving away from Scrivener and am gravitating towards Obsidian, I'm working on three things: I know there's markdown approaches already to it, but they were too limited for me, and I wanted more control - and integration with Scrivener actually, at that point in time. What I've already done is to create a script on top of Scrivener - I called it TeXDown - that takes away most of the LaTeX command you'd otherwise use in your day to day work. The file format is comparatively open - it's just a UI sitting on top of a bunch of rtf notes that are all held together by one big XML containing all the metadata. I've been Scrivener for a while now, and since I'm not only a student myself now, but also take care of some students, I'm mostly annoyed by it being limited to MacOS, paid software, etc. It is just a thought since I am a complete n00b when it comes to Obsidian, but as part of my writing, I've extensive experience with LaTeX, and hence was looking for a way to push the Zettelkasten idea to generate content for my PhD thesis. That's something that I may be able to contribute to. You could have a transcluded note in your home note for instance I have ] for things I'm actively working on, and in that note have links to each of your thesis outline notes so no folders are needed: Keeping all of these thesis outline notes in a folder is likely the approach I would have just for a clear separation of concerns while I'm working on them (organizing these notes would be made easier by prepending incrementing numbers like 1.0, 1.1, 1.1.3, etc to the beginning of the heading for the eventual refactoring).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |