Friday, November 4, 2016

LiClipse 3.2.1

The new LiClipse release is out.

The major updates were actually to PyDev, which has fixes such as a regression added on 5.3.0 where Ctrl+1 was not properly resolving symbols from dependent projects, code analysis on a particular case with PEP 448 (list unpacking), auto-indents async and await blocks, highlights async and await blocks and fixes an issue in the code completion using aliases.

It does have one new feature in which Ctrl+Shift+O (which fixes unresolved tokens by adding the needed imports) uses the improved sorting also used for the code-completion (so that tokens from the project appear before tokens from other projects, which in turn appear before tokens from the standard library). Also, the substring completion is now on by default (it may be turned off in the code-completion preferences).

Still, besides the updates to PyDev, the stock LiClipse themes were improved so that the current selected tab colors (on the active or inactive views) can be configured (selectedTabInitialBackground and selectedTabActiveInitialBackground in the theme preferences) and some colors were changed to have better defaults in a number of themes.


  1. I mostly develop (JavaScript apps) in CoffeeScript. Do you think autocompletion will be supported in the future ?

    1. Hi Mikkel,

      For this LiClipse would probably need an external library... do you know any library which is able to provide code-completion for CoffeScript?

    2. I was thinking more of a "general autocomplete" as seen in Atom editor.
      It doesn't really "know" CoffeeScript or any other language but simply use the words it sees in the project and base it's autocompletion on those.

    3. Oh, in that case, yes, such a form of autocompletion is expected to be supported in the future (but there's still no timeframe for it -- currently you have to resort to the regular Eclipse hippie completion, which only sees open files -- and may be activate with Alt+/).

    4. OK thanks looking forward to it !

  2. Hi Fabio,

    I do a lot of Python/Django and React/ES6 daily, but jshint slowness and incompatbility with JSX is driving me nuts.

    Was wondering if there was a way for me to disable jshint and set up eslint for my own setup?

    (I was the one that lodged issue 188. Can't seem to figure out when it was created via the tracker)

  3. Hi Twig,

    Well, you can disable jshint (as explained in, but you can't currently enable eslint.

    My plan is adding that support in LiClipse 3.6.0 (I'm doing a new release 3.5.0 this week and hope to add this for the next release, which should be around a month+ away).