Re: But in Ctrl-N completion
Martin Stubenschrott wrote: I am using vim7 final, and have this problem: Let's assume this buffer (between the quotes): " this that " Now i start inserting 'th' and press ctrl-n and get a popup menu with two choices 'this' and 'that', while the inserted text still remains 'th' (I am using completeopt=longest,menu,preview). Now I decide to keep on writing since I don't want neither 'this' or 'that', and write let's say 'thus'. After that I press 'esc', and a '.' to repeat the insertion. But now I get 'thusus' instead of just 'thus'. regards, and thanks for the wonderful vim7 release. -- Martin IIUC, the 2nd "us" is the "repeated" insertion, from your dot command. Maybe "thusthus" would have been more logical but I guess using Omni completion (even without applying any result found) created an undo point. (IIUC, Escape just left Insert mode, going into Normal mode.) Or did I misunderstand you? Best regards, Tony.
But in Ctrl-N completion
I am using vim7 final, and have this problem: Let's assume this buffer (between the quotes): " this that " Now i start inserting 'th' and press ctrl-n and get a popup menu with two choices 'this' and 'that', while the inserted text still remains 'th' (I am using completeopt=longest,menu,preview). Now I decide to keep on writing since I don't want neither 'this' or 'that', and write let's say 'thus'. After that I press 'esc', and a '.' to repeat the insertion. But now I get 'thusus' instead of just 'thus'. regards, and thanks for the wonderful vim7 release. -- Martin
CVS service resumed?
Hi all, It seems that the CVS service of sourceforge.net resumed again. The host name changed to "vim.cvs.sourceforge.net". So what? Regards, Edward Leap Fox
RE: SVN and svn:eol-style
In regard to line-endings in vim sources, Bill McCarthy wrote > >> So? Why are you using notepad? > > When working on another's computer, what > do you suggest? Wordpad? This thread is about adding CR/LF to vim sources in svn. So the question is why would one need to view vim's sources in notepad? If vim sources is on the computer, won't some version of vim be on it too? --Suresh
Re: vim7 possible bug
On 5/11/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote: 1. Vim is not an IDE 2. Vim works differently 3. Get used to it Hah. Awesome, I literally "LOL"ed
Re: vim7 possible bug
Le Jeu 11 Mai 2006 21:55, Martin Stubenschrott a écrit : > On Thu, May 11, 2006 at 03:10:40PM +0200, Pierre Habouzit wrote: > > Le Jeu 11 Mai 2006 14:57, Pierre Habouzit a écrit : > > > " make work in popup > > > inoremap =pumvisible() ? "\C-Y>" : > > > "\cr>" > > > > > > sadly I can't do the same with to exit the completion, > > > because of beeing (and me using vim into non 8-bit > > > capable terminals). > > > > which is a wrong assertion, > > > > inoremap =pumvisible() ? "\C-E>" : "\esc>" > > > > just look to work fine. I don't remember which problem I > > encountered with that one ... > > Here it doesn't work (urxvt terminal), after this mapping, I get > things like just writing A and B on a new line when I press or > after canceling a popup with esc. rght, that was the problem: and other keys like that do not work anymore in insert mode. I knew there was a “small glitch” if using vim in a terminal emulator :) -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgp3jJvB0phbw.pgp Description: PGP signature
Re: vim7 possible bug
On Thu, May 11, 2006 at 03:10:40PM +0200, Pierre Habouzit wrote: > Le Jeu 11 Mai 2006 14:57, Pierre Habouzit a écrit : > > > " make work in popup > > inoremap =pumvisible() ? "\C-Y>" : "\cr>" > > > > sadly I can't do the same with to exit the completion, because > > of beeing (and me using vim into non 8-bit capable > > terminals). > > which is a wrong assertion, > > inoremap =pumvisible() ? "\C-E>" : "\esc>" > > just look to work fine. I don't remember which problem I encountered > with that one ... Here it doesn't work (urxvt terminal), after this mapping, I get things like just writing A and B on a new line when I press or after canceling a popup with esc.
Re: SVN and svn:eol-style
On 5/11/06, Bill McCarthy <[EMAIL PROTECTED]> wrote: On Thu 11-May-06 6:31am -0600, you wrote: > So? Why are you using notepad? When working on another's computer, what do you suggest? Wordpad? Wordpad does understand LF as line separator, unlike notepad. Yakov
Re: SVN and svn:eol-style
On 5/11/06, Bill McCarthy <[EMAIL PROTECTED]> wrote: On Thu 11-May-06 6:31am -0600, you wrote: > So? Why are you using notepad? When working on another's computer, what do you suggest? Wordpad? I really don't understand what causes you so many problems. Why are you working with the Vim sources in the first place, and why are you doing so on a computer without Vim installed? n.o.w.
Re: SVN and svn:eol-style
On Thu 11-May-06 6:31am -0600, you wrote: > On 5/11/06, Bill McCarthy <[EMAIL PROTECTED]> wrote: >> On Wed 10-May-06 3:06am -0600, Nikolai Weibull wrote: >> >> > On 5/10/06, Bill McCarthy <[EMAIL PROTECTED]> wrote: >> > >> >> When I checkout vim7 with svn under WinXP Pro, my text files >> >> are all coming out as UNIX files (using LF instead of >> >> CR/LF). >> > >> > So? Doesn't Vim handle them correctly? >> >> So? Do other utilities and apps work also? >> >> Not even WinXP's notepad can handle LF only. > So? Why are you using notepad? When working on another's computer, what do you suggest? Wordpad? >> >> The svn program is designed to handle proper EOL for an >> >> operating system when a property called svn:eol-stype is set >> >> to "native". >> > >> > It's uncanny how aptly named Subversion really is... >> >> I believe a similar technique is used in CVS. All that is >> needed, is to mark the appropriate files (.txt, .c, .h, >> .mak, etc.). > So perhaps we should continue using CVS then? Seeing as how it got so > much right... No need to, snv is now set up properly and works well. -- Best regards, Bill
Re: SVN and svn:eol-style
On Thu 11-May-06 2:03am -0600, you wrote: > Bill McCarthy wrote: >> >> When I checkout vim7 with svn under WinXP Pro, my text files >> >> are all coming out as UNIX files (using LF instead of >> >> CR/LF). >> >> >> >> The svn program is designed to handle proper EOL for an >> >> operating system when a property called svn:eol-stype is set >> >> to "native". >> >> >> >> Am I supposed to do anything special to cause svn to give my >> >> text files to be stored as standard CR/LF files? >> > >> > Why do you want CR-LF files? A single LF should work just fine. >> >> The svn docs explain this quite well. Some programs fail to >> properly deal with LF only. A good example is Microsoft >> notepad.exe. > In the context of Vim I don't think we should worry about notepad users. Probably not, but there are other utility programs that also fail on LF files. As Mike wrote, the diff utility was one of these - I haven't checked the new diff.exe that was distributed with Windows Vim. >> > Automatic LF to CR-LF translation always causes trouble somewhere. >> >> I have never had a problem with CVS doing this. I believe >> the "trick" is to only mark 'native' those files which are >> indeed text files. > Right. So what if files aren't properly marked as text or binary? And > there always is a mistake somewhere (I recall there was an icon file > that was broken for a year before someone discovered it should be marked > binary). > I've seen too many files with mixed line endings, this can be a real > mess. Especially Unix files that were edited in Visual studio. > Also remember that files on a USB stick will never adjust to the > computer you plug it into. Systems must be able to deal with both LF > and CR-LF. > There is only one solution eventually: Drop those CR-LF line separators. > It just takes a bit of time before all MS-Windows programs can deal with > them. One big step forward is to (1) use the LF format in the Window distribution and (2) use the same file structure for Windows and UNIX. -- Best regards, Bill
Re: SVN and svn:eol-style
Edward, On Thu 11-May-06 12:45am -0600, you wrote: > Well, well, well... I prop-setted most of the file that I > recognized. If you find anything wrong or prop missing, > plz contact me. Fantastic! Although I haven't set this up yet, now I should be able to write a small batch file to update the Windows Vim distribution a few `copy /us` commands. Assuming that works, we can keep our Windows Vim tree updated indirectly through svn. It is still unfortunate that the Windows and UNIX trees can't be the same structure. If that were the case, svn would work directly. > The bad news for everyone is, after prop-setting the files, everyone > has to download the prop-setted files again. That will cost quite a > long time. It took 3 or 4 'snu up' tries to get all the way through, but was fairly painless. -- Thanks again, Bill
Patch 7.0.012
Patch 7.0.012
Problem:Using the matchparen plugin, moving the cursor in Insert mode to a
shorter line that ends in a brace, changes the preferred column
Solution: Use winsaveview()/winrestview() instead of getpos()/setpos().
Files: runtime/plugin/matchparen.vim
*** ../vim-7.0.011/runtime/plugin/matchparen.vimWed May 10 15:22:55 2006
--- runtime/plugin/matchparen.vim Thu May 11 14:42:55 2006
***
*** 1,6
" Vim plugin for showing matching parens
" Maintainer: Bram Moolenaar <[EMAIL PROTECTED]>
! " Last Change: 2006 Apr 27
" Exit quickly when:
" - this plugin was already loaded (or disabled)
--- 1,6
" Vim plugin for showing matching parens
" Maintainer: Bram Moolenaar <[EMAIL PROTECTED]>
! " Last Change: 2006 May 11
" Exit quickly when:
" - this plugin was already loaded (or disabled)
***
*** 90,96
" Find the match. When it was just before the cursor move it there for a
" moment.
if before > 0
! let save_cursor = getpos('.')
call cursor(c_lnum, c_col - before)
endif
--- 90,96
" Find the match. When it was just before the cursor move it there for a
" moment.
if before > 0
! let save_cursor = winsaveview()
call cursor(c_lnum, c_col - before)
endif
***
*** 102,108
let [m_lnum, m_col] = searchpairpos(c, '', c2, s_flags, s_skip, stopline)
if before > 0
! call setpos('.', save_cursor)
endif
" If a match is found setup match highlighting.
--- 102,108
let [m_lnum, m_col] = searchpairpos(c, '', c2, s_flags, s_skip, stopline)
if before > 0
! call winrestview(save_cursor)
endif
" If a match is found setup match highlighting.
*** ../vim-7.0.011/src/version.cThu May 11 19:24:16 2006
--- src/version.c Thu May 11 19:29:58 2006
***
*** 668,669
--- 668,671
{ /* Add new patch number below this line */
+ /**/
+ 12,
/**/
--
Corduroy pillows: They're making headlines!
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
Patch 7.0.011
Patch 7.0.011
Problem:Can't compile without the folding and with the eval feature.
Solution: Add an #ifdef. (Vallimar)
Files: src/option.c
*** ../vim-7.0.010/src/option.c Wed May 10 15:22:50 2006
--- src/option.cWed May 10 19:37:10 2006
***
*** 5227,5239
case PV_STL:return &curwin->w_p_stl_flags;
#endif
#ifdef FEAT_EVAL
case PV_FDE:return &curwin->w_p_fde_flags;
case PV_FDT:return &curwin->w_p_fdt_flags;
# ifdef FEAT_BEVAL
case PV_BEXPR: return &curbuf->b_p_bexpr_flags;
# endif
- #endif
- #if defined(FEAT_EVAL)
# if defined(FEAT_CINDENT)
case PV_INDE: return &curbuf->b_p_inde_flags;
# endif
--- 5227,5239
case PV_STL:return &curwin->w_p_stl_flags;
#endif
#ifdef FEAT_EVAL
+ # ifdef FEAT_FOLDING
case PV_FDE:return &curwin->w_p_fde_flags;
case PV_FDT:return &curwin->w_p_fdt_flags;
+ # endif
# ifdef FEAT_BEVAL
case PV_BEXPR: return &curbuf->b_p_bexpr_flags;
# endif
# if defined(FEAT_CINDENT)
case PV_INDE: return &curbuf->b_p_inde_flags;
# endif
*** ../vim-7.0.010/src/version.cWed May 10 17:55:37 2006
--- src/version.c Thu May 11 19:22:54 2006
***
*** 668,669
--- 668,671
{ /* Add new patch number below this line */
+ /**/
+ 11,
/**/
--
hundred-and-one symptoms of being an internet addict:
112. You are amazed that anyone uses a phone without a modem on it...let
alone hear actual voices.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
gvim7 filename tab completion insert CTRL-I
I just installed vim7 on windows xp. the installer prog also removed vim6 (i chose to keep the vimrc file i'd). first problem i ran into is, in gvim command mode, typing :Ex c:\LongDir insert ^I instead of completing the file/dir name to LongDirName. This always worked until vim7. Do I (how) need to edit .vimrc somehow so tab file name completion would work again in Vim7 ? Thanks. tcpoob At yahoo dot com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: SVN and svn:eol-style
On Thu, May 11, 2006 at 09:03:20AM +0200, Bram Moolenaar wrote: > Right. So what if files aren't properly marked as text or binary? And > there always is a mistake somewhere (I recall there was an icon file > that was broken for a year before someone discovered it should be marked > binary). It looks like perhaps the tool that is converting between CVS and SVN isn't copying the attributes over. Dave
Re: vim7 possible bug
Le Jeu 11 Mai 2006 14:57, Pierre Habouzit a écrit : > " make work in popup > inoremap =pumvisible() ? "\C-Y>" : "\cr>" > > sadly I can't do the same with to exit the completion, because > of beeing (and me using vim into non 8-bit capable > terminals). which is a wrong assertion, inoremap =pumvisible() ? "\C-E>" : "\esc>" just look to work fine. I don't remember which problem I encountered with that one ... -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpcyonmnM1F8.pgp Description: PGP signature
Re: vim7 possible bug
On 5/11/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote: Matt Zyzik wrote: > Not a single IDE has the kind of completion system where the entry isn't > selected as you type it. It's a speed convenience, that you can hit > enter at any time to insert the entry into text. With Vim, I could hit > to keep completing, or to select. I don't feel like having > to type before either of those two. It's too time consuming and > annoying. Doesn't anyone agree? Who disagrees? 1. Vim is not an IDE 2. Vim works differently 3. Get used to it Amen. n.o.w.
Re: vim7 possible bug
Le Jeu 11 Mai 2006 00:18, Matt Zyzik a écrit : > > > Ok good. However, I don't see why the item shouldn't be selected > > > in the first place (as you type), like it was before. It seems > > > like there was no harm in this, and also you can just hit > > > rather than . And you could also start hitting > > > without having to hit first. > > > > It's this way because people mentioned that CTRL-N didn't get the > > first entry but the second one. I think it's not illogical that > > when you use "longest" that you get the longest common text and no > > entry selected yet. > > Not a single IDE has the kind of completion system where the entry > isn't selected as you type it. It's a speed convenience, that you can > hit enter at any time to insert the entry into text. With Vim, I > could hit to keep completing, or to select. I don't feel > like having to type before either of those two. It's too time > consuming and annoying. Doesn't anyone agree? well, IDE's are wrong. moreover autocommands helps you here to implement such a behaviour. > Who disagrees? I do, I hate when an IDE try to complete everytime, everywhere, with no idea of what I need for autocompletion. Especially since vim autocompletion is purely syntaxic (without clever omnicompletion at least) which can be bothering with big sources. I love needing C-n (even if I remapped it to with clever heuristics to guess if I want autocompletion or ;p). I don't like the to validate your choice, so I've used a hack that is suggested in the help: " make work in popup inoremap =pumvisible() ? "\C-Y>" : "\cr>" sadly I can't do the same with to exit the completion, because of beeing (and me using vim into non 8-bit capable terminals). I'm perfectly happy with that, because I like my editor doing what I want, not what I *may* want. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpIP7YAmNF4F.pgp Description: PGP signature
RE: guifont: a few issues/problems?
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ... > > Trying gvim-gtk2 and gvim-motif on Linux system (I didn't try > > other gui's but I could if needed) I found the > > following differences I am not able to say if they are > > correct or not: > > Not surprising, GTK 2 uses completely different font names. > I know and do use appropriate font nameshowgh! :-) > > - :set guifont=* > >.. select the font from the font selector that pops up > >.. and observe that: > > . in gtk2, the 'guifont' will be set to the choice > > . in motif it will not be (guifont will stay set to '*') > >Comment: I found very convenient to see to what it is set to > > because I can than copy&paste it to .gvimrc > > so I like gtk2 behavior. > > Could motif be made to behave the same way? > > What about other gui's? > > Perhaps 'guifont' can be set to the selected font. It's not easy > though, there are a lot of fall back mechanisms. > For TODO then? Would be useful. > > - in both: when I enter :set guifont=* for the first time, > >make no selection click OK, and repeat the command, > >the choice displayed the first and the second time will be very > >different. From then on the display will always be like the > >second time. Repeatable. > >Why? > > Vim tries to set the default to the currently selected font. Because > X11 font names are weird this doesn't always work properly. > They are weird, indeed. Maybe a word or two in the doc would prevent me asking :-)?? > > - Question: > >I have different settings of guifont (list of fonts) for gtk2, > >motif, X11, win32, etc. When I startup gvim, I don't > actually know, > >which font has been picked up for a given choice of gui (which > >element in the guifont list) or maybe one that is not in the > >list when none in the list exists on the platform I am running. > >This is really painful and time consuming to find out what needs > >to be changed for a given O/S platform to get a pleasing display. > >If you move from platform to another often it becomes a headache. > >So: is there or could we have a way to actually display the > >font definition which has been chosen? > >like :set thisguifont? > > Not in general, the GUI library often does things we don't know about. > Especially when you have an incomplete font name (with "*" in X11 font > names) and when you change 'encoding'. For X11 there are > also fontsets, > thus a list of font names. > I see, that's too bad, not nice as it is (in gui's). > > - perhaps unrelated question: > >using colorscheme 'xterm16', I find very striking differences > >in highlightings between motif and gtk2 gui. Motif could be > >called "beautiful" while gtk2 "lousy" at best. > >Is there any coherent explanation to this? > > Depends on how the colors are defined: with names or RGB values. With > RGB values they should be the same. > OK, will have to look at that, thanks for the idea. Cheers, ---Zdenek
Re: SVN and svn:eol-style
On 5/11/06, Bill McCarthy <[EMAIL PROTECTED]> wrote: On Wed 10-May-06 3:06am -0600, Nikolai Weibull wrote: > On 5/10/06, Bill McCarthy <[EMAIL PROTECTED]> wrote: > >> When I checkout vim7 with svn under WinXP Pro, my text files >> are all coming out as UNIX files (using LF instead of >> CR/LF). > > So? Doesn't Vim handle them correctly? So? Do other utilities and apps work also? Not even WinXP's notepad can handle LF only. So? Why are you using notepad? >> The svn program is designed to handle proper EOL for an >> operating system when a property called svn:eol-stype is set >> to "native". > > It's uncanny how aptly named Subversion really is... I believe a similar technique is used in CVS. All that is needed, is to mark the appropriate files (.txt, .c, .h, .mak, etc.). So perhaps we should continue using CVS then? Seeing as how it got so much right... nikolai
Re: guifont: a few issues/problems?
Zdenek Sekera wrote: > Trying gvim-gtk2 and gvim-motif on Linux system (I didn't try > other gui's but I could if needed) I found the > following differences I am not able to say if they are > correct or not: Not surprising, GTK 2 uses completely different font names. > - :set guifont=* >.. select the font from the font selector that pops up >.. and observe that: > . in gtk2, the 'guifont' will be set to the choice > . in motif it will not be (guifont will stay set to '*') >Comment: I found very convenient to see to what it is set to > because I can than copy&paste it to .gvimrc > so I like gtk2 behavior. > Could motif be made to behave the same way? > What about other gui's? Perhaps 'guifont' can be set to the selected font. It's not easy though, there are a lot of fall back mechanisms. > - in both: when I enter :set guifont=* for the first time, >make no selection click OK, and repeat the command, >the choice displayed the first and the second time will be very >different. From then on the display will always be like the >second time. Repeatable. >Why? Vim tries to set the default to the currently selected font. Because X11 font names are weird this doesn't always work properly. > - Question: >I have different settings of guifont (list of fonts) for gtk2, >motif, X11, win32, etc. When I startup gvim, I don't actually know, >which font has been picked up for a given choice of gui (which >element in the guifont list) or maybe one that is not in the >list when none in the list exists on the platform I am running. >This is really painful and time consuming to find out what needs >to be changed for a given O/S platform to get a pleasing display. >If you move from platform to another often it becomes a headache. >So: is there or could we have a way to actually display the >font definition which has been chosen? >like :set thisguifont? Not in general, the GUI library often does things we don't know about. Especially when you have an incomplete font name (with "*" in X11 font names) and when you change 'encoding'. For X11 there are also fontsets, thus a list of font names. > - perhaps unrelated question: >using colorscheme 'xterm16', I find very striking differences >in highlightings between motif and gtk2 gui. Motif could be >called "beautiful" while gtk2 "lousy" at best. >Is there any coherent explanation to this? Depends on how the colors are defined: with names or RGB values. With RGB values they should be the same. -- hundred-and-one symptoms of being an internet addict: 104. When people ask about the Presidential Election you ask "Which country?" /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Adding a New Language for Vimtutor
Joseph Ku wrote: > I am a new subscriber of this mailing list. > I am from Taiwan, and I am also a fanatical fan of VIm. > The latest Vim, Vim7, does have many great features. > And the vimtutor is also updated to version 1.7. > Vimtutor is the most important desgin for a vim rookie. > However, I found there is no Chinese UTF-8 tutor file (Nowadays, most > distributions use UTF-8 for Chinese language support), and the existed > Chinese tutor file is just version 1.5. > Therefore, I have prepared a new tutor.vim and Chinese UTF-8 tutor > files for VIm7. > How could I update these file? > From CVS? Mail them to someone? First try to contact the previous translator/maintainer of the file. If that fails then you can send it to me. -- A meeting is an event at which the minutes are kept and the hours are lost. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Adding a New Language for Vimtutor
Hi, I am a new subscriber of this mailing list. I am from Taiwan, and I am also a fanatical fan of VIm. The latest Vim, Vim7, does have many great features. And the vimtutor is also updated to version 1.7. Vimtutor is the most important desgin for a vim rookie. However, I found there is no Chinese UTF-8 tutor file (Nowadays, most distributions use UTF-8 for Chinese language support), and the existed Chinese tutor file is just version 1.5. Therefore, I have prepared a new tutor.vim and Chinese UTF-8 tutor files for VIm7. How could I update these file? From CVS? Mail them to someone? Thanks. Best Regards, Joseph Ku
guifont: a few issues/problems?
Trying gvim-gtk2 and gvim-motif on Linux system (I didn't try other gui's but I could if needed) I found the following differences I am not able to say if they are correct or not: - :set guifont=* .. select the font from the font selector that pops up .. and observe that: . in gtk2, the 'guifont' will be set to the choice . in motif it will not be (guifont will stay set to '*') Comment: I found very convenient to see to what it is set to because I can than copy&paste it to .gvimrc so I like gtk2 behavior. Could motif be made to behave the same way? What about other gui's? - in both: when I enter :set guifont=* for the first time, make no selection click OK, and repeat the command, the choice displayed the first and the second time will be very different. From then on the display will always be like the second time. Repeatable. Why? - Question: I have different settings of guifont (list of fonts) for gtk2, motif, X11, win32, etc. When I startup gvim, I don't actually know, which font has been picked up for a given choice of gui (which element in the guifont list) or maybe one that is not in the list when none in the list exists on the platform I am running. This is really painful and time consuming to find out what needs to be changed for a given O/S platform to get a pleasing display. If you move from platform to another often it becomes a headache. So: is there or could we have a way to actually display the font definition which has been chosen? like :set thisguifont? - perhaps unrelated question: using colorscheme 'xterm16', I find very striking differences in highlightings between motif and gtk2 gui. Motif could be called "beautiful" while gtk2 "lousy" at best. Is there any coherent explanation to this? Perhaps someone will worry why am I trying different gui's, why not pick up one I like and stick to it.. That's because some platforms have only installed and not others. Thanks and cheers, ---Zdenek
Patch for Insert mode completion to try out
Using CTRL-L to add a character to the completed text caused the
currently selected match to be abandoned, going back to the typed text
with one character added. This patch should fix that.
This is tricky code, please check for any side effects. If it looks
like it is an improvement I'll send it out as an official patch.
*** ../../vim-7.0.010/src/edit.cWed May 10 15:22:49 2006
--- edit.c Thu May 11 10:38:54 2006
***
*** 751,757
continue;
}
! /* Pressing CTRL-Y selects the current match. Shen
* compl_enter_selects is set the Enter key does the same. */
if (c == Ctrl_Y || (compl_enter_selects
&& (c == CAR || c == K_KENTER || c == NL)))
--- 751,757
continue;
}
! /* Pressing CTRL-Y selects the current match. When
* compl_enter_selects is set the Enter key does the same. */
if (c == Ctrl_Y || (compl_enter_selects
&& (c == CAR || c == K_KENTER || c == NL)))
***
*** 3046,3052
ins_compl_delete();
ins_bytes(compl_leader + curwin->w_cursor.col - compl_col);
compl_used_match = FALSE;
- compl_enter_selects = FALSE;
if (compl_started)
ins_compl_set_original_text(compl_leader);
--- 3046,3051
***
*** 3076,3081
--- 3075,3081
compl_restarting = FALSE;
}
+ #if 0 /* disabled, made CTRL-L, BS and typing char jump to original text. */
if (!compl_used_match)
{
/* Go to the original text, since none of the matches is inserted. */
***
*** 3087,3092
--- 3087,3094
compl_curr_match = compl_shown_match;
compl_shows_dir = compl_direction;
}
+ #endif
+ compl_enter_selects = !compl_used_match;
/* Show the popup menu with a different set of matches. */
ins_compl_show_pum();
***
*** 3175,3184
char_u*p;
int len = curwin->w_cursor.col - compl_col;
int c;
p = compl_shown_match->cp_str;
if ((int)STRLEN(p) <= len) /* the match is too short */
! return;
p += len;
#ifdef FEAT_MBYTE
c = mb_ptr2char(p);
--- 3177,3208
char_u*p;
int len = curwin->w_cursor.col - compl_col;
int c;
+ compl_T *cp;
p = compl_shown_match->cp_str;
if ((int)STRLEN(p) <= len) /* the match is too short */
! {
! /* When still at the original match use the first entry that matches
!* the leader. */
! if (compl_shown_match->cp_flags & ORIGINAL_TEXT)
! {
! p = NULL;
! for (cp = compl_shown_match->cp_next; cp != NULL
!&& cp != compl_first_match; cp = cp->cp_next)
! {
! if (ins_compl_equal(cp, compl_leader,
! (int)STRLEN(compl_leader)))
! {
! p = cp->cp_str;
! break;
! }
! }
! if (p == NULL || (int)STRLEN(p) <= len)
! return;
! }
! else
! return;
! }
p += len;
#ifdef FEAT_MBYTE
c = mb_ptr2char(p);
***
*** 4100,4105
--- 4124,4144
&& compl_shown_match->cp_next != NULL
&& compl_shown_match->cp_next != compl_first_match)
compl_shown_match = compl_shown_match->cp_next;
+
+ /* If we didn't find it searching forward, and compl_shows_dir is
+* backward, find the last match. */
+ if (compl_shows_dir == BACKWARD
+ && !ins_compl_equal(compl_shown_match,
+ compl_leader, (int)STRLEN(compl_leader))
+ && (compl_shown_match->cp_next == NULL
+ || compl_shown_match->cp_next == compl_first_match))
+ {
+ while (!ins_compl_equal(compl_shown_match,
+ compl_leader, (int)STRLEN(compl_leader))
+ && compl_shown_match->cp_prev != NULL
+ && compl_shown_match->cp_prev != compl_first_match)
+ compl_shown_match = compl_shown_match->cp_prev;
+ }
}
if (allow_get_expansion && insert_match
--
hundred-and-one symptoms of being an internet addict:
102. When filling out your driver's license application, you give
your IP address.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: SVN and svn:eol-style
Edward L. Fox did utter on 11/05/2006 06:45: On 5/11/06, Bill McCarthy <[EMAIL PROTECTED]> wrote: On Wed 10-May-06 9:43pm -0600, Anduin Withers wrote: >> Why do you want CR-LF files? A single LF should work just fine. The >> only place where I know it doesn't work is when you read Make_ivc.mak >> into Visual Studio. >> >> Automatic LF to CR-LF translation always causes trouble somewhere. > > CVS did it automatically, as long as binaries are properly tagged there > shouldn't be (and wasn't, at least for me) a problem. > > One reason is consistency: This is the behavior CVS had, it is the format > the releases are in on the ftp site, it also makes things look better when I > edit my .vim files with notepad. > > Just another request for native line endings. Some days it is better for me to read my mail from newest to oldest - or at least read through everything before replying. Well stated. I now wish I used a different example that notepad - although that is indeed a good one, since every Windows user has it and it is frequently a default in Explorer. Hopefully, the gentleman maintaining the svn repository (Edward L Fox) will talk to the gentleman who properly marked the files in CVS. Well, well, well... I prop-setted most of the file that I recognized. If you find anything wrong or prop missing, plz contact me. The bad news for everyone is, after prop-setting the files, everyone has to download the prop-setted files again. That will cost quite a long time. I have also had no problems with the CVS distribution That's because CVS doens't support that features at all and every text file is forced to use native linebreaks. -- Best regards, Bill Another match on the oil - the patch utility I use on windows gets very unhappy if the source file and patch file use different line endings. There isn't an option to alter line endings when saving attachments in TBird (that I have found). Fighting the natural order of things on a particular platform is a recipe for unending pain. I would have thought any source control system would Do The Right Thing wrt line endings by default, since the vast majority of files it will contain would be text based. 2ps worth. Mike -- Taglines temporarily suspended - sorry.
Re: SVN and svn:eol-style
Bill McCarthy wrote: > >> When I checkout vim7 with svn under WinXP Pro, my text files > >> are all coming out as UNIX files (using LF instead of > >> CR/LF). > >> > >> The svn program is designed to handle proper EOL for an > >> operating system when a property called svn:eol-stype is set > >> to "native". > >> > >> Am I supposed to do anything special to cause svn to give my > >> text files to be stored as standard CR/LF files? > > > > Why do you want CR-LF files? A single LF should work just fine. > > The svn docs explain this quite well. Some programs fail to > properly deal with LF only. A good example is Microsoft > notepad.exe. In the context of Vim I don't think we should worry about notepad users. > > Automatic LF to CR-LF translation always causes trouble somewhere. > > I have never had a problem with CVS doing this. I believe > the "trick" is to only mark 'native' those files which are > indeed text files. Right. So what if files aren't properly marked as text or binary? And there always is a mistake somewhere (I recall there was an icon file that was broken for a year before someone discovered it should be marked binary). I've seen too many files with mixed line endings, this can be a real mess. Especially Unix files that were edited in Visual studio. Also remember that files on a USB stick will never adjust to the computer you plug it into. Systems must be able to deal with both LF and CR-LF. There is only one solution eventually: Drop those CR-LF line separators. It just takes a bit of time before all MS-Windows programs can deal with them. -- hundred-and-one symptoms of being an internet addict: 96. On Super Bowl Sunday, you followed the score by going to the Yahoo main page instead of turning on the TV. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: vim7 possible bug
Matt Zyzik wrote: > Not a single IDE has the kind of completion system where the entry isn't > selected as you type it. It's a speed convenience, that you can hit > enter at any time to insert the entry into text. With Vim, I could hit > to keep completing, or to select. I don't feel like having > to type before either of those two. It's too time consuming and > annoying. Doesn't anyone agree? Who disagrees? 1. Vim is not an IDE 2. Vim works differently 3. Get used to it Is it so difficult to type CTRL-N to get the first entry? I'm getting a bit tired of these remarks about how it works elsewhere. I'll keep it as-is for at least a month and only fix real bugs. So you need to get used to how it is now. Then after a several weeks we might see how well it works. -- hundred-and-one symptoms of being an internet addict: 97. Your mother tells you to remember something, and you look for a File/Save command. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
