- Pharo-dev - lists.pharo.org

Re: [Pharo-project] TextLint for Emacs & TextMate

by Lukas Renggli

> textmate > else this is nice to think about our texts. > The integration is good too. Yeah, the VM somehow doesn't work in headless mode on OS X. I have to try with a different one. > The rule Avoid using two or more continuous adjectives, be concise and clear. > is full of false positives related to conjunction use and in on by.... kinds of words Yeah, this rule and some other ones have too much false positives to be useful. This is due to a change I made yesterday that needs to be revisited. It affects the rules: - Avoid excess of adjectives - Avoid list of terms without comma - Avoid similar adjective synonyms - Avoid similar adverb synonyms - Use the serial comma Lukas > > based on > local variable > or dynamic > .... > > > Â Â Â Â â¢ existing virtual > Â Â Â Â â¢ addressed by > Â Â Â Â â¢ by such > Â Â Â Â â¢ adequate in > Â Â Â Â â¢ just giving > Â Â Â Â â¢ our previous > Â Â Â Â â¢ based on > Â Â Â Â â¢ Low level > Â Â Â Â â¢ level virtual > Â Â Â Â â¢ One key > Â Â Â Â â¢ on static > Â Â Â Â â¢ powerful reflective > Â Â Â Â â¢ fundamental level > Â Â Â Â â¢ it easy > > Â Â Â Â â¢ used in > Â Â Â Â â¢ based on > Â Â Â Â â¢ unrealistic in > Â Â Â Â â¢ variable transitive > Â Â Â Â â¢ here \ct{self > Â Â Â Â â¢ reachable by > Â Â Â Â â¢ it later > Â Â Â Â â¢ first class > Â Â Â Â â¢ leaked by > Â Â Â Â â¢ revocable one > Â Â Â Â â¢ one then > Â Â Â Â â¢ reachable by > Â Â Â Â â¢ given by > Â Â Â Â â¢ one or > Â Â Â Â â¢ working on > Â Â Â Â â¢ on its > Â Â Â Â â¢ its revocable > Â Â Â Â â¢ in particular > Â Â Â Â â¢ ruled out > Â Â Â Â â¢ supporting safer > Â Â Â Â â¢ how specific > Â Â Â Â â¢ involved in > Â Â Â Â â¢ special case > Â Â Â Â â¢ safe dynamic > Â Â Â Â â¢ solved in > Â Â Â Â â¢ single paper > Â Â Â Â â¢ in dynamic > Â Â Â Â â¢ or dynamic > Â Â Â Â â¢ presented early > Â Â Â Â â¢ defined on > Â Â Â Â â¢ up in > Â Â Â Â â¢ later in > Â Â Â Â â¢ defined in > Â Â Â Â â¢ one special > Â Â Â Â â¢ controllable proxy > Â Â Â Â â¢ proxy on > Â Â Â Â â¢ available in > Â Â Â Â â¢ class based > Â Â Â Â â¢ In particular > Â Â Â Â â¢ defined in > Â Â Â Â â¢ in general > Â Â Â Â â¢ very similar > Â Â Â Â â¢ different on > Â Â Â Â â¢ In particular > Â Â Â Â â¢ done in > Â Â Â Â â¢ recursive following > Â Â Â Â â¢ used by > Â Â Â Â â¢ its normal > Â Â Â Â â¢ knowing it > Â Â Â Â â¢ self} or > Â Â Â Â â¢ in various > Â Â Â Â â¢ public} part > Â Â Â Â â¢ accessible only > Â Â Â Â â¢ private} part > Â Â Â Â â¢ self} in > Â Â Â Â â¢ in traditional > Â Â Â Â â¢ self} in > Â Â Â Â â¢ divided in > Â Â Â Â â¢ reflected in > Â Â Â Â â¢ Other higher > Â Â Â Â â¢ higher level > Â Â Â Â â¢ on inactive > Â Â Â Â â¢ presented model > Â Â Â Â â¢ based on > Â Â Â Â â¢ its own > Â Â Â Â â¢ own class > Â Â Â Â â¢ class or > Â Â Â Â â¢ known by > Â Â Â Â â¢ separated in > Â Â Â Â â¢ then on > Â Â Â Â â¢ In particular > Â Â Â Â â¢ abstract class > Â Â Â Â â¢ used by > Â Â Â Â â¢ self new > Â Â Â Â â¢ pointed by > Â Â Â Â â¢ on his > Â Â Â Â â¢ his own > Â Â Â Â â¢ its own > Â Â Â Â â¢ own class > Â Â Â Â â¢ applied on > Â Â Â Â â¢ same class > Â Â Â Â â¢ first specific > Â Â Â Â â¢ done by > Â Â Â Â â¢ by on > Â Â Â Â â¢ only supporting > Â Â Â Â â¢ present how > Â Â Â Â â¢ class such > Â Â Â Â â¢ based on > Â Â Â Â â¢ previous model > Â Â Â Â â¢ previous paper > Â Â Â Â â¢ set up > Â Â Â Â â¢ interesting in > Â Â Â Â â¢ Even complex > Â Â Â Â â¢ shared in > Â Â Â Â â¢ only revocable > Â Â Â Â â¢ Our revocable > Â Â Â Â â¢ based on > Â Â Â Â â¢ class named > Â Â Â Â â¢ old trick > Â Â Â Â â¢ class named > Â Â Â Â â¢ by revocable > Â Â Â Â â¢ only revocable > Â Â Â Â â¢ presented above > Â Â Â Â â¢ above in > Â Â Â Â â¢ class named > Â Â Â Â â¢ In particular > Â Â Â Â â¢ new one > Â Â Â Â â¢ in \secref{nuts > Â Â Â Â â¢ operational semantic > Â Â Â Â â¢ temporary variable > Â Â Â Â â¢ same semantic > Â Â Â Â â¢ semantic such > Â Â Â Â â¢ such it > Â Â Â Â â¢ done in > Â Â Â Â â¢ specific semantic > Â Â Â Â â¢ presented how > Â Â Â Â â¢ modified it > Â Â Â Â â¢ it so > Â Â Â Â â¢ Difficult Case > Â Â Â Â â¢ Certain meta > Â Â Â Â â¢ analyzed case > Â Â Â Â â¢ case by > Â Â Â Â â¢ by case > Â Â Â Â â¢ complex in > Â Â Â Â â¢ first class > Â Â Â Â â¢ first class > Â Â Â Â â¢ self inline > Â Â Â Â â¢ test in > Â Â Â Â â¢ in previous > Â Â Â Â â¢ variable by > Â Â Â Â â¢ given by > Â Â Â Â â¢ our previous > Â Â Â Â â¢ slow down > Â Â Â Â â¢ down normal > Â Â Â Â â¢ our modified > Â Â Â Â â¢ normal virtual > Â Â Â Â â¢ on our > Â Â Â Â â¢ exact same > Â Â Â Â â¢ on our > Â Â Â Â â¢ our special > Â Â Â Â â¢ create one > Â Â Â Â â¢ wrapped in > Â Â Â Â â¢ new revocable > Â Â Â Â â¢ dependent how > Â Â Â Â â¢ quite large > Â Â Â Â â¢ very naive > Â Â Â Â â¢ first class > Â Â Â Â â¢ slow down > Â Â Â Â â¢ on static > Â Â Â Â â¢ compact\footnote{In > Â Â Â Â â¢ compact class > Â Â Â Â â¢ revocable just > Â Â Â Â â¢ our previous > Â Â Â Â â¢ our previous > Â Â Â Â â¢ previous paper > Â Â Â Â â¢ paper about > Â Â Â Â â¢ model developed > Â Â Â Â â¢ developed here > Â Â Â Â â¢ different on > Â Â Â Â â¢ new model > Â Â Â Â â¢ previous model > Â Â Â Â â¢ only designed > Â Â Â Â â¢ defined on > Â Â Â Â â¢ only one > Â Â Â Â â¢ done by > Â Â Â Â â¢ multiple compatible > Â Â Â Â â¢ only revocable > Â Â Â Â â¢ planned in > Â Â Â Â â¢ in advance > Â Â Â Â â¢ current model > Â Â Â Â â¢ current model > Â Â Â Â â¢ how different > Â Â Â Â â¢ current model > Â Â Â Â â¢ In particular > Â Â Â Â â¢ similar one > Â Â Â Â â¢ used in > Â Â Â Â â¢ by supporting > Â Â Â Â â¢ low level > Â Â Â Â â¢ secure dynamic > Â Â Â Â â¢ presented in > Â Â Â Â â¢ present here > Â Â Â Â â¢ well known > Â Â Â Â â¢ standard dynamic > Â Â Â Â â¢ defined only > Â Â Â Â â¢ trapped by > Â Â Â Â â¢ meta-level > Â Â Â Â â¢ close in > Â Â Â Â â¢ passed through > Â Â Â Â â¢ through it > Â Â Â Â â¢ based on > Â Â Â Â â¢ on its > Â Â Â Â â¢ its different > Â Â Â Â â¢ done inside > Â Â Â Â â¢ hidden or > Â Â Â Â â¢ based on > Â Â Â Â â¢ model supporting > Â Â Â Â â¢ on its > Â Â Â Â â¢ In our > Â Â Â Â â¢ on internal > Â Â Â Â â¢ late binding > Â Â Â Â â¢ meta-level > Â Â Â Â â¢ separate reflective > Â Â Â Â â¢ base-level > Â Â Â Â â¢ reflective base > Â Â Â Â â¢ base-level > Â Â Â Â â¢ protected by > Â Â Â Â â¢ visible outside > Â Â Â Â â¢ in Noble > Â Â Â Â â¢ solved by > Â Â Â Â â¢ by dynamic > Â Â Â Â â¢ one solved > Â Â Â Â â¢ solved by > Â Â Â Â â¢ dependent behavioral > Â Â Â Â â¢ or disabled > Â Â Â Â â¢ disabled based > Â Â Â Â â¢ based on > Â Â Â Â â¢ presented in > Â Â Â Â â¢ defined by > Â Â Â Â â¢ very general > Â Â Â Â â¢ organized in > Â Â Â Â â¢ only concerned > Â Â Â Â â¢ self pseudo > Â Â Â Â â¢ pseudo-variable > Â Â Â Â â¢ pseudo-variable > Â Â Â Â â¢ our dynamic > Â Â Â Â â¢ In particular > Â Â Â Â â¢ or immutable > Â Â Â Â â¢ first class > Â Â Â Â â¢ validated our > Â Â Â Â â¢ just in > Â Â Â Â â¢ supported by > Â Â Â Â â¢ like dynamic > Â Â Â Â â¢ private in > Â Â Â Â â¢ so only > Â Â Â Â â¢ only local > Â Â Â Â â¢ local or > Â Â Â Â â¢ or inherited > Â Â Â Â â¢ base our > Â Â Â Â â¢ model used > Â Â Â Â â¢ used by > Â Â Â Â â¢ like dynamic > Â Â Â Â â¢ or class > Â Â Â Â â¢ used by > Â Â Â Â â¢ additional static > Â Â Â Â â¢ used by > Â Â Â Â â¢ listed in > Â Â Â Â â¢ specified out > Â Â Â Â â¢ out by > Â Â Â Â â¢ bound in > Â Â Â Â â¢ corresponding binding > Â Â Â Â â¢ actual class > Â Â Â Â â¢ class in > Â Â Â Â â¢ local variable > Â Â Â Â â¢ existent variable > > > On Sep 6, 2011, at 10:51 AM, Damien Cassou wrote: > >> On Tue, Sep 6, 2011 at 10:45 AM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> how do you get the selection in the editor when you click on the reported link? >> >> what editor are you using? With Emacs it should be the case by default >> (look at the screencast) >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Lambdas are relegated to relative obscurity until Java makes them >> popular by not having them." James Iry >> > > > -- Lukas Renggli www.lukas-renggli.ch

Sept. 6, 2011

[Pharo-project] [update 1.4] #14121

by Marcus Denker

14121 ----- Issue 4757: remove #StandardToolSet from privCleanUnloadMethods http://code.google.com/p/pharo/issues/detail?id=4757 Issue 4724: polymorph fixes http://code.google.com/p/pharo/issues/detail?id=4724 Issue 4643: Inspector>>fieldListMenu: aMenu http://code.google.com/p/pharo/issues/detail?id=4643 -- Marcus Denker -- http://marcusdenker.de

Sept. 6, 2011

Re: [Pharo-project] TextLint for Emacs & TextMate

by StÃ©phane Ducasse

textmate else this is nice to think about our texts. The integration is good too. The rule Avoid using two or more continuous adjectives, be concise and clear. is full of false positives related to conjunction use and in on by.... kinds of words based on local variable or dynamic .... â¢ existing virtual â¢ addressed by â¢ by such â¢ adequate in â¢ just giving â¢ our previous â¢ based on â¢ Low level â¢ level virtual â¢ One key â¢ on static â¢ powerful reflective â¢ fundamental level â¢ it easy â¢ used in â¢ based on â¢ unrealistic in â¢ variable transitive â¢ here \ct{self â¢ reachable by â¢ it later â¢ first class â¢ leaked by â¢ revocable one â¢ one then â¢ reachable by â¢ given by â¢ one or â¢ working on â¢ on its â¢ its revocable â¢ in particular â¢ ruled out â¢ supporting safer â¢ how specific â¢ involved in â¢ special case â¢ safe dynamic â¢ solved in â¢ single paper â¢ in dynamic â¢ or dynamic â¢ presented early â¢ defined on â¢ up in â¢ later in â¢ defined in â¢ one special â¢ controllable proxy â¢ proxy on â¢ available in â¢ class based â¢ In particular â¢ defined in â¢ in general â¢ very similar â¢ different on â¢ In particular â¢ done in â¢ recursive following â¢ used by â¢ its normal â¢ knowing it â¢ self} or â¢ in various â¢ public} part â¢ accessible only â¢ private} part â¢ self} in â¢ in traditional â¢ self} in â¢ divided in â¢ reflected in â¢ Other higher â¢ higher level â¢ on inactive â¢ presented model â¢ based on â¢ its own â¢ own class â¢ class or â¢ known by â¢ separated in â¢ then on â¢ In particular â¢ abstract class â¢ used by â¢ self new â¢ pointed by â¢ on his â¢ his own â¢ its own â¢ own class â¢ applied on â¢ same class â¢ first specific â¢ done by â¢ by on â¢ only supporting â¢ present how â¢ class such â¢ based on â¢ previous model â¢ previous paper â¢ set up â¢ interesting in â¢ Even complex â¢ shared in â¢ only revocable â¢ Our revocable â¢ based on â¢ class named â¢ old trick â¢ class named â¢ by revocable â¢ only revocable â¢ presented above â¢ above in â¢ class named â¢ In particular â¢ new one â¢ in \secref{nuts â¢ operational semantic â¢ temporary variable â¢ same semantic â¢ semantic such â¢ such it â¢ done in â¢ specific semantic â¢ presented how â¢ modified it â¢ it so â¢ Difficult Case â¢ Certain meta â¢ analyzed case â¢ case by â¢ by case â¢ complex in â¢ first class â¢ first class â¢ self inline â¢ test in â¢ in previous â¢ variable by â¢ given by â¢ our previous â¢ slow down â¢ down normal â¢ our modified â¢ normal virtual â¢ on our â¢ exact same â¢ on our â¢ our special â¢ create one â¢ wrapped in â¢ new revocable â¢ dependent how â¢ quite large â¢ very naive â¢ first class â¢ slow down â¢ on static â¢ compact\footnote{In â¢ compact class â¢ revocable just â¢ our previous â¢ our previous â¢ previous paper â¢ paper about â¢ model developed â¢ developed here â¢ different on â¢ new model â¢ previous model â¢ only designed â¢ defined on â¢ only one â¢ done by â¢ multiple compatible â¢ only revocable â¢ planned in â¢ in advance â¢ current model â¢ current model â¢ how different â¢ current model â¢ In particular â¢ similar one â¢ used in â¢ by supporting â¢ low level â¢ secure dynamic â¢ presented in â¢ present here â¢ well known â¢ standard dynamic â¢ defined only â¢ trapped by â¢ meta-level â¢ close in â¢ passed through â¢ through it â¢ based on â¢ on its â¢ its different â¢ done inside â¢ hidden or â¢ based on â¢ model supporting â¢ on its â¢ In our â¢ on internal â¢ late binding â¢ meta-level â¢ separate reflective â¢ base-level â¢ reflective base â¢ base-level â¢ protected by â¢ visible outside â¢ in Noble â¢ solved by â¢ by dynamic â¢ one solved â¢ solved by â¢ dependent behavioral â¢ or disabled â¢ disabled based â¢ based on â¢ presented in â¢ defined by â¢ very general â¢ organized in â¢ only concerned â¢ self pseudo â¢ pseudo-variable â¢ pseudo-variable â¢ our dynamic â¢ In particular â¢ or immutable â¢ first class â¢ validated our â¢ just in â¢ supported by â¢ like dynamic â¢ private in â¢ so only â¢ only local â¢ local or â¢ or inherited â¢ base our â¢ model used â¢ used by â¢ like dynamic â¢ or class â¢ used by â¢ additional static â¢ used by â¢ listed in â¢ specified out â¢ out by â¢ bound in â¢ corresponding binding â¢ actual class â¢ class in â¢ local variable â¢ existent variable On Sep 6, 2011, at 10:51 AM, Damien Cassou wrote: > On Tue, Sep 6, 2011 at 10:45 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> how do you get the selection in the editor when you click on the reported link? > > what editor are you using? With Emacs it should be the case by default > (look at the screencast) > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry >

Sept. 6, 2011

Re: [Pharo-project] TextLint for Emacs & TextMate

by Damien Cassou

On Tue, Sep 6, 2011 at 10:45 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > how do you get the selection in the editor when you click on the reported link? what editor are you using? With Emacs it should be the case by default (look at the screencast) -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 6, 2011

Re: [Pharo-project] TextLint for Emacs & TextMate

by Damien Cassou

On Tue, Sep 6, 2011 at 10:43 AM, Stefan Marr <pharo(a)stefan-marr.de> wrote: > I noticed that the VM/image is coming up in the background when activated. > Could the VM just be run in headless mode, or are there any technical issues that prevent that at the moment? in Emacs on Linux the VM runs headless. I think Lukas had some problems to make the VM run headless on Mac OS X. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 6, 2011

[Pharo-project] [update 1.3] #13301

by Marcus Denker

13301 ----- Issue 4748: The test for allocating 1GB crashed the current cog VMs http://code.google.com/p/pharo/issues/detail?id=4748 Issue 4643: Inspector>>fieldListMenu: aMenu http://code.google.com/p/pharo/issues/detail?id=4643 -- Marcus Denker -- http://marcusdenker.de

Sept. 6, 2011

Re: [Pharo-project] TextLint for Emacs & TextMate

by StÃ©phane Ducasse

how do you get the selection in the editor when you click on the reported link? On Sep 6, 2011, at 10:18 AM, Damien Cassou wrote: > On Tue, Sep 6, 2011 at 9:52 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> I'm how can I get it running? > > https://github.com/DamienCassou/textlint#readme > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry >

Sept. 6, 2011

Re: [Pharo-project] TextLint for Emacs & TextMate

by Stefan Marr

Hi: On 06 Sep 2011, at 09:23, Damien Cassou wrote: > Integration within TextMate: http://www.youtube.com/watch?v=SrG29zWHqkk > - TextMate (https://github.com/DamienCassou/textlint) > > I'm also very interested in feedback, code, and whatever can make the > whole thing better. Very nice, thanks. Now I will hopefully remember to use it to fix the most obvious things in my English. I noticed that the VM/image is coming up in the background when activated. Could the VM just be run in headless mode, or are there any technical issues that prevent that at the moment? Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Sept. 6, 2011

Re: [Pharo-project] Some bugs

by Igor Stasenko

On 5 September 2011 18:02, Lukas Renggli <renggli(a)gmail.com> wrote: > Even if you have a AST debugger you still need at some point a bytecode to > AST (or source) mapping, because otherwise you cannot just break into a > debugger at a random point in the code. I imagine this jump from bytecode to > AST interpretation quite difficult; likely you still need a full bytecode > stepper to find a position where you can jump into the AST interpreter. > It depends, whether you able (or want to) insert a breakpoint which are inside a single AST node (for AST node which contains multiple bytecode), or allow to halt only at AST nodes boundaries. Consider C debugger - it has to deal with same situation: a single C statement could contain multiple machine code instructions, but when you stepping over that statement, you are not stepping over single machine code instruction(s) at a time, you stepping over single C statement. In some cases, stepping over single machine instruction is useful (especially when you dealing with generated machine code ;) but when you debugging a normal code, you don't need that, which means that if you have an AST -> bytecode ranges mapping you know the ranges and stepping points and don't have to interpret each bytecode separately, but intead just interpret what AST node does. > Lukas > > On Monday, 5 September 2011, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: >> We were thinking with marcus that using byte code to go back to sources >> code is >> broken by essence and that using an AST is the way to go. >> Now we would need a good AST-based interpreter to start with. >> >>> 2011/9/5 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> BTW mike roberts is building a tool to be able to understand and fix the >>>> code range of the debugger hilighting. >>>> Probably your bug is also related to the closure introduction. >>>> >>>> Now the abstraction used is so low level that this is a pain and >>>> fragile. >>>> Ideally using an AST would be much better but this is for the future. >>>> >>>> Stef >>>> >>> >>> Stef, >>> If you are saying that implementation is not crystal clear, I can only >>> agree with you. >>> Eliot did avoid a full rewrite (I guess he took the shortest path to >>> make the available implementation work with closures), and this design >>> decision can be questioned indeed. >>> >>> But speaking of abstraction level by itself, I don't understand your >>> sentence. >>> To me, the abstraction is at the correct level. >>> The Debugger has to map the low level execution machinery >>> (Context/program counter/CompiledMethod/byteCodes) to high level >>> specification visible to the user (source code). >>> The Debugger does so by mapping bytecodes to source ranges via AST, no >>> more, no less. >>> >>> In case of inlined blocks, there are more instructions on the bytecode >>> side than messages sent on the AST side, just to make the problem a >>> bit more complex, so maybe there are more intelligent way to address >>> the mapping problem (maybe you mean via an intermediate transformation >>> of AST), but you'll have to explain this a bit deeper. >>> >>> Nicolas >>> >>>> >>>> On Sep 5, 2011, at 9:07 AM, Andrea BrÃ¼hlmann wrote: >>>> >>>>> Hello Stef, >>>>> >>>>> I appreciate the work of the pharo community! We will continue >>>>> reporting bugs and submit fixes that >>>>> we made. Of course I do not expect anyone to fix all reported bugs, but >>>>> there are issues like 4694 >>>>> (debugger) where we really need your help. Other issues like the buggy >>>>> code completion can be >>>>> workarounded by me by disabling code completion ;-) >>>>> >>>>> So thanks for the welcome and I am looking forward to having 4694 >>>>> fixed! >>>>> >>>>> Andrea >>>>> >>>>> >>>>> >>>>> >>>>> StÃ©phane Ducasse schrieb: >>>>>> Thanks andrea >>>>>> Welcome to the pharo mailing-list and community. Now I think that this >>>>>> is important that inside netstyle you also consider that if pharo is >>>>>> important for you (which I imagine) that you should also contribute. Bug >>>>>> reporting is already a contribution. Â Pharo is an open-source software >>>>>> mainly supported by the free time of people, people that are often do not >>>>>> earning their money from their pharo work (I thank them for all that). I >>>>>> also understand that people can get frustrated by changes but what can we >>>>>> do? >>>>>> May be people can gather and check the fixes that are important to fix >>>>>> but we do not have the force to maintain. >>>>>> Imagine well that we have one engineer full time since 8 months. Stef >>>>>> On Aug 23, 2011, at 8:54 AM, Andrea BrÃ¼hlmann wrote: >>>>>>> Hello, >>>>>>> >>>>>>> I reported some bugs on the issue tracker and hope you can help me >>>>>>> with them! >>>>>>> >>>>>>> >>>>>>> 4681: Accepting with the enter key does not work >>>>>>> Â Â http://code.google.com/p/pharo/issues/detail?id=4681 >>>>>>> >>>>>>> 4682: Code completion makes strange cursor placements and too many >>>>>>> spaces >>>>>>> Â Â http://code.google.com/p/pharo/issues/detail?id=4682 >>>>>>> >>>>>>> 4683: Code completion breaks some search fields (errors during >>>>>>> typing) >>>>>>> Â Â http://code.google.com/p/pharo/issues/detail?id=4683 >>>>>>> >>>>>>> 4684: Missing ctrl+w (methodNamesContainingIt:) >>>>>>> Â Â http://code.google.com/p/pharo/issues/detail?id=4684 >>>>>>> >>>>>>> 4685: Merge dialog: cannot resolve conflict with removed method >>>>>> > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Best regards, Igor Stasenko.

Sept. 6, 2011

Re: [Pharo-project] TextLint for Emacs & TextMate

by Damien Cassou

On Tue, Sep 6, 2011 at 9:52 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I'm how can I get it running? https://github.com/DamienCassou/textlint#readme -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 6, 2011