Try this for yourself and see what happens:
Scenario 1 (@@ Section as first child node)
1) Create a new new empty node say, @auto-md Some File.md
2) Create a new child node say, @@ Section 1 (body text optional)
3) Save the file to create the external file. Viewed in external editor,
the layout is as expected.
4) Refresh from disk.
The read code creates a !Declarations node with the following body text:
#@@ Section1
Body text
Scenario 2 (@@ Section *not* the first child node)
1) Same as above except the @@ Section is a subsequent node (or child node).
2) Save and refresh from disk.
3) Now the parent node node contains:
``#@@ Section 1`` as body text, not the node header as expected.
If your setup doesn't duplicate this behavior, I will send you a small
sample file.
Rob.........
On Sunday, December 11, 2016 at 4:32:08 AM UTC-5, Edward K. Ream wrote:
>
> On Fri, Dec 9, 2016 at 12:41 PM, Largo84 <lar...@gmail.com <javascript:>>
> wrote:
>
>> Terry, I added an addendum to my original post that I think indicates
>> what caused the problem, the use of ``@@`` in the node headline. Not sure
>> if that's a bug or a feature:-)
>>
>>
>
> Greetings from Northern Mississippi :-)
>
> If you have ever written the .md file from Leo, the markdown writer will
> use hash ('#') markup for all sections. And even if not, @@ should never
> affect underlining, which is limited to "=" or "-" characters.
>
> My guess is that level is zero, so maybe the actual markup isn't the real
> issue. Please send me the file, so I can see exactly what is happening.
>
> EKR
>
--
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 https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
