leo-editor / blog

Blog source code

Leo https://leo-editor.github.io/leo-editor/ 6.7.8 is now available on GitHub and pypi.

Leo is an IDE, outliner and PIM.

The highlights of Leo 6.7.8

This release simplifies Leo's install process. See https://leo-editor.github.io/leo-editor/getting-started.html

• PR #3757: (leoTokens.py) Make Leo's beautifier 3x faster.
• PR #3771: Revert colorizing of f-strings.
• PR #3786: Support Nim.
• PR #3790: Add "get-unl" command to Leo's server.
• PR #3805: Fix problems with auto-completion and calltips.
• PR #3806: Fix problems with Leo's go-back and go-forward commands.
• PR #3807: Improve Leo's Python importer.
• PR #3817: Allow relative paths in gnx-based UNLs.
• The usual minor improvements and bug fixes.

Links

• Download Leo
• Install Leo
• 6.7.8 Issues
• 6.7.8 Pull Requests
• Documentation
• Tutorials
• Video tutorials
• Forum
• Download
• Leo on GitHub
• LeoVue
• What people are saying about Leo
• A web page that displays .leo files
• More links

blog's Issues

Create "leo fragment" css

To make leo outline segments look good, we should create a canonical html presentation for it. To put it in jade-like presentation, it could be something like:

.leofragment
  .n.l0
    .h headline for root item
    .b body text
  .n.l1 
     .h headline of child
     .b body text 

Here, "l0" and "l1" are node "levels" that are translated to left margin of the div

How well does or doesn't Pelican handle Leo sentinels?

From readme: "You can use Leo to edit the article, but I'd recommend using @auto-rst. Not sure how well Pelican handles sentinels."

would be a good idea to test this, find out what does and doesn't work, and perhaps see if it's worth doing something about.

Move blog URL out of root

Publish blog to http://leo-editor.github.io/blog sub-folder instead of root.

Part of upstream leo-editor/leo-editor#480

Side effect is to simplify the publishing process: we don't need to manage 2 repo's anymore just to add an article.

• In GH navigate to Repo >> Settings >> Enable Github Pages to publish from ./docs folder in master branch.
• publish Content
• merge or discard mismatched content
• Erase blog content from other repo