On Thu, Dec 8, 2016 at 5:37 PM, Edward K. Ream wrote:
> Rebecca and I will be on the road to Florida starting tomorrow morning.
> I'll have my laptop with me, and will be able to respond to emails.
>
happy holiday ;-)
> Edward
>
> --
> You received this message because you
Rebecca and I will be on the road to Florida starting tomorrow morning.
I'll have my laptop with me, and will be able to respond to emails.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop
Sorry for commentary on previous post. You said you had fixed enough
crashers, I'm wondering if some methods changed since you made your
original fixes which broke the curses GUI.
On Thursday, December 8, 2016 at 2:40:53 PM UTC-5, john lunzer wrote:
>
> I'm getting a traceback when I try to run
On Thu, Dec 8, 2016 at 10:57 AM, Largo84 wrote:
> Before I do that, is it possible that it's not working because they all
> have .txt instead of .rst as a file extension?
>
Not sure. If you use @auto-rst everything should work regardless of
extension.
> It didn't matter
On Thu, Dec 8, 2016 at 11:08 AM, Largo84 wrote:
> Looks like that fixed it, will report back if there are other issues. BTW,
> I liked using .txt because it was easier for other programs and mobile text
> apps to recognize the file type and open them outside of Leo.
>
I
I'm getting a traceback when I try to run with the --gui=curses on the most
recent Rev.
setting leoID from os.getenv('USER'): 'jlunzer'
reading settings in
/Users/jlunz/anaconda/adds/leo-editor/leo/config/leoSettings.leo
reading settings in /home/home51/lunz8748/.leo/myLeoSettings.leo
Using
My guess is using position methods is the way to go(*). I think there's
something about the way people come to Leo scripting that leads them down the
c.k.simulateCommand path, but I'm not really sure that's intentionally. My
feeling is that c.k.simulateCommand is best for occasional limited
Sorrynot very well formatted question.
When I use the c.k.simulateCommand() method, it does an immediate redraw of
the outline. I would like to suppress the redraw until after I am done
making changes. I am looking at using position methods to do the same
thing so that I control the
Looks like that fixed it, will report back if there are other issues. BTW,
I liked using .txt because it was easier for other programs and mobile text
apps to recognize the file type and open them outside of Leo.
Rob..
On Thursday, December 8, 2016 at 11:57:00 AM UTC-5, Largo84 wrote:
>
>
> Python is way too good a language to ignore. Don't be afraid of it.
>
>
> Not fear so much as not enough time to spend to learn it. I agree with
another comment you made earlier that the best way to learn is to have a
specific task (need) and from that figure out how to accomplish the
Before I do that, is it possible that it's not working because they all
have .txt instead of .rst as a file extension? It didn't matter before,
maybe now it does? I will change the file file extensions and try reloading
and see if that works and will report.
Rob.
On Thursday, December
On Thu, Dec 8, 2016 at 6:26 AM, Martin Monperrus wrote:
> Thanks for your answer.
>
> doc = new LeoDoc("foo.tex")
>
> This means that foo.tex already exists, has content, and I want to load it
> with Leo's API, before manipulating the nodes I'm interested in.
>
You
Thanks for your answer.
doc = new LeoDoc("foo.tex")
This means that foo.tex already exists, has content, and I want to load it
with Leo's API, before manipulating the nodes I'm interested in.
My question then reads: to add the Leo nodes (ie the Leo tags in Latex
comments) in the already
On Thu, Dec 8, 2016 at 5:05 AM, Martin Monperrus wrote:
>
> I would like to programmatically capture a subset of a latex document.
>
> If I add the right Leo's metadata to the document as Latex comments, I
> should be able to do this with Leo, something like:
>
>
Hi,
I would like to programmatically capture a subset of a latex document. If I
add the right Leo's metadata to the document as Latex comments, I should be
able to do this with Leo, something like:
doc = new LeoDoc("foo.tex")
node = doc.getNode("bar")
print node.text
Is it possible? Do you
On Tue, Dec 6, 2016 at 2:14 PM, Zoom.Quiet wrote:
> On Tue, Dec 6, 2016 at 12:47 PM, 'Terry Brown' via leo-editor
> wrote:
> > (How I feel about clones, YMMV)
> >
> ...
> > I can see why people are attracted to clones for this second category
On Tue, Dec 6, 2016 at 1:24 PM, Largo84 wrote:
I'm quite rusty when it comes to programming code and writing scripts (my
> last actual programming was 20 years ago in Pascal, never learned Python).
>
Pascal might have been called state-of-the-art in programming simplicity
On Tue, Dec 6, 2016 at 12:47 PM, 'Terry Brown' via leo-editor <
leo-editor@googlegroups.com> wrote:
Clones are really really good for creating task specific views of
> code, by gathering together all the nodes relevant to a particular
> development task, so you don't have to constantly scroll
On Wed, Dec 7, 2016 at 4:04 PM, Largo84 wrote:
> The .rst files are still coming in flat (all of them) and still getting
> the Qt large text warning.
>
Please send me one of the files.
Edward
--
You received this message because you are subscribed to the Google Groups
19 matches
Mail list logo