Edward K. Ream wrote:
Excellent. Does the qt gui work?
I have no idea -- I've never used PyQT.
The bindings work on Ubuntu and Windows, but not necessarily on MacOS
because of different key names and usages. Have you tried setting:
@bool swap_mac_keys = True
OK I've tried this, and it works OK.
However, to do it, I went to the help menu, and selected "Open
LeoSetting.leo"
which gave me a nice tree of settings, but I couldn't find
"swap_mac_keys". I poked around, and didn't find it, I did a search for
"swap" and didn't find it. In fact, what I did do is open the file in
another editor, search for "swap", change it save it and re-start leo.
I don't know if that's 'cause i just don't know how to use leo -- but
it's really making think that this is a major leap from plain old text
file editing!
I'll be happy to add a node/tree for Mac-centric bindings if you
contribute it.
we'll see -- I need to convince my self that this outlining way of
working is worth it...But it's nice to know that Mac support is probably
only as far away as a Mac user willing to help a bit.
syntax coloring is only a start. Is there any other support?
What support would you like?
well, at least good indenting, etc, and hopefully a way to runt eh code,
or built it or whatever. Also assorted shortcuts, I write LaTeX a fair
bit, and it's nice to have help with that.
It works using the qt gui. There are focus problems with the tk gui
that cause the minibuffer to reset to a single character. I had
forgotten about this in the recent flurry of activity. I'll declare
this a 3-day bug.
fair enough.
Almost no editors get [indenting] right.
Debatable. I prefer the present way with auto-indent following a colon.
Have you ever tried it the way I suggest? Probably not -- not many
editors do it.
We never argue about preferences in Leo, so I'll add the operation you
describe as option. Another 3-day bug.
Give it a try then, I think you'll be surprised at how much nicer it is!
Whether an indentation level is a tab or n spaces should be set-able
depending on the type of file and/or personal preference.
It is.
@tabwidth 8 # hard tabs, 8 characters wide.
@tabwidth -4 # tab with 4 spaces.
that looks to be leo-wide -- what if you want different setting for
different kinds of files? That's another emacs-ism I really like -- the
idea of major-modes and minor modes. Major modes, in particular make it
easy to have the editor behave quite differently depending on what kind
of file you are editing.
There doesn't seem to be a setting that sets default tab width. It
appears hard-code at -4.
So what does @tabwidth set?
By the way, a couple TK on OS_C notes:
moving the sashes between windows is really "flashy" -- a bit hard to
describe.
The tree is all messed up while scrolling.
Also, some weirdnesses with line numbers. I'm editing a python file.
There is a syntax error on a line.
In the editing window, it's line 21
when I run it from leo, the error is reported as being at line 24
when I run it from the command line, it's reported as line 19
This is all quite confusing.
One other thing, for a newbie:
I opened a python file, edited it, saved it, and now I have no idea how
to get the edited version! It saved a workbook.leo file, but didn't
touch the python file.
It seems you can't quite use leo as "just a text editor" out of the box.
Still on the fence here.....
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
[email protected]
