Yo, Nikawhite.
What do you mean by vim-like navigator?
F3, F4 are hotkeys to navigate files in forwarding / backwarding.
--
___
enlightenment-devel mailing list
enlightenment-
I mean key bindings for navigation/edit into the EDC code entry.
For me vim-style navigation is a keys h,j,k,l for movement cursor
through text.
I need to think out more detailed. Will share concept later this month
(end of september maybe).
Also will be great to have ability to change keys and
On 09/02/2016 06:08 PM, Hermet Park wrote:
> Yo, Nikawhite.
>
> What do you mean by vim-like navigator?
>
> F3, F4 are hotkeys to navigate files in forwarding / backwarding.
I haven't tried building yet as eo usage is still quite annoying to
handle, was this release designed to work with efl
Good job trying to tackle it, but this is wrong.
This is not thread-safe and the Eo infrastructure should be. So
essentially, this optimisation is not allowed. You could maybe do a
cache per-thread, raster claims that __thread is actually quite alright
nowadays with GCC, I'm not sure, but this,
On Sep 2, 2016 07:15, "Tom Hacohen" wrote:
>
> Good job trying to tackle it, but this is wrong.
>
> This is not thread-safe and the Eo infrastructure should be. So
> essentially, this optimisation is not allowed. You could maybe do a
> cache per-thread, raster claims that __thread is actually quit
On 02/09/16 15:40, Cedric BAIL wrote:
> On Sep 2, 2016 07:15, "Tom Hacohen" wrote:
>>
>> Good job trying to tackle it, but this is wrong.
>>
>> This is not thread-safe and the Eo infrastructure should be. So
>> essentially, this optimisation is not allowed. You could maybe do a
>> cache per-thread
bu5hm4n pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=50030dc69346c209109c36bb41631b176c85b2c5
commit 50030dc69346c209109c36bb41631b176c85b2c5
Author: Marcel Hollerbach
Date: Thu Sep 1 21:49:31 2016 +0200
ibar: try to get a better min siz
On Fri, Sep 2, 2016 at 7:44 AM, Tom Hacohen wrote:
> On 02/09/16 15:40, Cedric BAIL wrote:
>> On Sep 2, 2016 07:15, "Tom Hacohen" wrote:
>>> Good job trying to tackle it, but this is wrong.
>>>
>>> This is not thread-safe and the Eo infrastructure should be. So
>>> essentially, this optimisation
cedric pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=05f05dde5c96b284c4fafd8457e6c3bb30c47c73
commit 05f05dde5c96b284c4fafd8457e6c3bb30c47c73
Author: Cedric Bail
Date: Fri Sep 2 09:59:09 2016 -0700
eo: protect efl_isa from thread race condition.
--
cedric pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=605fec91ee794c564582e9c5ea3a833b21a8c937
commit 605fec91ee794c564582e9c5ea3a833b21a8c937
Author: Cedric BAIL
Date: Wed Aug 31 14:12:02 2016 -0700
eo: improve speed of walking callback array by so
cedric pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=3ab60a15646630a9a76a0a6d437dc2132cae75fd
commit 3ab60a15646630a9a76a0a6d437dc2132cae75fd
Author: Cedric BAIL
Date: Wed Aug 31 17:15:35 2016 -0700
eo: store registered callbacks in an array instea
onefang Rejected wrote:
> On Thu, 01 Sep 2016 14:06:19 + Mike Blumenkrantz
> wrote:
>
>
>> how is this thread still active
>>
>
> Coz I'm finding Rasters attitude to EFL application developers is
> deplorable, and I'm having serious thoughts about dropping my
> involvement in EFL devel
On Wed, 31 Aug 2016 16:46:13 +0900 (KST) Hermet Park said:
> Hello everyone,
>
> I'm glad to announce Enventor 1.0 release.
awesome man! :) good work.
> Please see and enjoy it. :)
>
> Demo Video:
>https://youtu.be/lTLfr6knXrA
>
> And fyi, Enventor has an official about page that helps
On Fri, 02 Sep 2016 16:33:02 -0400 Jose Gonzalez said:
> onefang Rejected wrote:
> > On Thu, 01 Sep 2016 14:06:19 + Mike Blumenkrantz
> > wrote:
> >
> >
> >> how is this thread still active
> >>
> >
> > Coz I'm finding Rasters attitude to EFL application developers is
> > deplorable,
On Fri, 2 Sep 2016 15:15:07 +0100 Tom Hacohen said:
> Good job trying to tackle it, but this is wrong.
>
> This is not thread-safe and the Eo infrastructure should be. So
> essentially, this optimisation is not allowed. You could maybe do a
> cache per-thread, raster claims that __thread is ac
On Fri, 2 Sep 2016 09:53:25 -0700 Cedric BAIL said:
> On Fri, Sep 2, 2016 at 7:44 AM, Tom Hacohen wrote:
> > On 02/09/16 15:40, Cedric BAIL wrote:
> >> On Sep 2, 2016 07:15, "Tom Hacohen" wrote:
> >>> Good job trying to tackle it, but this is wrong.
> >>>
> >>> This is not thread-safe and the E
16 matches
Mail list logo
