"fatal: No names found, cannot describe anything" is from executing `git
describe --tags` in a shallow clone that isn't deep enough to include a
tagged commit. Fixed in travis.yml by increasing the clone depth from
default of 50 to 100 with commit 4d7e814
I'm glad this came up, I was going to say something on this under the
title: "Leo, an embarrassment of riches that are too well hidden."
I was involved in another editor in the past, in it we followed another
convention for documentation. Say you added support for another language,
well,
于2018年10月11日周四 上午7:01写道：
>
>
> I recently went through all the settings in Leo, and wow, there's quite a bit
> of good stuff there. How much of that is in the docs? Had I not decided to
> look at *all* the settings, I would not have discovered many of them. I'd
> like a page that lists
Below are some random examples. It's hard for me to give you a fuller
answer as I now do know some Leo and so I'm less confused when I read the
docs - so I can't easily point out problems.
In the main tutorial page, the script in Accessing Outline Data doesn't
work - it's missing a
> Recent revs have fixed all Leo-related problems. Now there is a setup.py
> problem:
> [...]
> File "/home/travis/build/leo-editor/leo-editor/leo/core/leoGlobals.py",
> line 4890, in gitDescribe
> tag, distance, commit = describe[0].rsplit('-',2)
> IndexError: list index out of range
>
>
On Wed, Oct 10, 2018 at 1:22 PM wrote:
> My dream is that the documents be vastly improved.
Please tell me what you think should be added to CheatSheet.leo, or to the
tutorials.
Typing completion in the minibuffer is a good way to discover commands.
After that, leoPyRef.leo contains all the
I expect Emacs is of comparable complexity,how does
it offer such good documentation?
On Wed, Oct 10, 2018 at 1:22 PM wrote:
> I came to Leo because I wanted a programmable text editor that I can
> program in Python. I am an Emacs user who did not want to learn Emacs Lisp.
>
> My dream is that
I came to Leo because I wanted a programmable text editor that I can
program in Python. I am an Emacs user who did not want to learn Emacs Lisp.
My dream is that the documents be vastly improved. As it is, when it comes
to scripting in Leo so I can customize my experience, the docs are no help.
On Wednesday, October 10, 2018 at 6:32:54 AM UTC-5, Edward K. Ream wrote:
> "@test event classes" is failing because QtCore hasn't been imported
correctly:
Recent revs have fixed all Leo-related problems. Now there is a setup.py
problem:
$ python setup.py bdist_wheel | grep -v -e '^adding'
"@test event classes" is failing because QtCore hasn't been imported
correctly:
==
ERROR: runTest (leo.core.leoTest.GeneralTestCase)
@test event classes
Traceback (most recent call last):
File
On Wed, Oct 10, 2018 at 2:50 AM 'tfer' via leo-editor <
leo-editor@googlegroups.com> wrote:
> Even with the caveats I've mentioned, Neovim should be one of the easiest
> to put into Leo. On non window systems you could embed the terminal
> version into the n-curses like version of Leo. For all
On Tue, Oct 9, 2018 at 11:12 AM Kent Tenney wrote:
> I also think it would be great if Leo could use neovim for the editing
> experience.
>
> This project
> https://github.com/neovim/python-client
>
> says:
>
> You can embed neovim into your python application instead of binding to a
> running
Even with the caveats I've mentioned, Neovim should be one of the easiest
to put into Leo. On non window systems you could embed the terminal
version into the n-curses like version of Leo. For all systems you'd take
the Qt front end version of Neovim and get it to take the place of the
13 matches
Mail list logo
