On Thu, Feb 12, 2009 at 6:45 PM, Christopher Barker
<[email protected]>wrote:

>
> I got the latest Leo from bzr, and tried it out on OS-X


Excellent.  Does the qt gui work?

>
> I'll have to mess with that, but out of the box, only ctrl works. Even
> though there are bindings listed in the menus for alt and alt+shift, they
> don't work.


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

The comment in the node says:

True (legacy): Translate control-only keys to command keys on the Mac.
False (recommended):  No translation.


> I'm surprised that TK didn't make more of of them work by default -- oh
> well.


This is only indirectly a Tk problem.  Leo can not determine, from the key
event itself, what key caused the event(!)  This is a giant hole in the Tk
api, but nobody in the Tk world seems to care.

As a result, Leo must create a separate binding for *all* keys that have a
entry in an @settings node.  So any bindings issues are due to settings in
@shortcuts nodes.

I'll be happy to add a node/tree for Mac-centric bindings if you contribute
it.

syntax coloring is only a start. Is there any other support?


What support would you like?

You've go [isearch] now, but it either is broken, or there was a
> misunderstanding of what it means


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.

Almost no editors get [indenting] right.


Debatable.  I prefer the present way with auto-indent following a colon.

We never argue about preferences in Leo, so I'll add the operation you
describe as option.  Another 3-day bug.


> 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.

There doesn't seem to be a setting that sets default tab width.  It appears
hard-code at -4.  It would be trivial to add such a setting if its lack
bothers you.

Edward

Reply via email to