Re: new pre-release

  • From: "Liviu Andronic" <landronimirc@xxxxxxxxx>
  • To: emelfm2@xxxxxxxxxxxxx
  • Date: Wed, 1 Oct 2008 09:01:39 +0200

On Sun, Sep 28, 2008 at 12:21 PM,  <tpgww@xxxxxxxxxxx> wrote:
>> Another issue with the pre-release is that I am unable to define
>> keyboard bindings; these are simply not captured by emel. Sometimes
>> I'm even able to type in "aasdf", instead of the binding. NOTE: I have
>> just installed the latest pre-release, and this issue seems gone. I
>> still can however not use the defined bindings.
> Can you please describe an example or 2 of exactly what key(s) you've bound, 
> and in what category, and what happens, if anything, when the key is pressed.
>
In the latest pre-release, this issue seems no longer present. It
concerned `panes'. I failed to make any use of `<ctrl>+g 2' and
decided to set my own <ctrl><alt>2. With the first pre-release, I
think, emel captured nothing if I used modifiers. If I tried to use
simple letters it either captured it, or allowed me to freely type in.
Again, I no longer see capturing issues in the subsequent releases.

I did notice more important issues in the latest pre-release.
1. The focus does not follow the selection when I switch the panes
using the mouse (perhaps relevant, I use `bold name header' as
indicator of active pane). Easiest test: start emel, click with the
mouse on a file in the second pane. Assuming that you have a folder
selected in the first pane, hit enter and you will see the folder open
up (even though the `active selection' was in the `passive pane').
Switching correctly the focus does work with <tab>
2. There is no mouse c-menu. When I <right-click> on any folder or
file, I get absolutely nothing. I'm using `new' type of config, but
noticed the same problems using a fresh config file. If relevant, I'm
not using windows right-click behaviour.
3. The output pane c-menu displays the standard GTK+ widget
`copy/paste' menu. The usual emel menu is gone.

There may be other issues, but right now I cannot go into extensive debugging.


>  and INSTALL
> No mention there, ATM.
>
Oh, since INSTALL contains a somewhat exhaustive list of possible emel
dependencies, I thought it would be best to keep it up-to-date, ..


>  I would also suggest to include
>> on the home page [2] the same information about the dependencies as
>> that contained in INSTALL.
> Now updated a bit.
.. and to reuse the information on the Web site. The home page is a
bit scarce on information on optional dependencies.

Regards,
Liviu


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: