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: 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: 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///
Re: vim7 possible bug
> > > > > When you use 'longest' then none of the items is selected. That was > > > > > discussed quite a while ago. You need to do CTRL-N first to select an > > > > > item from which you can take letters with CTRL-L. > > > > > > > > If you do CTRL-N first, then the item is selected/inserted, and CTRL-L > > > > does nothing. I think what you mean is that you select the item first > > > > with the up/down arrows and then take letters with CTRL-L. Even then > > > > that's not the case, it only works for one letter. > > > > > > > > I'm pretty sure it's a bug; try it out. > > > > > > OK, I see what you mean. After using CTRL-L it shouldn't unselect the > > > item. > > > > 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? Who disagrees? --Matt
Re: vim7 possible bug
Matt Zyzik wrote: > > > > When you use 'longest' then none of the items is selected. That was > > > > discussed quite a while ago. You need to do CTRL-N first to select an > > > > item from which you can take letters with CTRL-L. > > > > > > If you do CTRL-N first, then the item is selected/inserted, and CTRL-L > > > does nothing. I think what you mean is that you select the item first > > > with the up/down arrows and then take letters with CTRL-L. Even then > > > that's not the case, it only works for one letter. > > > > > > I'm pretty sure it's a bug; try it out. > > > > OK, I see what you mean. After using CTRL-L it shouldn't unselect the > > item. > > 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. -- # echo reboot >universe # chmod +x universe # ./universe /// 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
> > > When you use 'longest' then none of the items is selected. That was > > > discussed quite a while ago. You need to do CTRL-N first to select an > > > item from which you can take letters with CTRL-L. > > > > If you do CTRL-N first, then the item is selected/inserted, and CTRL-L > > does nothing. I think what you mean is that you select the item first > > with the up/down arrows and then take letters with CTRL-L. Even then > > that's not the case, it only works for one letter. > > > > I'm pretty sure it's a bug; try it out. > > OK, I see what you mean. After using CTRL-L it shouldn't unselect the > item. 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. > > -- > >From "know your smileys": > :-| :-| Deja' vu! > > /// 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 Mzyzik wrote: > > > I do have 'ic' set. So then it's not a bug... ok. However, you did not > > > address my other bug: to complete character by character does not > > > work. > > > > When you use 'longest' then none of the items is selected. That was > > discussed quite a while ago. You need to do CTRL-N first to select an > > item from which you can take letters with CTRL-L. > > If you do CTRL-N first, then the item is selected/inserted, and CTRL-L > does nothing. I think what you mean is that you select the item first > with the up/down arrows and then take letters with CTRL-L. Even then > that's not the case, it only works for one letter. > > I'm pretty sure it's a bug; try it out. OK, I see what you mean. After using CTRL-L it shouldn't unselect the item. -- >From "know your smileys": :-| :-| Deja' vu! /// 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
On Wed, May 10, 2006 at 08:08:57PM +0200, Bram Moolenaar wrote: > > Matt Mzyzik wrote: > > > I do have 'ic' set. So then it's not a bug... ok. However, you did not > > address my other bug: to complete character by character does not > > work. > > When you use 'longest' then none of the items is selected. That was > discussed quite a while ago. You need to do CTRL-N first to select an > item from which you can take letters with CTRL-L. If you do CTRL-N first, then the item is selected/inserted, and CTRL-L does nothing. I think what you mean is that you select the item first with the up/down arrows and then take letters with CTRL-L. Even then that's not the case, it only works for one letter. I'm pretty sure it's a bug; try it out. > > > > > I also noticed no longer selects menu items, however I guess > > > > that might be intended as most people use as in the docs. > > > > > > Do you mean the Enter key? That changed a while back. > > > > No I don't mean Enter key. I mean . > > That doesn't have a specific meaning for completion, thus it takes you > out of completion mode. > > -- > I AM THANKFUL... > ...for a lawn that needs mowing, windows that need cleaning > and gutters that need fixing because it means I have a home. > > /// 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 Mzyzik wrote: > I do have 'ic' set. So then it's not a bug... ok. However, you did not > address my other bug: to complete character by character does not > work. When you use 'longest' then none of the items is selected. That was discussed quite a while ago. You need to do CTRL-N first to select an item from which you can take letters with CTRL-L. > > > I also noticed no longer selects menu items, however I guess > > > that might be intended as most people use as in the docs. > > > > Do you mean the Enter key? That changed a while back. > > No I don't mean Enter key. I mean . That doesn't have a specific meaning for completion, thus it takes you out of completion mode. -- I AM THANKFUL... ...for a lawn that needs mowing, windows that need cleaning and gutters that need fixing because it means I have a home. /// 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
On Wed, May 10, 2006 at 04:28:51PM +0200, Bram Moolenaar wrote: > > Matt Mzyzik wrote: > > > > > Assume the buffer is as follows (between quotes): > > > > " > > > > Rabbits are really great > > > > rats are not so great > > > > ra > > > > " > > > > > > > > Now if my cursor is after the "ra" on the third line, and I do a c-n to > > > > see keyword completions, the "ra" disappears when the menu comes up. Is > > > > this desired? > > > > > > I get "rats". Check your 'completeopt' setting. > > > > my 'completeopt' is set to "longest,menuone" > > > > also, I'm certain now that this bug didn't happen on at least one of the > > old vim betas (the one on the gentoo portage) > > > > and yes, if I take out "longest" from 'cot', then everything works > > > > there's also another problem with "longest", where the items are no > > longer selected and I cannot do things like to keep completing > > character by character > > You must also have 'ignorecase' set. What happens then is that the > matches "Rabbits" and "rats" are found. The longest common text is > empty then. Previously only one of "rabbits" and "Rabbits" would be > found. Depending on which one was found first you would get "ra" or an > empty string like now. I do have 'ic' set. So then it's not a bug... ok. However, you did not address my other bug: to complete character by character does not work. > > > I also noticed no longer selects menu items, however I guess > > that might be intended as most people use as in the docs. > > Do you mean the Enter key? That changed a while back. No I don't mean Enter key. I mean . > > -- > >From "know your smileys": > %-) After staring at screen for 15 hours > > /// 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 Mzyzik wrote: > > > Assume the buffer is as follows (between quotes): > > > " > > > Rabbits are really great > > > rats are not so great > > > ra > > > " > > > > > > Now if my cursor is after the "ra" on the third line, and I do a c-n to > > > see keyword completions, the "ra" disappears when the menu comes up. Is > > > this desired? > > > > I get "rats". Check your 'completeopt' setting. > > my 'completeopt' is set to "longest,menuone" > > also, I'm certain now that this bug didn't happen on at least one of the > old vim betas (the one on the gentoo portage) > > and yes, if I take out "longest" from 'cot', then everything works > > there's also another problem with "longest", where the items are no > longer selected and I cannot do things like to keep completing > character by character You must also have 'ignorecase' set. What happens then is that the matches "Rabbits" and "rats" are found. The longest common text is empty then. Previously only one of "rabbits" and "Rabbits" would be found. Depending on which one was found first you would get "ra" or an empty string like now. > I also noticed no longer selects menu items, however I guess > that might be intended as most people use as in the docs. Do you mean the Enter key? That changed a while back. -- >From "know your smileys": %-)After staring at screen for 15 hours /// 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
On Wed, May 10, 2006 at 11:16:40AM +0200, Bram Moolenaar wrote: > > Matt Mzyzik wrote: > > > Assume the buffer is as follows (between quotes): > > " > > Rabbits are really great > > rats are not so great > > ra > > " > > > > Now if my cursor is after the "ra" on the third line, and I do a c-n to > > see keyword completions, the "ra" disappears when the menu comes up. Is > > this desired? > > I get "rats". Check your 'completeopt' setting. my 'completeopt' is set to "longest,menuone" also, I'm certain now that this bug didn't happen on at least one of the old vim betas (the one on the gentoo portage) and yes, if I take out "longest" from 'cot', then everything works there's also another problem with "longest", where the items are no longer selected and I cannot do things like to keep completing character by character I also noticed no longer selects menu items, however I guess that might be intended as most people use as in the docs. --Matt > > -- > hundred-and-one symptoms of being an internet addict: > 89. In addition to your e-mail address being on your business > cards you even have your own domain. > > /// 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 Mzyzik wrote: > Assume the buffer is as follows (between quotes): > " > Rabbits are really great > rats are not so great > ra > " > > Now if my cursor is after the "ra" on the third line, and I do a c-n to > see keyword completions, the "ra" disappears when the menu comes up. Is > this desired? I get "rats". Check your 'completeopt' setting. -- hundred-and-one symptoms of being an internet addict: 89. In addition to your e-mail address being on your business cards you even have your own domain. /// 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///
