mleku on Nostr: i don't want it to be part of the document because it's implicit i was just talking ...
i don't want it to be part of the document because it's implicit
i was just talking the other day to someone about how it's a bit weird the way that interfaces in #golang are implicitly satisfied... there is some other features of the language that work the same way, and avoid complexity... like, Go actually uses semicolon statement separators, but they are implied by newlines except after a small set of specific operators, comma, infix operators, so you don't have to remember them, one of the most annoying things about C/C++/etc
the document has headers, the headers are structure, the parser can scan the headers and voila, table of contents.
in actual fact, also, you probably didn't know this but in the top right of the document viewer, also even if markdown, github has a menu of the - same thing - as the TOC
i have also been using an interesting asciidoc plugin for intellij that is based on ascidoctor and JCEF... it has a top bar that stacks up your current header level and the next levels up from it directly (sorta like a series of back buttons with further context)
the editor doesn't sync the position between the two but it does jump the editor if you click on a header to the header you clicked on the preview
just the fact that it can automatically have a proper ToC is big for me, because a document that is more than a few screenfuls without an index is really troublesome to navigate, and hyperlinking can introduce other problems, though it does make side-by-side stuff easier, that is more important for editing than viewing anyway
i was just talking the other day to someone about how it's a bit weird the way that interfaces in #golang are implicitly satisfied... there is some other features of the language that work the same way, and avoid complexity... like, Go actually uses semicolon statement separators, but they are implied by newlines except after a small set of specific operators, comma, infix operators, so you don't have to remember them, one of the most annoying things about C/C++/etc
the document has headers, the headers are structure, the parser can scan the headers and voila, table of contents.
in actual fact, also, you probably didn't know this but in the top right of the document viewer, also even if markdown, github has a menu of the - same thing - as the TOC
i have also been using an interesting asciidoc plugin for intellij that is based on ascidoctor and JCEF... it has a top bar that stacks up your current header level and the next levels up from it directly (sorta like a series of back buttons with further context)
the editor doesn't sync the position between the two but it does jump the editor if you click on a header to the header you clicked on the preview
just the fact that it can automatically have a proper ToC is big for me, because a document that is more than a few screenfuls without an index is really troublesome to navigate, and hyperlinking can introduce other problems, though it does make side-by-side stuff easier, that is more important for editing than viewing anyway