Re: @auto-rst vs. @nosent
On Sat, Feb 14, 2015 at 9:05 PM, karho...@gmail.com wrote: all these commands that you have recently changed need proper documentation, once the dust has settled. Thanks for this reminder. I've just put it on the list. There were also some obscure points I came across while reading the manual some time ago, but I don't remember them specifically. If you do remember, or have other questions, I'll be interested in hearing about anything that is difficult to understand. Edward -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: @auto-rst vs. @nosent
On Sat, Feb 14, 2015 at 12:50 PM, gatesphere gatesph...@gmail.com wrote: @auto-md is useful for the same reasons. And afaik, is completely undocumented. Thanks for this heads up. I'll make sure all flavors of @auto-* are documented for 5.1. For sure, @auto will remain for the foreseeable future. This is turning into a fascinating discussion, as I'll now explain. It may be relatively easy to make @nosent do the work of @auto-rst and the rest (@auto-*) This will involve special cases to the @nosent read and write logic. These special cases should be relatively straightforward. **Terminology**: @ns-* denotes @nosent augmented with special read/write code for rst, md, vimoutline and otl (Emacs outlines). We may not need different flavors to the @nosent directive, but that's another question. = @ns-* write logic In his initial post, Rob said, when I change my @auto-rst files to @nosent files, the resulting files do not contain the RST section headers that were automatically added by @auto-rst. This proves that @ns-rst must have special logic that writes the proper section headers. Happily, this can be done easily with special cases in at.putOpenNodeSentinel. Ditto for @ns-md, @ns-vimoutline and @ns-otl. = @ns-rst read logic No change is actually *required* for @ns-rst and @ns-md. When reading an @ns-rst or @ns-md file, added sections could be slurped into the outline as under/overlining text. The user could leave the changed node as it is. Or the user could create a new node with the indicated headline. Either way, the @ns-rst write logic would recreate the changed file. However, a simple, fast post-pass in the @ns-rst/md read logic could create the new nodes automagically. The post-pass would traverse the tree created by the @nosent logic looking for under/overlined lines (or # lines for md), creating new nodes as needed. The actual code would be similar to the @auto-rst logic,but it exists in a far simpler context than @auto-rst. Post passes are probably *required* for @ns-vimoutline and @ns-otl. Indeed, vimoutline or otl sentinels should *never* be left as plain text in an existing node. The raw sentinels would corrupt the vim or Emacs outline if the node were later moved. An unpleasant time bomb. = Summary @auto-* will remain for the foreseeable future. This post has been discussing new features. I'll investigate adding @ns-* logic. The write code is trivial; the read post-pass should be simple, straightforward, and similar to corresponding @auto sentinel-recognition code. Your comments, please. Edward -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
@auto-rst vs. @nosent
I've been following the recent discussion about replacing @auto with @nosent (and by extension, @auto-rst). Now, maybe I'm missing something obvious, but when I change my @auto-rst files to @nosent files, the resulting files do not contain the RST section headers that were automatically added by @auto-rst. My goal was to create RST style plain text files that could be easily navigated by non-Leo editors (Android for example via Dropbox sync), then reloaded in Leo. How is this supposed to work if I use @nosent instead? Rob -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: @auto-rst vs. @nosent
No, it's not. It's always been difficult for me to see what it's supposed to do. I figured it out on my own with some trial and error. Then there were issues with v5 reading earlier files (had something to do with where extra line feeds were or something). Thanks for your response, looks like I'll need to keep using @auto-rst for the foreseeable future. Rob.. On Saturday, February 14, 2015 at 1:13:29 PM UTC-5, Edward K. Ream wrote: On Sat, Feb 14, 2015 at 9:55 AM, Largo84 lar...@gmail.com javascript: wrote: ...when I change my @auto-rst files to @nosent files, the resulting files do not contain the RST section headers that were automatically added by @auto-rst. Oops. Good thing 5.1 will continue support for @auto-rst! My goal was to create RST style plain text files that could be easily navigated by non-Leo editors (Android for example via Dropbox sync), then reloaded in Leo. How is this supposed to work if I use @nosent instead? It looks like you've proven that @auto-rst is still useful. Thanks for these comments. Furthermore, I'm not sure @auto-rst is properly documented. I've put it on the list to check... Edward -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: @auto-rst vs. @nosent
On Sat, Feb 14, 2015 at 9:55 AM, Largo84 larg...@gmail.com wrote: ...when I change my @auto-rst files to @nosent files, the resulting files do not contain the RST section headers that were automatically added by @auto-rst. Oops. Good thing 5.1 will continue support for @auto-rst! My goal was to create RST style plain text files that could be easily navigated by non-Leo editors (Android for example via Dropbox sync), then reloaded in Leo. How is this supposed to work if I use @nosent instead? It looks like you've proven that @auto-rst is still useful. Thanks for these comments. Furthermore, I'm not sure @auto-rst is properly documented. I've put it on the list to check... Edward -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: @auto-rst vs. @nosent
On 2/14/2015 1:13 PM, Edward K. Ream wrote: On Sat, Feb 14, 2015 at 9:55 AM, Largo84 larg...@gmail.com mailto:larg...@gmail.com wrote: ...when I change my @auto-rst files to @nosent files, the resulting files do not contain the RST section headers that were automatically added by @auto-rst. Oops. Good thing 5.1 will continue support for @auto-rst! My goal was to create RST style plain text files that could be easily navigated by non-Leo editors (Android for example via Dropbox sync), then reloaded in Leo. How is this supposed to work if I use @nosent instead? It looks like you've proven that @auto-rst is still useful. Thanks for these comments. Furthermore, I'm not sure @auto-rst is properly documented. I've put it on the list to check... Edward -- @auto-md is useful for the same reasons. And afaik, is completely undocumented. --Jake -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: @auto-rst vs. @nosent
On Saturday, 14 February 2015 18:13:29 UTC, Edward K. Ream wrote: It looks like you've proven that @auto-rst is still useful. Thanks for these comments. Furthermore, I'm not sure @auto-rst is properly documented. I've put it on the list to check... This partially answers your question on what needs to be worked on in documentation, Edward. More generally, all these commands that you have recently changed need proper documentation, once the dust has settled. There were also some obscure points I came across while reading the manual some time ago, but I don't remember them specifically. -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
