OK, got the @string thing to work. I was putting eg.
@string selected-background-color = #fdf5f5
in the *body* rather than the headline.
I'm not sure to what extent this is a 'Doh!', and to what extent this
might be better spelled out somewhere.
J^n
I downloaded the latest snapshot and tangling still doesn't work. And
it's not on that list.
Same error as previously reported.
On Tue, Jun 2, 2009 at 3:36 AM, Edward K. Ream edream...@gmail.com wrote:
My inbox is now empty re Leo, and all known open bugs are now listed
at:
On Thu, Jun 4, 2009 at 12:48 PM, jkn jkn...@nicorp.f9.co.uk wrote:
OK, got the @string thing to work. I was putting eg.
@string selected-background-color = #fdf5f5
in the *body* rather than the headline.
I'm not sure to what extent this is a 'Doh!', and to what extent this
might be
On Thu, Jun 4, 2009 at 2:16 PM, Ville M. Vainio vivai...@gmail.com wrote:
Perhaps your pattern of working is suboptimal, you if explicitly
'if you', obviously (busy mind).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this
On Jun 4, 12:16 pm, Ville M. Vainio vivai...@gmail.com wrote:
Perhaps your pattern of working is suboptimal,
This is quite possible...
you if explicitly
switch between tree and body modes.
I always start moving around the tree by pressing alt + arrow, then
either keep the alt key down
Here's an annoying Qt one:
In Tk, if I have:
variable (the are significant in this example)
and double-click inside it, the following is selected:
variable
In Qt, this is selected:
variable
The Tk functionality is normal, IMO
Mike
On Thu, Jun 4, 2009 at 4:34 PM, jkn jkn...@nicorp.f9.co.uk wrote:
Actually, I do think the docs could be clearer here.
the 'Leo Directives' in Chapter 2 says:
quote
Leo directives control such things as syntax coloring, line wrapping
within the body pane and the width of tabs. **Leo
On Jun 4, 2:41 pm, Ville M. Vainio vivai...@gmail.com wrote:
The deal is that @ is not a reserved character in any way. At best,
@ tells the user that leo, or a leo plugin, might have a special
interpretation for this character.
sure - but it should still be mentioned (as might your added
Perhaps your pattern of working is suboptimal, you if explicitly
switch between tree and body modes.
I always start moving around the tree by pressing alt + arrow, then
either keep the alt key down or release it, depending how I feel like
;-). Then, I return to body pane by pressing enter.
On Thu, Jun 4, 2009 at 7:54 PM, Matt Wilkie map...@gmail.com wrote:
Alt-T is easy to discover via Help Print Bindings as it's called
focus-to-tree. The descriptions for Alt-arrow do not reveal that they
also focus-to-tree before carrying out their true function, e.g.
expand-and-go-right. I
On Jun 4, 7:19 pm, Ville M. Vainio vivai...@gmail.com wrote:
[...]
There are only a few keyboard shortcuts that are really needed, so I
think a document that only explains these is better. I'll those to the
introductory docs.
A chart of the commands in the 'using leo as an outliner'
On Thu, Jun 4, 2009 at 11:09 PM, jkn jkn...@nicorp.f9.co.uk wrote:
A chart of the commands in the 'using leo as an outliner' section of
Chapter 2 (with default key bindings! - they could sensibly be added
to that section), together with those in the 'editing body text'
I have already added
On Jun 4, 9:35 pm, Ville M. Vainio vivai...@gmail.com wrote:
[...]
I have already added the default bindings to that section. I have some
stuff still not committed.
OK.
I don't really see a point in Chapter 3 Editing body text, it could
be replaced by Body editing is like in most
I don't really see a point in Chapter 3 Editing body text, it could
be replaced by Body editing is like in most mainstream text editors.
Where body editing deviates from that (it still does with some
commands), it should be treated as bug, not documented, IMHO ;-).
...continuing on the
Control-Shift-R does replace
Position on the tree to the highest level you want to search/replace.
It will operate on all nodes below.
ALT- replace selection then fine
F3 find next
Matt Wilkie wrote:
I don't really see a point in Chapter 3 Editing body text, it could
be
When you press Enter after entering the replacement text, Leo should find
and highlight the search text.
confirmed, this is what I see.
If you want to replace and find the next occurrence, press ALT- (alt +
minus)
When I press (alt + minus) the focus moves to the tree and collapses
the
Matt,
So sorry, was doing from memory: It's Ctrl-Minus, not Alt-Minus
Matt Wilkie wrote:
When you press Enter after entering the replacement text, Leo should find
and highlight the search text.
confirmed, this is what I see.
If you want to replace and find the next occurrence,
So sorry, was doing from memory: It's Ctrl-Minus, not Alt-Minus
aaah, that makes all the difference in the world! thanks :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group,
Thanks - I hadn't realised this configuration was possible. Anything
similar for the tree highlight?
The hack was to add FocusIn/Out methods to the leoQtBody class I doubt that
anything similar exists for the leoQtTree class.
Feel free to add a wish-list item if you like
On Wed, Jun 3, 2009 at 5:50 AM, jkn jkn...@nicorp.f9.co.uk wrote:
FYI, whilst having a look at the code (can't yet get the above
settings to work, but I'm just exploring at the moment) I found this
typo:
qtGui.py, line 5842:
def traceFocuse (self,eventType,obj):
should be
def
A couple of things which probably don't fall into the 'urgent or
annoying category', but nevertheless ...
- I've just done a full 'bzr checkout' and got revno 1990. But 'Help |
about Leo' still shows Leo 4.6 Beta 1, build 1.244, March 24, 2009'.
It would help bug reports etc. if this was
On Tue, Jun 2, 2009 at 4:57 AM, jkn jkn...@nicorp.f9.co.uk wrote:
A couple of things which probably don't fall into the 'urgent or
annoying category', but nevertheless ...
- I've just done a full 'bzr checkout' and got revno 1990. But 'Help |
about Leo' still shows Leo 4.6 Beta 1, build
On Jun 2, 2:25 pm, Edward K. Ream edream...@gmail.com wrote:
[...]
I use the following settings (in myLeoSettings.leo) to switch colors in the
body pane depending on focus:
@string selected-background-color = #fdf5f5
A kind of pink, for when the body has focus
@string
On Tue, Jun 2, 2009 at 10:33 AM, jkn jkn...@nicorp.f9.co.uk wrote:
I use the following settings (in myLeoSettings.leo) to switch colors in
the
body pane depending on focus:
@string selected-background-color = #fdf5f5
A kind of pink, for when the body has focus
@string
I am using 4.6.b1 so this list could be fairly useless by now
features or bugs on qt interface, windows
1. right click context menu on headlines requires first a double left
click to select and then a right click
2. context menu in 1. does not have heading controls like insert,
delete etc.
3.
edit:
6. the only way to expand a node is to click on the + symbol.
clicking adjacent to the heading name triggers selection
rather than expansion
On Jun 1, 11:22 am, rhh rod.h.holl...@gmail.com wrote:
I am using 4.6.b1 so this list could be fairly useless by now
features or bugs on qt
On Mon, Jun 1, 2009 at 9:22 PM, rhh rod.h.holl...@gmail.com wrote:
7. if I try to run start-ipython I get the error message no module
name ipy_qt.qti_pywidget
Launch leo by:
python launchLeo.py --gui=qt --ipython
Yes, this is a documentation glitch.
--
Ville M. Vainio
more:
9. open with settings not read from my_leo_settings or @openwith
directive
10. In general, it seems to ignore the my_leo_settings (thats an
overly broad first impression)
Rod
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
I think the start-up command is a better way to go. The mini-buffer
command would often fail for me anyway in the tk interface if I had
run some scripts prior to invoking it.
Thanks
On Jun 1, 11:28 am, Ville M. Vainio vivai...@gmail.com wrote:
On Mon, Jun 1, 2009 at 9:22 PM, rhh
On Mon, Jun 1, 2009 at 9:43 PM, rhh rod.h.holl...@gmail.com wrote:
I think the start-up command is a better way to go. The mini-buffer
command would often fail for me anyway in the tk interface if I had
run some scripts prior to invoking it.
Note that you still need to run alt+shift+I to
Ville,
I tried the command line load. It loads and i get an ileo command
prompt but
1. I try wb. and then command line completion in Ileo and nothing
happens ... ileo does not seem to work
2. right click context menus in Leo flash on the screen and disappear
in a fraction of a second.
Some
ok - i also associated the file with start-ipython
item 1 above (wb) now works - but is sluggish
item 2 above is still a problem
Rod
On Jun 1, 11:50 am, rhh rod.h.holl...@gmail.com wrote:
Ville,
I tried the command line load. It loads and i get an ileo command
prompt but
1. I try
On Mon, Jun 1, 2009 at 9:50 PM, rhh rod.h.holl...@gmail.com wrote:
1. I try wb. and then command line completion in Ileo and nothing
happens ... ileo does not seem to work
- Did you press Alt+Shift+I? (ok, saw that you did)
- Check that you have latest ipy_leo installed (from
bzr
more:
windows, tk interface, 4.6.1b
11. adjusting the window size with full width button bars throws up
tk errors. Sometimes a few of the buttons show up at the bottom of
the window, sometimes they are truncated at the left edge at the top
of the window. When they first load they can be
ok - I will try the recent version later this week. This was my first
foray into the 4.6 / qt release so I started with the 'official'
release.
By the way - in general, in bug testing, are bugs reported relative to
'official' releases or relative to continuously updated code?
Rod
On Jun 1,
35 matches
Mail list logo
