Re: Leo as wiki replacement
So I run the default example @rst node and it creates the nice looking html
page. Then I decided to change the .html to .pdf and see how the pdf looks.
I'm guessing I skipped a bunch of steps because that seems too easy. I have
the following error:
Unexpected docutils exception
Traceback (most recent call last):
File "/home/lang/leo-editor/leo/core/leoRst.py", line 1678, in writeToDocutils
settings_overrides=overrides)
File "/usr/lib/python2.7/dist-packages/docutils/core.py", line 414,
in publish_string
enable_exit_status=enable_exit_status)
File "/usr/lib/python2.7/dist-packages/docutils/core.py", line 662,
in publish_programmatically
output = pub.publish(enable_exit_status=enable_exit_status)
File "/usr/lib/python2.7/dist-packages/docutils/core.py", line 219, in publish
output = self.writer.write(self.document, self.destination)
File "/usr/lib/python2.7/dist-packages/docutils/writers/__init__.py",
line 80, in write
self.translate()
File "/home/lang/leo-editor/leo/plugins/leo_pdf.py", line 658, in translate
visitor = PDFTranslator(self,self.document)
File "/home/lang/leo-editor/leo/plugins/leo_pdf.py", line 782, in __init__
self.styleSheet = getStyleSheet()
File "/home/lang/leo-editor/leo/plugins/leo_pdf.py", line 299, in
getStyleSheet
stylesheet = StyleSheet1()
NameError: global name 'StyleSheet1' is not defined
rst3: 1 files in 0.13 sec.
I'm have docutils installed. Leo from git today.
On Fri, May 12, 2017 at 1:50 PM, Chris George wrote:
> I use Leo strictly for writing, restructured text to .odt using docutils.
> I also use it as my data bank for quotes, snippets of interesting info,
> bookmarks, recipes, etc. It makes it easy to keep information organized and
> simple to find again when I need it.
>
>
> Chris
>
> On Fri, May 12, 2017 at 12:38 PM, Largo84 wrote:
>
>> Sounds a lot like how I use Leo. I'm not a programmer either (unless you
>> count minimal scripting in LaTex). I write extensively in Leo (LaTex, HTML
>> and markdown mostly). I recently tried Scrivener, but quickly came back to
>> Leo after seeing that Pandoc will be easy enough for me to use. Don't
>> hesitate to ask, it's a great group and usually somebody can and will help.
>>
>> If you haven't yet, try out the linking capabilities.
>>
>> Rob.
>>
>>
>> On Friday, May 12, 2017 at 3:12:46 PM UTC-4, Lang Hurst wrote:
>>>
>>> Thanks for the response. Nothing special about vimwiki, it's just a wiki
>>> I use for organization and writing. Substitute any wiki for the use. More
>>> interested in the linking and moving back and forth. I'm feeling like I
>>> just have to change my thinking style and this should be pretty awesome.
>>> Nothing like changing up workflow 1/2 way through a Masters, but it seems
>>> to be the way that I always work. Anyway, thanks again.
>>>
>>> -Lang
>>>
>>> On Friday, May 12, 2017 at 12:00:26 PM UTC-7, Terry Brown wrote:
On Fri, 12 May 2017 11:11:03 -0700 (PDT)
Lang Hurst wrote:
> Hello. I just spent a few days looking at Leo after seeing a post of
> Mr. Reams on the npyscreen group. Leo looks pretty damn cool. The
> problem is I don't do much coding anymore. I mostly just use vimwiki
> to manage my website, but mostly for organizing my notes and writing
> papers. I've been writing the papers in LaTex while in vimwiki and
> then compiling it from there. Seems like I could use Leo to do most
> of this. Before I spend more time though, am I using this tool in a
> way that doesn't make sense? Is there anyone who does this? I can see
> how awesome Leo could be for straight up writing, but just wondering
> how or if people utilize it outside of that or just python
> programming.
I think a lot of people use Leo for non-coding / writing type
purposes. I've been writing papers via Leo -> markdown -> pandoc,
which uses LaTeX for PDF output.
Not familiar with vimwiki so not sure how much automation that's
bringing to the LaTeX writing process. Leo's abbreviations can be
helpful, e.g. expanding something like fig;; to
\begin{figure}\end{figure}
Not aware of any particular pre-view apparatus, but it's very easy to
write button scripts that generate a doc. being viewed in PDF preview
or whatever.
Cheers -Terry
>>> --
>> 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.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "leo-editor" group.
> To unsubscribe from this topic, visit https://groups
Re: Leo as wiki replacement
I use Leo strictly for writing, restructured text to .odt using docutils. I
also use it as my data bank for quotes, snippets of interesting info,
bookmarks, recipes, etc. It makes it easy to keep information organized and
simple to find again when I need it.
Chris
On Fri, May 12, 2017 at 12:38 PM, Largo84 wrote:
> Sounds a lot like how I use Leo. I'm not a programmer either (unless you
> count minimal scripting in LaTex). I write extensively in Leo (LaTex, HTML
> and markdown mostly). I recently tried Scrivener, but quickly came back to
> Leo after seeing that Pandoc will be easy enough for me to use. Don't
> hesitate to ask, it's a great group and usually somebody can and will help.
>
> If you haven't yet, try out the linking capabilities.
>
> Rob.
>
>
> On Friday, May 12, 2017 at 3:12:46 PM UTC-4, Lang Hurst wrote:
>>
>> Thanks for the response. Nothing special about vimwiki, it's just a wiki
>> I use for organization and writing. Substitute any wiki for the use. More
>> interested in the linking and moving back and forth. I'm feeling like I
>> just have to change my thinking style and this should be pretty awesome.
>> Nothing like changing up workflow 1/2 way through a Masters, but it seems
>> to be the way that I always work. Anyway, thanks again.
>>
>> -Lang
>>
>> On Friday, May 12, 2017 at 12:00:26 PM UTC-7, Terry Brown wrote:
>>>
>>> On Fri, 12 May 2017 11:11:03 -0700 (PDT)
>>> Lang Hurst wrote:
>>>
>>> > Hello. I just spent a few days looking at Leo after seeing a post of
>>> > Mr. Reams on the npyscreen group. Leo looks pretty damn cool. The
>>> > problem is I don't do much coding anymore. I mostly just use vimwiki
>>> > to manage my website, but mostly for organizing my notes and writing
>>> > papers. I've been writing the papers in LaTex while in vimwiki and
>>> > then compiling it from there. Seems like I could use Leo to do most
>>> > of this. Before I spend more time though, am I using this tool in a
>>> > way that doesn't make sense? Is there anyone who does this? I can see
>>> > how awesome Leo could be for straight up writing, but just wondering
>>> > how or if people utilize it outside of that or just python
>>> > programming.
>>>
>>> I think a lot of people use Leo for non-coding / writing type
>>> purposes. I've been writing papers via Leo -> markdown -> pandoc,
>>> which uses LaTeX for PDF output.
>>>
>>> Not familiar with vimwiki so not sure how much automation that's
>>> bringing to the LaTeX writing process. Leo's abbreviations can be
>>> helpful, e.g. expanding something like fig;; to
>>>
>>> \begin{figure}\end{figure}
>>>
>>> Not aware of any particular pre-view apparatus, but it's very easy to
>>> write button scripts that generate a doc. being viewed in PDF preview
>>> or whatever.
>>>
>>> Cheers -Terry
>>>
>> --
> 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.
>
--
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.
Re: Leo as wiki replacement
Sounds a lot like how I use Leo. I'm not a programmer either (unless you
count minimal scripting in LaTex). I write extensively in Leo (LaTex, HTML
and markdown mostly). I recently tried Scrivener, but quickly came back to
Leo after seeing that Pandoc will be easy enough for me to use. Don't
hesitate to ask, it's a great group and usually somebody can and will help.
If you haven't yet, try out the linking capabilities.
Rob.
On Friday, May 12, 2017 at 3:12:46 PM UTC-4, Lang Hurst wrote:
>
> Thanks for the response. Nothing special about vimwiki, it's just a wiki I
> use for organization and writing. Substitute any wiki for the use. More
> interested in the linking and moving back and forth. I'm feeling like I
> just have to change my thinking style and this should be pretty awesome.
> Nothing like changing up workflow 1/2 way through a Masters, but it seems
> to be the way that I always work. Anyway, thanks again.
>
> -Lang
>
> On Friday, May 12, 2017 at 12:00:26 PM UTC-7, Terry Brown wrote:
>>
>> On Fri, 12 May 2017 11:11:03 -0700 (PDT)
>> Lang Hurst wrote:
>>
>> > Hello. I just spent a few days looking at Leo after seeing a post of
>> > Mr. Reams on the npyscreen group. Leo looks pretty damn cool. The
>> > problem is I don't do much coding anymore. I mostly just use vimwiki
>> > to manage my website, but mostly for organizing my notes and writing
>> > papers. I've been writing the papers in LaTex while in vimwiki and
>> > then compiling it from there. Seems like I could use Leo to do most
>> > of this. Before I spend more time though, am I using this tool in a
>> > way that doesn't make sense? Is there anyone who does this? I can see
>> > how awesome Leo could be for straight up writing, but just wondering
>> > how or if people utilize it outside of that or just python
>> > programming.
>>
>> I think a lot of people use Leo for non-coding / writing type
>> purposes. I've been writing papers via Leo -> markdown -> pandoc,
>> which uses LaTeX for PDF output.
>>
>> Not familiar with vimwiki so not sure how much automation that's
>> bringing to the LaTeX writing process. Leo's abbreviations can be
>> helpful, e.g. expanding something like fig;; to
>>
>> \begin{figure}\end{figure}
>>
>> Not aware of any particular pre-view apparatus, but it's very easy to
>> write button scripts that generate a doc. being viewed in PDF preview
>> or whatever.
>>
>> Cheers -Terry
>>
>
--
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.
Re: Leo as wiki replacement
On Fri, May 12, 2017 at 2:12 PM, Lang Hurst wrote: > Thanks for the response. Nothing special about vimwiki, it's just a wiki I > use for organization and writing. Substitute any wiki for the use. More > interested in the linking and moving back and forth. I'm feeling like I > just have to change my thinking style and this should be pretty awesome. > Nothing like changing up workflow 1/2 way through a Masters, but it seems > to be the way that I always work. Anyway, thanks again. > ​Feel free to ask questions here. Welcome aboard. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Leo as wiki replacement
Thanks for the response. Nothing special about vimwiki, it's just a wiki I
use for organization and writing. Substitute any wiki for the use. More
interested in the linking and moving back and forth. I'm feeling like I
just have to change my thinking style and this should be pretty awesome.
Nothing like changing up workflow 1/2 way through a Masters, but it seems
to be the way that I always work. Anyway, thanks again.
-Lang
On Friday, May 12, 2017 at 12:00:26 PM UTC-7, Terry Brown wrote:
>
> On Fri, 12 May 2017 11:11:03 -0700 (PDT)
> Lang Hurst > wrote:
>
> > Hello. I just spent a few days looking at Leo after seeing a post of
> > Mr. Reams on the npyscreen group. Leo looks pretty damn cool. The
> > problem is I don't do much coding anymore. I mostly just use vimwiki
> > to manage my website, but mostly for organizing my notes and writing
> > papers. I've been writing the papers in LaTex while in vimwiki and
> > then compiling it from there. Seems like I could use Leo to do most
> > of this. Before I spend more time though, am I using this tool in a
> > way that doesn't make sense? Is there anyone who does this? I can see
> > how awesome Leo could be for straight up writing, but just wondering
> > how or if people utilize it outside of that or just python
> > programming.
>
> I think a lot of people use Leo for non-coding / writing type
> purposes. I've been writing papers via Leo -> markdown -> pandoc,
> which uses LaTeX for PDF output.
>
> Not familiar with vimwiki so not sure how much automation that's
> bringing to the LaTeX writing process. Leo's abbreviations can be
> helpful, e.g. expanding something like fig;; to
>
> \begin{figure}\end{figure}
>
> Not aware of any particular pre-view apparatus, but it's very easy to
> write button scripts that generate a doc. being viewed in PDF preview
> or whatever.
>
> Cheers -Terry
>
--
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.
Re: Leo as wiki replacement
On Fri, 12 May 2017 11:11:03 -0700 (PDT)
Lang Hurst wrote:
> Hello. I just spent a few days looking at Leo after seeing a post of
> Mr. Reams on the npyscreen group. Leo looks pretty damn cool. The
> problem is I don't do much coding anymore. I mostly just use vimwiki
> to manage my website, but mostly for organizing my notes and writing
> papers. I've been writing the papers in LaTex while in vimwiki and
> then compiling it from there. Seems like I could use Leo to do most
> of this. Before I spend more time though, am I using this tool in a
> way that doesn't make sense? Is there anyone who does this? I can see
> how awesome Leo could be for straight up writing, but just wondering
> how or if people utilize it outside of that or just python
> programming.
I think a lot of people use Leo for non-coding / writing type
purposes. I've been writing papers via Leo -> markdown -> pandoc,
which uses LaTeX for PDF output.
Not familiar with vimwiki so not sure how much automation that's
bringing to the LaTeX writing process. Leo's abbreviations can be
helpful, e.g. expanding something like fig;; to
\begin{figure}\end{figure}
Not aware of any particular pre-view apparatus, but it's very easy to
write button scripts that generate a doc. being viewed in PDF preview
or whatever.
Cheers -Terry
--
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.
Leo as wiki replacement
Hello. I just spent a few days looking at Leo after seeing a post of Mr. Reams on the npyscreen group. Leo looks pretty damn cool. The problem is I don't do much coding anymore. I mostly just use vimwiki to manage my website, but mostly for organizing my notes and writing papers. I've been writing the papers in LaTex while in vimwiki and then compiling it from there. Seems like I could use Leo to do most of this. Before I spend more time though, am I using this tool in a way that doesn't make sense? Is there anyone who does this? I can see how awesome Leo could be for straight up writing, but just wondering how or if people utilize it outside of that or just python programming. -- 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.
ENB: 3 Ahas re guis
This is an Engineering Notebook post. It will be of interest only to Leo's core devs. Three Ahas appeared yesterday: - (The big one) Use vnodes instead of npyscreen.TreeData nodes. - Event handling in the curses gui is easy, and almost complete. - Most unit tests should pass when using the null gui. *Using vnodes in the curses gui* After exercise yesterday I saw how to collapse the complexity of the tree code. Aha: use vnodes instead of (a subclass of) npyscreen.TreeData. Instantly, all linkage and update problems go away. This will require an override (rewrite) of npyscreen.MultiLine.update, the code that redraws the outline. That's not a big deal. ML.update does nothing but call curses.addstr, albeit with complicated code to determine the position args to addstr. The override, LeoMLTree.update, will just call c.frame.tree.redraw, that is, CursesTree.redraw.This code is a copy of the code from the Qt gui, with Qt calls commented out. We just need to teach the (ex Qt) drawing code how to use curses. There may be complications. A top-level "*native*" switch in cursesGui2.py will mark the required changes. There should be no need for the npyscreen classes to know anything about this switch: the new code will override all affected npyscreen methods. *Generating events* The curses gui *does* generate events, namely keystrokes and mouse clicks. npyscreen.InputHandler.handle_input is the one and only "event handler". Leo's curses gui code already contains handlers to handle these. These handlers will call several methods in Leo's core, especially, c.frame.tree.select. So you could say that *tree.select is an event handler in Leo's core*. tree.select calls methods in cursesGui2.py. In effect, tree.select generates *other* events. The code (copied from the Qt gui) in cursesGui2.py *already *has lockouts to prevent endless loops. In short, handling events should be easy. *Unit testing with the null gui* The null gui could, and should, represent Leo's tree, body and log panes using *string widgets*, based on the StringTextWrapper in leoFrame.py. In effect, npyscreen widgets are string widgets too. Linking up the string widgets in Leo's null gui would be almost identical to the linking code in CursesGui.createCursesTop & helpers. Once that is done, most unit tests should pass. We could run the unit tests from Leo's bridge, but it would be simpler have the event loop for Leo's --gui=null option do just the following: - load unitTest.leo (using the null gui, of course), - execute run-all-unit-tests-locally, - quit. There is no urgency connected to this Aha, but it's worth noting. *Summary* Using Leo's native tree of vnodes instead of TreeData nodes will eliminate all sorts of problems. LeoMLTree.update will just call c.frame.tree.redraw, that is, CursesTree.redraw. CTree.redraw must generate the proper calls to curses.addstr. The "native" switch in cursesGui.py will mark all the changes. Event handling in the curses gui should much like the Qt gui code. Running unit tests with a null gui (--gui=null) will be very fast. Running tests with --gui=curses is already very fast. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Sentinels in PHP meant for web
On Thu, May 11, 2017 at 9:20 PM, Adrian Calvin wrote: > Is there a way to somehow make these TOP sentinels act as if they are when > you use the directive "language @html", and sentinels are encased as > "
Sentinels in PHP meant for web
Hi, I am new to leo, I have google, but still am unsure. I am wondering how to deal with sentinels at the TOP of my PHP scripts. These happen before the "https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
