2011/2/10 Peter de Ridder <cavalie...@gmail.com> > On Wed, Feb 9, 2011 at 11:00 AM, Xavier Wang <weasley...@gmail.com> wrote: > > > > thank you for you patch! I desired editing hex text in Vim in a long > time. > > hex-columnview.patch can't compile in VC2008, you add preprocessing > routine > > within a macro, and VC can not hand this. > > change all > > RET_WIN_BUF_CHARTABSIZE(curwin, curbuf, s, col > > #ifdef FEAT_HEX > > , sep > > #endif > > ) > > like macro to: > > # ifndef FEAT_HEX > > RET_WIN_BUF_CHARTABSIZE(curwin, curbuf, s, col) > > # else > > RET_WIN_BUF_CHARTABSIZE(curwin, curbuf, s, col, sep) > > # endif > > may resolve this problem. > > but when I set columnview, Vim behaves strange. it usually only show one > or > > two line of text, and the nest of line are "@", I don't know why it > happens. > > and, maybe you can close the syntax highlights or add new highlights > groups. > > and, how to show the original text after the hex text, so as in a normal > hex > > editor? > > I'll take that suggestion for the define in mind. > > The columnview patch is very experimental. I noticed that strange > behaviour too. It seems to be related to line numbering being enabled. > I think I started in the wrong direction with this patch. So I'll > start over and try to base my code on how 'linebreak' works. > > The settings for 'displaymode' and 'hexnumber' are pretty straight > forward. But the 'columnview' setting is a bit more difficult. For > example the 'wrap' setting must be enabled. I require that for now > because of the way I implemented the line breaking. I wonder if it > makes sense to keep this or to see if the 'columnview' implementation > should work around the 'wrap' mode. I hope the rest of the > 'columnview' setting makes sense. > If I remove the dependency of 'columnview' to 'wrap' I could see > 'columnview' be used like 'textwidth' so the line wrapping can be > setup independent of the window width. > > Regards, > Peter > > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php >
the problem is Vim haven't a good abstract paint layer. has anybody try to refactoring the render engine of Vim? now win_line function in screen.c has 2670 loc, if Vim can split render info several different module: memline -> layout -> symtax -> show then we can replace some of these module to make Vim more flexible, e.g. hex editing. but the first difficult task is to refactoring Vim, it does need a experienced expert....... -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
