Re: Future work wiki page

and nobody has started work on such !? :-) I think this is very much off-topic. Does this make sense at all? Does anybody of you know any such attempt ? I mean C++ started as preprocessor, too. Marc Weber -- -- Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/y

Re: Future work wiki page

speedup could matter - I'd imagine such behaviour to be smarter than having to disable syntax for large files. Marc Weber -- -- Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel --- You received this message because you are subscribed to the G

Re: Future work wiki page

Feedback about switching off syntax. I'd say you should evaluate a different design: First first render without syntax, wait for the parser to provide syntax & color info, then redraw with highlighting. Marc Weber -- -- Yi development mailing list yi-devel@googlegroups

Re: Towards removing the mutually recursive modules in yi

oth. Usually forking, notifying, starting work, posting updates is best what you can do. Marc Weber -- -- Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel --- You received this message because you are subscribed to the Google Groups "yi

Re: Re-thinking bootstrapping yi

a) cabal compiling twice: Yes, I dream about cabal building debug and non debug versions in parallel as well b) compile time rest: yesod is using ghci interpreter to speed up recompilation. Whether this way is usable for a console editor I don't know. Consider this being my thoughts only

Re: Starting a minimalist fork at https://github.com/ijt/yi

p configure --flags "-pango -cocoa -gtk" and the like. Marc Weber -- Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel