On Wed, Oct 25, 2006 at 09:29:45AM +0200, Alexander 'boesi' Bösecke wrote:
> Hi
>
> When inserting a backtick (`) I normally type "`<space>". But sometimes
> nothing happens... When I enter a 2. <space>, I get a space. I can enter
> as many spaces as I want, but I get no backtick. When I type a letter,
> eg. d, _than_ I get "`d" at the current cursor position. Wnen I type a 2.
> ` instead of d, I get "``".
>
> And really strange is that I can't reproduce this behaviour constantly.
> Eg. starting with an empty Vim (no file opened) and the backtick+space
> works as it should. Starting an empty Vim again and it doesn't work...
> I've tested it with python and tex files. Sometime "`<space>" produce a
> backtick, but mostly not.
>
> Well I could use a mapping like this:
> imap `<space> ``<C-O>x
> But this is IMHO a bit too hackish.
>
> I'm using gVim 7 on WinXP. The Console-Vim seems to work correctly. Is
> this a matter of my configuration? Or where is the ` waiting?
On Wed, Oct 25, 2006 at 08:23:40PM +0200, Alexander 'boesi' Bösecke wrote:
> Hi
>
> Am 25.10.2006 15:08:23 schrieb Benji Fisher:
[snip]
> > I suggest typing CTRL-V before the back-tick and before the
> > space. Just to be sure, I would also try starting vim with
> >
> > $ vim -u NONE
>
> Both don't change anything. But as I've noted earlier, console-vim
> doesn't have this problem - only gvim.
Sorry, I did not read the original post carefully the first time.
> > If it does not solve the problem, then PEBKAV (Problem
> > Exists Between Keyboard And Vim).
>
> Hmpf
> Can somebody at least confirm my problem? The mapping from my first mail
> solves it, but I'd like to know the cause...
I do not see any such problem using gvim on Linux.
If you want someone to try to reproduce the problem, we need more
information. Where did you get your copy of vim; or, if you compiled
yourself, how did you do it? (In the first case, please give a link to
the download site. In the second case, we need to know patch level,
which compiler, what options you used to compile, etc.) If in fact
PEBKAV, then it probably makes a difference what language/localization
you have for WinXP.
I still suspect that a mapping or abbreviation is involved.
Especially since you mentioned tex: have you installed latex-suite? If
so, then
:set ft=tex
:imap `
should show that there is a mapping defined by plugin/imaps.vim . Even
with this, I cannot reproduce the problem, though.
If there is no problem with console-vim, then I want to know the
result of starting gvim while skipping all your startup files. I am not
sure of the right syntax from an XP command line, but something like
$ gvim.exe -u NONE -U NONE
should do it. If you still see the problem after starting gvim this
way, then I will be convinced that there is no errant mapping causing
problems. (I think the -U NONE is redundant, but it does not hurt much
to leave it in.)
HTH --Benji Fisher
