> I think I had a look at every c submodules... So stupid I am !
heheh. But look how smart you are now, you've seen it, and a whole new
world opened up. :)
I'm striving to look for those "Doh!" moments as often as possible. Bring
'em on! It means I'm learning. (It wasn't always that way, I used
Sounds like you are describing a DSE, Domain Specific Editor, which would
be customized for the requirements of a framework such as Sphinx or Django.
A myLeoSettings.leo file would contain buttons, menus, commands, bindings etc.
specific to the project.
Not too simple, not feature overwhelming, ju
Edward has just closed
https://github.com/leo-editor/leo-editor/issues/73
which was a meta ticket / bug report referencing all the old Launchpad
bugs. Closing it means they're all either resolved or tracked by
updated github bugs. This represents a ton of organizational work,
nice job! :-)
Cheer
On Wednesday, November 12, 2014 10:08:57 AM UTC-6, Terry Brown wrote:
>
> Edward has just closed
> https://github.com/leo-editor/leo-editor/issues/73
> which was a meta ticket / bug report referencing all the old Launchpad
> bugs. Closing it means they're all either resolved or tracked by
> up
First, don't panic: I am not going to do anything about this until after
5.0 final.
The perfect import checks ensure (in some hard-to-define way) that
round-tripping (reading, then writing) any @auto file does not change in
any *significant* way. When the the checks fail, Leo inserts an @ignor
As stated in #99, I am having a hard time understanding exactly what is
meant. I won't target this bug for any particular release until I know
more about it.
Afaik, all key bindings made in myLeoSettings.py work, but I don't use
MacOS much.
Is anyone having any kind of key-binding problems o
All the parsers I find important work fine, re the .md
issues, I would be happy if
@auto index.md
was aliased to
@edit index.md
I'm more interested in the convenience of accessing files
from Leo than in having the files parsed into heirarchies.
I actually find the parsing of html too granular, I
Is it possible to branch another leo google group for minor newbie
day-to-day issues?
I'm using Leo as a daily organizer at work, and hope to someday transition
to a programmer that uses it.
When little problems or issues come up, it would be nice to have a
discussion that is separate from the r
On Wed, 12 Nov 2014 09:09:59 -0800 (PST)
Todd Mars wrote:
> Is it possible to branch another leo google group for minor newbie
> day-to-day issues?
> I'm using Leo as a daily organizer at work, and hope to someday
> transition to a programmer that uses it.
> When little problems or issues come u
On Wed, 12 Nov 2014 11:31:05 -0600
"'Terry Brown' via leo-editor" wrote:
> On Wed, 12 Nov 2014 09:09:59 -0800 (PST)
> Todd Mars wrote:
>
> > Is it possible to branch another leo google group for minor newbie
> > day-to-day issues?
> > I'm using Leo as a daily organizer at work, and hope to som
On Wed, Nov 12, 2014 at 9:31 AM, 'Terry Brown' via leo-editor <
leo-editor@googlegroups.com> wrote:
> So you want somewhere to address these issues without the noise of the
> power users-developers discussion? :-) That's not unreasonable.
>
We already have one! :)
https://groups.google.com/foru
11 matches
Mail list logo
