New release of Leksah
jnf at arcor.de
Wed Jul 22 16:05:26 EDT 2009
> Some minor problems that I've found so far:
> • the cross [x] buttons on tabs are almost invisible (don't
New: With version 0.6 for a pleasant visual appearance, you have
or append the .gtkrc-2.0 file from the Leksah data folder or
data folder in Leksah sources to your home folder. (Manual 7)
> • the [X] button on the toolbar behaves in a counterintuitive
way IMO (I
> expected it to close source editor tabs not
> Is it really needed?
Well we have made a concept, were you are basically free to
every part of the Leksah window. So you are free to close every
When I work this is my rescue:
In Leksah there may be an active pane. The name of this
pane is displayed in the second compartment from the left
side in the status bar. Some actions like moving, splitting,
closing panes or finding or replacing items in a text buffer
act on the current pane, so check the display in the status
bar to see if the pane you want to act on, is really the active
> • name completion popup sometimes goes beyond the bottom edge
> • debugging doesn't work if ~/.cabal/bin is not in the path -
> Cannot find the program 'ghc' at 'leksahecho' or on the
path" (does it
> mean that it can't find leksahecho?)
True. Not shure what it is really searching, but it needs to
> • does importing some module need its package to be specified
> dependencies first? Would it be possible to automatically add
> dependencies if I wanted to use something from it?
The import helper just looks in imported packages, so if you
package import, you have to fix it manually. It would be an
feature for the future.
> • adding imports based on errors from log doesn't seem to work
> for "src/Main.hs:22:16: Not in scope: `Data.Graph.buildG'" if
> /add import/ I get "Identifier Grap not found in imported
This may be: The metadata collector has a problem parsing your
the metadata is not up to date. So try to click on "Update
it stilll don't work try to look at the Metadata collection
the manual, and try to report the original error.
> • adding dependencies from packages installed by cabal doesn't
> work: "Setup: At least the following dependencies are missing:
> >=22.214.171.124", while doing "~/.cabal/bin/cabal configure" in the
> directory runs normally. I have parsec installed in my home
This is because cabal install uses the per user database of
packages, while the default is the machine database. So you have
--user to the ConfigFlags in Package / Package Flags.
> Out of these problems the last one is the most important as it
> me from using my locally-installed packages in Leksah.
So, the last one was easy.
> Let me know if I could be of any assistance.
Thank you for testing and taking the time to write it down.
can start a FAQ page on the Wiki.
More information about the Leksah