Re: Future work wiki page

2013-11-20 Thread Corey O'Connor
On Mon, Nov 18, 2013 at 9:38 PM, Dmitry Ivanov wrote: > > > I have never been fond of this approach because: > > 1. Calling external programs is unreliable (having yet another > dependency is already problematic) > > Ideally we would have yi-plugin-clang depending on libclang and yi, not yi > dep

Re: Future work wiki page

2013-11-18 Thread Marc Weber
Excerpts from Dmitry Ivanov's message of Tue Nov 19 06:38:24 +0100 2013: > Also, regarding modularization: I see in git history that there was an > attempt to extract GUIs into separate packages. Does anyone remember why > that didn't work out? Ideally we'd replace C. :) C++ is considered "to c

Re: Future work wiki page

2013-11-18 Thread Dmitry Ivanov
> I have never been fond of this approach because: > 1. Calling external programs is unreliable (having yet another dependency is already problematic) Ideally we would have yi-plugin-clang depending on libclang and yi, not yi depending on libclang. This way users without libclang installed won'

Re: Future work wiki page

2013-11-17 Thread Jean-Philippe Bernardy
[massive snip] >> Is being available as a dynamic library (or embeddable as a static > >> library) sufficient to make it possible to write a Yi highlighting > >> "adapter" in the new scheme of things? This would of course require FFI, > >> and so would require the IO monad. > >> > > > > There is a

Re: Future work wiki page

2013-11-15 Thread Bardur Arantsson
On 2013-11-15 14:51, Jean-Philippe Bernardy wrote: > On Fri, Nov 15, 2013 at 1:01 PM, Bardur Arantsson wrote: > >> On 2013-11-15 11:34, Jean-Philippe Bernardy wrote: >>> On Fri, Nov 15, 2013 at 10:21 AM, Dmitry Ivanov >> wrote: >>> >> [--snip--] >> >> (I'm using C++ as an example here, but you co

Re: Future work wiki page

2013-11-15 Thread Jean-Philippe Bernardy
On Fri, Nov 15, 2013 at 1:01 PM, Bardur Arantsson wrote: > On 2013-11-15 11:34, Jean-Philippe Bernardy wrote: > > On Fri, Nov 15, 2013 at 10:21 AM, Dmitry Ivanov > wrote: > > > [--snip--] > > (I'm using C++ as an example here, but you could probably insert "any > horribly complicated-to-parse lan

Re: Future work wiki page

2013-11-15 Thread Bardur Arantsson
On 2013-11-15 11:34, Jean-Philippe Bernardy wrote: > On Fri, Nov 15, 2013 at 10:21 AM, Dmitry Ivanov wrote: > [--snip--] (I'm using C++ as an example here, but you could probably insert "any horribly complicated-to-parse language". Not that there are that many of them other than C++ that are pop

Re: Future work wiki page

2013-11-15 Thread Jean-Philippe Bernardy
On Fri, Nov 15, 2013 at 10:21 AM, Dmitry Ivanov wrote: > > JP, > > I'm sorry if my previous post sounded like an accusation, I understand > that we all have day jobs and other stuff to do and I'm not good at > expressing tone in English. > No offense taken! I hope I did not give the wrong impres

Re: Future work wiki page

2013-11-15 Thread Dmitry Ivanov
JP, I'm sorry if my previous post sounded like an accusation, I understand that we all have day jobs and other stuff to do and I'm not good at expressing tone in English. Regarding pygments example: imagine that user has to edit files in some non-trivial language and already has a parser for

Re: Future work wiki page

2013-11-15 Thread Jean-Philippe Bernardy
On Fri, Nov 15, 2013 at 5:28 AM, Dmitry Ivanov wrote: > Hello JP, > > Will this new highlighting scheme also be more modular? > I think the main flaw of the current scheme is not speed, but > maintainability. > It's so deeply integrated into yi that it's very hard to isolate, > understand and tes

Re: Future work wiki page

2013-11-14 Thread Dmitry Ivanov
Hello JP, Will this new highlighting scheme also be more modular? I think the main flaw of the current scheme is not speed, but maintainability. It's so deeply integrated into yi that it's very hard to isolate, understand and test it. It also uses Alex in non-obvious ways and overall is virtual

Re: Future work wiki page

2013-11-12 Thread MichaƂ J Gajda
Since we already use multithreaded runtime for Yi, why not just make highlighting available in parallel, with lower priority, as soon as it is available, but still allow full editing before that time? Using two threads on modern machines is much wiser than artificial serializing, as we do now.

Re: Future work wiki page

2013-11-12 Thread Marc Weber
There is another useful thing: You could introduce a setting: Highligt the first 20.000 lines/bytes by default only. This would do the right thing by default: You can still edit huge files, but small files would be colored. (Just yet another idea). If you open 1G files (for whatever reason) every

Re: Future work wiki page

2013-11-12 Thread Jean-Philippe Bernardy
I have devised a new syntax highlighting scheme. Benefits: much faster, and syntax can be derived directly from an existing context-free grammar. Tobias (cc'ed) is interested in integrating it into Yi as part of his Master's thesis. Cheers, JP. On Mon, Nov 11, 2013 at 8:24 PM, Marc Weber wrote

Re: Future work wiki page

2013-11-11 Thread Marc Weber
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.com http://groups.googl

Future work wiki page

2013-11-11 Thread Dmitry Ivanov
Hello All, I've written some thoughts about future work here: https://github.com/yi-editor/yi/wiki/Future-work It would be great if someone is interested in digging deeper into some of these points or just discussing yi's future. Regards, Dmitry -- -- Yi development mailing list yi-devel@go