Re: using @first and not getting expected results

2017-02-20 Thread Edward K. Ream
On Wednesday, February 8, 2017 at 12:19:58 PM UTC-6, Eric S. Johansson wrote: > There was no mention of where the@first directive should go [in several places in the docs]. Just fixed, in LeoDocs.leo and on the web. Edward -- You received this message because you are subscribed to the

Re: using @first and not getting expected results

2017-02-08 Thread Eric S. Johansson
On Wednesday, February 8, 2017 at 5:50:24 AM UTC-5, Edward K. Ream wrote: > > ​No no no no. The @first lines must be first. > > I don't know how I can be any clearer. > > I apologize for frustrating you.. My misunderstanding was a combination of not reading the documentation clearly and going

Re: using @first and not getting expected results

2017-02-08 Thread Edward K. Ream
On Tue, Feb 7, 2017 at 3:04 PM, Eric S. Johansson wrote: > attached is a test case showing an @first that does not give expected > results. what I have in my @file section is: > > @language python > @tabwidth -4 > << docstring >> > > @first #! /usr/bin/python3 > @first #

Re: using @first and not getting expected results

2017-02-07 Thread Eric S. Johansson
attached is a test case showing an @first that does not give expected results. what I have in my @file section is: @language python @tabwidth -4 << docstring >> @first #! /usr/bin/python3 @first # a first line @others if __name__ == '__main__': main() # a comment when you load up the

Re: using @first and not getting expected results

2017-02-07 Thread Edward K. Ream
On Tue, Feb 7, 2017 at 9:56 AM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: > is the #@@first supposed to be blank? > ​Yes. ​ > Thanks for the workaround but yes it is counterintuitive. It seems to me > that having @first is the out of sequence way of putting in first

Re: using @first and not getting expected results

2017-02-07 Thread 'Terry Brown' via leo-editor
> is the #@@first supposed to be blank? Thanks for the workaround but yes it is > counterintuitive. It seems to me that having @first is the out of sequence > way of putting in first lines. Should I file a bug report? I think it's working as intended - not sure what the docs. say but my

Re: using @first and not getting expected results

2017-02-07 Thread Eric S. Johansson
On Tuesday, February 7, 2017 at 9:26:00 AM UTC-5, Jacob Peck wrote: > > I'm not sure if it's documented anywhere, but when I need to use @first, I > always need to put it as the very first line in the body node of the > @file/clean/yadayada, so: > > @first #! /usr/bin/python3 > @language

Re: using @first and not getting expected results

2017-02-07 Thread Jacob Peck
I'm not sure if it's documented anywhere, but when I need to use @first, I always need to put it as the very first line in the body node of the @file/clean/yadayada, so: @first #! /usr/bin/python3 @language python @and-so-on Hope this helps, -->Jake On 2/7/2017 9:13 AM, Eric S. Johansson

using @first and not getting expected results

2017-02-07 Thread Eric S. Johansson
in my @file section I have the following: @language python @tabwidth -4 @first #! /usr/bin/python3 @first # a first line << docstring >> @others if __name__ == '__main__': main() # a comment what I find saved in the output file is: #@+leo-ver=5-thin #@+node:alsoeric.20170202001826.1: *