I am not sure if these problems are related, but they might be, or
they might be problems for me because I am not completely fluent using
leo
-- double clicking a node does not work as it should (i.e. write a
@file node)
-- can not drag and drop nodes
-- commands in mini-buffer do not work
Could
> I don't see this behavior, either on Ubuntu or XP.
Well that just makes it more interesting ...
When I start up Qt Leo I get the following messages (which may have
nothing to do with the problem):
:~/leo-editor$ python launchLeo.py --gui=qt
reading settings in /home/.../leo-editor/leo/config/l
Thanks again
These commands below work
at = c.atFileCommands
p = c.currentPosition() # get the current position
fileName = p.atAutoNodeName()
at.readOneAtAutoNode(fileName,p)
I understand the second and third commands to get the current position
and the file name.
Originally I thought the fourt
On Mon, Mar 9, 2009 at 8:12 PM, Edward K. Ream wrote:
>> This would configure individual nodes - e.g. allow storing colors in
>> uAs, as in cleo plugin.
>
> Oh. I'm with you now.
Should I push a demo implementation (few small changes to core & a plugin)?
--
Ville M. Vainio
http://tinyurl.com
On Mar 9, 7:30 am, Jesse Aldridge wrote:
> Is there an easy way to move a clone node over a long distance? I see
> that when a clone is pasted after cutting or copying it is no longer a
> clone, but just a regular node.
I think you should use command "Paste Node as clone" from outline menu
in
On Mon, Mar 9, 2009 at 12:33 PM, mdb wrote:
>
> I can create an @auto note that brings back Latex commands created by
> the rst2 plugin and LEO was smart enough to start the node edit box with
> @language tex
>
> I might be best off using a created ReST file as the intermediary step
> and I could
On Mon, Mar 9, 2009 at 12:54 PM, Ville M. Vainio wrote:
>
> On Mon, Mar 9, 2009 at 6:21 PM, Edward K. Ream
> wrote:
>
> > My thought is that the obvious place to configure widgets is in
> > leoSettings.leo and myLeoSettings.leo. At present, there is a conflict
> in
> > Qt itself: apparently spe
On Mon, Mar 9, 2009 at 6:21 PM, Edward K. Ream wrote:
> My thought is that the obvious place to configure widgets is in
> leoSettings.leo and myLeoSettings.leo. At present, there is a conflict in
> Qt itself: apparently specifying a stylesheet interferes with programmatic
> settings.
This woul
Thanks Edward, this helps
I can create an @auto note that brings back Latex commands created by
the rst2 plugin
and LEO was smart enough to start the node edit box with @language tex
I might be best off using a created ReST file as the intermediary step
and I could not get similarly on the read
On Sat, Mar 7, 2009 at 3:21 PM, Ville M. Vainio wrote:
>
> It's obvious we want to do this (it's been done in tk plugin as well).
If by "this" you mean that we want to make widgets as configurable as
possible, then I certainly agree. I am not following the rest of this,
however,
My thought is
On Sat, Mar 7, 2009 at 10:35 PM, Steve Zatz wrote:
>
> Current trunk, QT plugin, on Ubuntu 8.10. When you import an @thin
> file using the import derived file command, the file is imported but
> only top level nodes are present with no nodes appearing under the top
> level nodes. When I open a
On Mon, Mar 9, 2009 at 10:13 AM, mdb wrote:
>
> I want simplify creating Latex/Beamer slide files and need help or
> suggestions.
>
> I can do the following
> --turn a leo node into an external rst or latex file using the rst3
> plugin
> --translate a rst file to basic Latex or Beamer using a p
I want simplify creating Latex/Beamer slide files and need help or
suggestions.
I can do the following
--turn a leo node into an external rst or latex file using the rst3
plugin
--translate a rst file to basic Latex or Beamer using a python
script outside of leo
(using docutils and
On Mar 9, 9:09 am, TL wrote:
> I suspect that the Vim emulation is not installed correctly for some
> reason. If it's installed correctly you will see a large number of
> "redefining shortcut" entries in the "Log" tab card when your Leo file
> is first opened.
>
look to be about 30, all seem
> On windows XP.
I am also running on WinXP.
I suspect that the Vim emulation is not installed correctly for some
reason. If it's installed correctly you will see a large number of
"redefining shortcut" entries in the "Log" tab card when your Leo file
is first opened.
Did you place a copy of "@
On Mon, Mar 9, 2009 at 1:30 AM, Jesse Aldridge wrote:
>
> Is there an easy way to move a clone node over a long distance? I see
> that when a clone is pasted after cutting or copying it is no longer a
> clone, but just a regular node.
Don't use copy/paste.
Enable typing completion, then type p
On Mon, Mar 9, 2009 at 1:59 AM, Jesse Aldridge wrote:
>
> But if I change the first line to:
> import leo.core.leoFind as leoFind
This is the proper way to do imports. Why the other way fails may depend on
path issues.
Edward
--~--~-~--~~~---~--~~
You received
17 matches
Mail list logo
