[SOLVED] vim inserting random characters when starting up

lorizean · 2015-07-03 13:24:36

Hello,

after the recent update to gvim and vim-runtime, whenever I open vim, it starts the session in insert mode with the characters "gba:b333/0000/0000/0000[>85;95;0c" already inserted.
This does not happen when using gvim.

This is my vimrc, if that matters.

A friend of mine running arch has the same problem.

I'm rolling back for now, but I'd be interested to know if other people have the same problem.

Last edited by lorizean (2015-07-12 21:38:11)

Trilby · 2015-07-03 13:41:45

No issues here. Does this friend share any of your configs (vim, shell, ...)? If so (or in either case really) what is the output of `type vim`?

Do you get the same effect when logged in as another user (e.g. root)? Does this happen when opening a blank buffer and/or when opening an existing file? Does it happen if you open an additional buffer when vim is already running (either blank or for an existing file)?

karol · 2015-07-03 16:16:32

https://bugs.archlinux.org/task/45535 ?

lorizean · 2015-07-03 18:53:15

Trilby wrote:

No issues here. Does this friend share any of your configs (vim, shell, ...)? If so (or in either case really) what is the output of `type vim`?
Do you get the same effect when logged in as another user (e.g. root)? Does this happen when opening a blank buffer and/or when opening an existing file? Does it happen if you open an additional buffer when vim is already running (either blank or for an existing file)?

We're not sharing configs, but we both use zsh.

type vim gives "vim is /usr/bin/vim".

It happens when opening blank buffers or files, but not if I open a new buffer inside an already running vim instance.

I just noticed something weird: If there's no .vimrc (and /etc/vimrc is completely commented out or not there), it doesn't happen.
But if a .vimrc is present (even a completely empy one), the characters get inserted - tested this out with other users as well (root and a newly created test user).

Trilby · 2015-07-03 18:57:05

Thanks for addressing all of my questions well - unfortunately that leaves me stumped. It sounds like there might be a bug somewhere - but I'm certainly not experiencing it. I might try zsh in a moment to see if I can replicate it there.

Edit: nothing here even with zsh - but I had an empty/default zsh config as I installed it just to test. Are you on x86_64 or i686?

Last edited by Trilby (2015-07-03 18:59:52)

lorizean · 2015-07-03 19:04:53

I am on x86_64.

I also tried different shells (bash, sh), but the same problem occurs.
I also removed all plugins, but to no avail.

js · 2015-07-03 19:09:59

