On Sat, Feb 7, 2009 at 6:42 AM, Александър Л. Димитров <[email protected]> wrote: > Thus spoke Jean-Philippe Bernardy: >> I'd rather stay "neutral". Also I have long dreamed of "better" keybindings >> that would be the default for Yi, picking vim as default feels like giving up >> on this. Plus, it should be really easy to create a yi-vim if you want. > > I second that. I'm a heavy Vim-user, but I think yi should stay out of holy > wars > and just play dumb until the user tells it which side they're on. > >> > * minibuffer >> > - minibuffer text should be simplified: drop all the haskell char >> > quotes and list brackets >> >> What do you mean? > > I think the problem here is that what we're currently showing in the > minibuffer > is essentially what the Show instance for the respective data types does. Let > me > elaborate: Say, I'm in Vim, and there's a great many files in my working dir. > I > will try to open one with :e and then hit tab. This is what I get: > > ---------- > ~ > ~ > [No Name] > :e > Album.hs Common.hs Group.hs Tag.hs User.hs > Artist.hs Event.hs Library.hs Tasteometer.hs Venue.hs > Auth.hs Geo.hs Playlist.hs Track.hs > :e > --------- > > I do the same thing in yi: > > --------- > ~ > ~ > - *scratch* L1 C0 0% fundamental 0 > :e > Matches: > ["Album.hs","Geo.hs","Track.hs","Venue.hs","Common.hs","Tag.hs","Playlist.hs"," > --------- > > And I don't even get the full list of files! This has been bugging me for a > while, but university work has prevented me so far from working more on yi. > >> > * C-z out of vty tends to leave the terminal in white on cyan? >> >> yep, but not consistently. > > Isn't this fixed in the darcs head, along with the complaint that quitting yi > doesn't clean up the console window (i.e. hides what has been on the console > before launching yi)? It Works For Me… > >> > Probably the vim mode is better, but the emacs one is still far from >> > the production quality of Emacs. >> >> I have implemented all features I need... If people wish to improve I'd >> be glad to help, but I have little motivation to implement stuff I don't >> need. >> Of course you can also try to convince me that I need more features :) > > What's more, obscure editing functions in both Vim and Emacs usually have even > obscurer corner cases, which only the heavy user will be able to implement > correctly, because you have to know them by heart :-). Of course, yi could > strive to be more consistent, as IMHO both Vim and Emacs have a great many > misfeatures. > > While we're on topic, let me ask another more theoretical question/thought > about/on yi: > > Currently, devising highlighting schemes for new languages is a bit tedious. > One > has to create a couple of files, and I haven't yet found good documentation on > how to do so, and what are good practices. It's been a while since I've tried > doing something in that direction, so I don't remember any particular gripes. > But I do like the parsing-approach. I looked into ditch Vim because vimscript > is > an unbearable Perlesque PITA, and making *formally* correct syntax files is > next > to impossible! > So, will anything about the parsing stuff undergo any major changes, or it > safe > to start working on some syntax highlighting (Prolog and Erlang are my first > candidates)? > > Aleks
I would note that highlighting-kate already supports Prolog and Erlang. Perhaps you could take a look at http://code.google.com/p/yi-editor/issues/detail?id=98 ? If for the same effort it would take to write Prolog & Erlang modes of equivalent quality, you could convert or integrate the highlighting-kate syntax code (with its dozens of supported languages) - that would be pretty neat. -- gwern --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list [email protected] http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
