-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Mon, Dec 1, 2008 at 2:01 PM, Corey O'Connor wrote: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEAREKAAYFAkk0OFEACgkQvpDo5Pfl1oK0vgCggT1I7P5QZzj4cnExSc0U/DXO RxQAn2JgXNqu87HYtjlD9ETTCX+wO3+V =T8pm -----END PGP SIGNATURE----- > > On Mon, Dec 1, 2008 at 2:54 AM, Jean-Philippe Bernardy > <[EMAIL PROTECTED]> wrote: >> I just uploaded Yi 0.5.2 to Hackage. > > I just tested "cabal install --user yi yi-vty" on a near-fresh GHC > 6.10.1 installation and it installed without problems. I am a little confused; isn't yi-vty obsolete and useless? I remember we had a discussion on uploading yi-gtk and yi-vty dummy packages since people were trying to use them with recent versions of Yi. >> Plans now include: dropping ghc 6.8 support and move on to using base 4; > > Does this effect being able to use template haskell or quasi quotes? I > vaguely recall there was a bytestring issue that prevented the use of > template haskell. As for quasi quotes, well, I think there are a > number of places quasi quotes would be useful. Well, the template-haskell package uses the (very) old packed-string package which is difficult to cabal-install. As far as I can tell, there's no reason for packed-string to be used, and I'm currently discussing this with Duncan on libraries-. >> Change the representation of buffers; >> Release and use the new version of vty; > > I presume this is referring a version of vty that uses > terminfo/termcap for all input classification? Instead of the part > custom, part terminfo based classification table. > Speaking of vty: I've uploaded 3.1.6 to hackage which has fixes to > build with GHC 6.10.1. However this release does not build with GHC > 6.8; 3.1.2 is the last release that does. I'm not sure how this will > effect yi's userbase (A bit of shortsightedness on my part) but I > intend to resolve that problem in the next release of vty. Presumably it won't really affect cabal-install users; I believe it's supposed to be smart enough to see that the most recent vty won't build for 6.8.x users and will backtrack to one that will. But I guess someone should test that that actually happens. > Cheers, > Corey O'Connor > >> many other things -- ideas welcome :) > > The things I've been thinking of working on are: > * More internal documentation of yi. > * modeline support > * Improved Perl and C/C++ lexer. Personally, what I'd really like is basic macro support, a Lisp mode, and a shell mode. With those three things, most of my Emacs functionality would be replicated. Random polish is also quite as valuable as better internal docs; we shouldn't be releasing half-broken stuff eg. M-x insertB was broken but it seems no one noticed that until I began experimenting with the M-x functions (trying to see why 'box replaceString' was failing). -- gwern --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