I am seeing something similar. However, I see :6666/0000/0000/0000[>85;95;0c

However, I have just found out that I'm only seeing it when using urxvtc, but not another VT or xterm.

lorizean · 2015-07-03 19:14:53

js wrote:

I am seeing something similar. However, I see :6666/0000/0000/0000[>85;95;0c
However, I have just found out that I'm only seeing it when using urxvtc, but not another VT or xterm.

You are correct, I only have this happen in urxvt as well.

thisoldman · 2015-07-04 07:47:14

I use a bash shell so I don't see this. But it strikes me that the two strings end with the same characters:
⁣ ⁣ ⁣ "[>85;95;0c".

U+0085 = 'NEXT LINE'
U+0095 = 'MESSAGE WAITING'
U+000C = 'FORM FEED'

Have you tried disabling any plugins?
Does the message appear when vim is started without a .vimrc, $ vim -u NONE ?

h8h · 2015-07-04 10:14:12

I've updated the bugreport.

I've also updated vim today and have this issue with my urxvt terminal. Using rxvt (without unicode) or vte works fine. So maybe this issue is unicode related.

@edit
I figure out that my .Xresources has something in common with this. I delete line-by-line everything until vim work the way it should work, and this line does the magic

before:

URxvt.background: [85]#11111

vim goes :d999/d2d1/6968/8786[>85;95;0

after:

URxvt.background: #11111

vim works

Yeah vim hates my transparency

Last edited by h8h (2015-07-04 10:35:13)

skwee · 2015-07-04 12:35:09

Thank you! I've had similar issue and removing transparency solved it!

knigitz · 2015-07-04 12:46:34

This must have happened after a recent update. I had this working fine until I issued a pacman -Syu this morning. Here's what it changed:

[2015-07-04 06:18] [ALPM] upgraded vim-runtime (7.4.738-1 -> 7.4.764-1)
[2015-07-04 06:18] [ALPM] upgraded vim (7.4.738-1 -> 7.4.764-1)

Edit:

I just confirmed that the following resolved this issue for me (assuming you have had these packages installed recently):

# cd /var/cache/pacman/pkg
# sudo pacman -U vim-runtime-7.4.738-1-x86_64.pkg.tar.xz vim-7.4.738-1-x86_64.pkg.tar.xz

Last edited by knigitz (2015-07-04 12:47:13)

h8h · 2015-07-04 13:36:46

I've also updated vim this morning and I had this issue, downgrading works, yes, but thats not my way to troubleshoot problems ;-)

skwee wrote:

Thank you! I've had similar issue and removing transparency solved it!

Thanks! Can anyone else confirm that this way solves the vim issue?

knigitz · 2015-07-04 16:39:07

h8h wrote:

I've also updated vim this morning and I had this issue, downgrading works, yes, but thats not my way to troubleshoot problems ;-)
skwee wrote:
Thank you! I've had similar issue and removing transparency solved it!
Thanks! Can anyone else confirm that this way solves the vim issue?

I'm not saying that it's going to get us to the root cause (obviously testing the configuration was appropriate, not saying otherwise), but until it gets fixed in a push to the master branch, for some vim users, there's an easy option to retain window transparency and use vim.

And yes, removing transparency does workaround the issue. Downgrading avoids it.

Last edited by knigitz (2015-07-04 16:43:28)

anatolik · 2015-07-04 18:05:50

I quickly checked vim recent changelog and do not see any obvious culprits for such transparency behavior. Please report your issue and findings upstream maillist.

js · 2015-07-04 18:17:14

Patch 7.4.757 is the first patch that I've found that exhibits the problem. What is the proper upstream list/site for vim?

anatolik · 2015-07-04 19:04:09

This is the maillilst https://groups.google.com/forum/#!forum/vim_dev and here is patch/discussion for 7.4.757 https://groups.google.com/forum/#!topic … LGjKaEzNUY

bpupp · 2015-07-06 03:48:37

I believe the full string is some kind of rgba color, which is why it inputs differently depending on what file is opened. eg. a blank file will not have the 'g' at the front because 'rg' will replace a letter with g. Also had this problem, also using urxvt, and terminal was also translucent. I changed it to solid and it is fixed now, weird. Also found out that setting a colorscheme in your .vimrc will fix the problem even if the terminal is translucent. So it might be something to do with vim trying to autodetect a colorscheme?

Last edited by bpupp (2015-07-06 03:53:55)

jdunn · 2015-07-06 16:28:11

This just started happening to me too. During a bit of sleuthing I realized that the characters being inserted, i.e.

:dddd/1110/1110/1110[>85;95;0c

look suspiciously like my urxvt-unicode color settings from ~/.Xresources:

URxvt*foreground: rgba:1111/1111/1111/dddd

And indeed, after modifying URxvt.foreground slightly (changed to hex color codes), VIM started inserting something that resembled my changed color codes.

w201 · 2015-07-07 19:38:11

Same problem here and disabling transparency temporarily (thanks h8h!!) solves the issue at least until they release a patch.

dalker · 2015-07-08 10:24:09

Same problem here, with the following inserted characters: g:ccdd/0000/0000/0000[>85;95;0c
Thanks for all in this thread to clarify the origins of the problem and suggesting workarounds.
Personally I'll be using vim from xterm instead of urxvt until this is fixed, in order to avoid changing any configuration files.
EDIT: found a second, better, workaround (for now): opening a tmux session within urxvt circumvents the bug

Last edited by dalker (2015-07-08 17:08:14)

vohof · 2015-07-10 01:08:31

I'm also having this problem and disabling the transparency in ~/.Xresources has circumvented this issue. I wonder what's causing it.

js · 2015-07-10 16:57:26

Just tested the newest code pushes(version 7.4.775) and the issue seems to be fixed, so the next update here on Arch hopefully won't have this issue anymore.

anatolik · 2015-07-11 16:28:56

js wrote:

Just tested the newest code pushes(version 7.4.775) and the issue seems to be fixed, so the next update here on Arch hopefully won't have this issue anymore.

Just pushed 7.4.778 to [testing], please check it.

apokatastasis · 2015-07-11 21:03:51

anatolik wrote:

Just pushed 7.4.778 to [testing], please check it.

I just upgraded to 7.4.778 to avoid this same problem with the version in stable repo, and it works for me, with or without window transparency.

Last edited by apokatastasis (2015-07-11 21:05:02)

Arch Linux

#1 2015-07-03 13:24:36

[SOLVED] vim inserting random characters when starting up

#2 2015-07-03 13:41:45

Re: [SOLVED] vim inserting random characters when starting up

#3 2015-07-03 16:16:32

Re: [SOLVED] vim inserting random characters when starting up

#4 2015-07-03 18:53:15

Re: [SOLVED] vim inserting random characters when starting up

#5 2015-07-03 18:57:05

Re: [SOLVED] vim inserting random characters when starting up

#6 2015-07-03 19:04:53

Re: [SOLVED] vim inserting random characters when starting up

#7 2015-07-03 19:09:59

Re: [SOLVED] vim inserting random characters when starting up

#8 2015-07-03 19:14:53

Re: [SOLVED] vim inserting random characters when starting up

#9 2015-07-04 07:47:14

Re: [SOLVED] vim inserting random characters when starting up

#10 2015-07-04 10:14:12

Re: [SOLVED] vim inserting random characters when starting up

#11 2015-07-04 12:35:09

Re: [SOLVED] vim inserting random characters when starting up

#12 2015-07-04 12:46:34

Re: [SOLVED] vim inserting random characters when starting up

#13 2015-07-04 13:36:46

Re: [SOLVED] vim inserting random characters when starting up

#14 2015-07-04 16:39:07

Re: [SOLVED] vim inserting random characters when starting up

#15 2015-07-04 18:05:50

Re: [SOLVED] vim inserting random characters when starting up

#16 2015-07-04 18:17:14

Re: [SOLVED] vim inserting random characters when starting up

#17 2015-07-04 19:04:09

Re: [SOLVED] vim inserting random characters when starting up

#18 2015-07-06 03:48:37

Re: [SOLVED] vim inserting random characters when starting up

#19 2015-07-06 16:28:11

Re: [SOLVED] vim inserting random characters when starting up

#20 2015-07-07 19:38:11

Re: [SOLVED] vim inserting random characters when starting up

#21 2015-07-08 10:24:09

Re: [SOLVED] vim inserting random characters when starting up

#22 2015-07-10 01:08:31

Re: [SOLVED] vim inserting random characters when starting up

#23 2015-07-10 16:57:26

Re: [SOLVED] vim inserting random characters when starting up

#24 2015-07-11 16:28:56

Re: [SOLVED] vim inserting random characters when starting up

#25 2015-07-11 21:03:51

Re: [SOLVED] vim inserting random characters when starting up

Board footer