I use markdown most of the time, because I've learned it, and that largely
due to the amount of time spent in the Stack Exchange network and now
GitHub. However I increasingly chafe under markdown's limitations and have
targetted as Asciidoc as my escape path. I tried rst but balked at the
My LaTeX processor choked on 2 instances of an unknown UTF8 character.
Probably came into Leo when I copied from somewhere else (perhaps an MS
Word document). Anyway, there was no visual clue in Leo where the offending
characters were. By process of elimination I found the offending node and
On Thursday, October 17, 2019 at 2:52:53 PM UTC+1, Rob wrote:
>
> Curious what other Leonistas use when writing plain text (not coding).
> Over the many years of using Leo, I have used markdown (md), multi-markdown
> (mmd), rst and org mode (experimented some, but don't really understand
>
On Thu, Oct 17, 2019 at 8:42 AM Chris George wrote:
>
>
>> Oh, I suppose Leo could run the rST through the sphinx tool chain, and
>> render the resulting html, or better, open the resulting page in a
>> browser. Rather than reopening #333, I have just created #1388. It's
>> schedule for Leo
I write fiction, nonfiction, and some technical documents (not so much
anymore).
For fiction I use plain text. Anything more is simply a distraction.
For nonfiction, I use rst as I learned it along with Leo. Links, bold,
italics etc. are easy with it. I could probably have used markdown but by
Curious what other Leonistas use when writing plain text (not coding). Over
the many years of using Leo, I have used markdown (md), multi-markdown
(mmd), rst and org mode (experimented some, but don't really understand
it). Haven't tried asciidoc yet. My current writing practice is:
- Write
>
> Oh, I suppose Leo could run the rST through the sphinx tool chain, and
> render the resulting html, or better, open the resulting page in a
> browser. Rather than reopening #333, I have just created #1388. It's
> schedule for Leo 6.1, but no guarantees.
>
> Edward
>
The browser based
On Thu, Oct 17, 2019 at 3:51 AM jkn wrote:
Thanks for #1398.
>
You're welcome. It should happen in a few days.
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
On Thu, Oct 17, 2019 at 12:17 AM gar wrote:
> I am talking about column with 'find-next: F3', , 'replace-all'
> elements in the 'Find' pane.
> I do remember that in version 5.9 of Leo they were accessible.
> But now they are just labels with helper texts, which cannot be pressed.
>
This is
On Thu, Oct 17, 2019 at 1:11 AM Quaraman wrote:
>
> I installed and run Leo 6.0-final in Python 3.8 with following changes:
>
[snip]
Thanks for this workaround. An easier one is to install Leo using git.
That way you get the latest code.
Edward
--
You received this message because you are
On Wed, Oct 16, 2019 at 5:04 PM The Living Cosmos
wrote:
There was a comment somewhere on the Leo website about Ed's methodology to
> understand a large code base. It said something like:
>
> "I create a new git repo and import all the files using @clean" or
> something like that.
>
> If
On Wednesday, October 16, 2019 at 12:24:16 PM UTC+1, Edward K. Ream wrote:
>
> On Wed, Oct 16, 2019 at 5:04 AM jkn >
> wrote:
>
> > I for one would appreciate a bit of an explanation of the 'very
> different workflow required'; I am kinda used to using @file etc. but abit
> unclear as to how
Hi @all,
I installed and run Leo 6.0-final in Python 3.8 with following changes:
*file: Python38\Lib\site-packages\leo\core\leoApp.py:*
line 2392 : t1 = time.process_time()
*rewrited method createCursesGui to:*
def createCursesGui(self, fileName='', verbose=False):
self.createQtGui()
I tried
>
> Work around:
>
> set HOME=%USERPROFILE%
> mkdir %HOME%\.leo
> echo "My ID" > %HOME%\.leo\.leoID.txt
> leo-console
>
> Note: skip the `set HOME` line if you already have it defined.
>
*DON'T* quote My ID or you'll break your .leo files. See
14 matches
Mail list logo
