Issue 384 in vim: VIM crashes on :py import threading

2015-07-16 Fir de Conversatie vim

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 384 by beo...@gmail.com: VIM crashes on :py import threading
https://code.google.com/p/vim/issues/detail?id=384

What steps will reproduce the problem?
1. Compile vim on Windows with python2.7 support
2. Run :py import threading in gvim


What is the expected output? What do you see instead?
Expected: no output
Actual: VIM crashes, and `Fatal Python error: PyThreadState_Get: no current  
thread` is printed to console


What version of the product are you using? On what operating system?
7.4.781 on Windows (compiled with mingw64 with mingw64 Python 2.7 on MSYS2)



--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
--
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

--- 
You received this message because you are subscribed to the Google Groups vim_dev group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: FS#45535 - [vim] latest version inserting g character upon opening file looks still broken

2015-07-16 Fir de Conversatie h_east
Hi,

2015-7-16(Thu) 10:13:32 UTC+9 mailin...@pcfreak.de:
 Hi,
 
 I think the problem, that some random characters are inserted into a file 
 after opening vim is still present, see https://bugs.archlinux.org/task/45535
 
 I personally can confirm, that on Arch Linux with vim 7.4.778-1 the problem 
 is not fixed. There are 2 workarrounds that seem to help.
 
 a) remove transparency from .XResources file e.g. remove urxvt.background: 
 [80]#00
 b) apply a color scheme to vim
 
 During work I access my arch box using MobaXTerm (Windows), for testing, the 
 personal version is free for 10 connections!
 I also use Putty.
 
 Problem only happens with MobaXTerm (which I use for years now without 
 problems) but not with Putty (Windows).
 
 I do not have a .XResources file so I workarround with a color scheme at the 
 moment.
 
 I also can confirm, whithout applying one of the workarrounds but downgrading 
 vim and vim-runtime to 7.4.738-1 the problem is gone.
 It started (on my machine) with version 7.4.764-1.
 
 So the problem needs to be found in changes between version 7.4.738-1 and 
 7.4.764-1.
 
 In my opinion, it is very dangerous for the integrity of configuration files, 
 that vim inserts characters at last cursor position!
 
 Kind regards and thanks for your commitment!
 
 PCFreak

Vim 7.4.757 or later send out the background color request to terminal and 
receive response. (Depending on the conditions)
There was bugs in Vim, but we had been fixed in patch 7.4.766 and patch 7.4.770.

I think that's probably mobaXterm of bug of you have reported.

Please try to hit the following command(Background color request) on the 
mobaXterm:

printf \033]11;?\007; cat

It will probably be less of such output(Background color response):

^[]0;rgb://^[\

This is incorrect.
Correct response must begin start with ^[]11;rgb:.

The mobaXterm response is incorrect. So, Vim buffer is in a bad state.

Please report to the development company of mobaXterm.

Thanks for reporting.
--
Best regard,
Hirohito Higashi (a.k.a. h_east)

-- 
-- 
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

--- 
You received this message because you are subscribed to the Google Groups 
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Issue 385 in vim: expansion of environment variables fails in Vim backtick expression

2015-07-16 Fir de Conversatie vim

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 385 by pavol.ju...@gmail.com: expansion of environment variables  
fails in Vim backtick expression

https://code.google.com/p/vim/issues/detail?id=385

What steps will reproduce the problem?

vim -u NONE -i NONE -N
:e `=$HOME . '/.vimrc'`

What is the expected output? What do you see instead?

Vim should open the .vimrc file in my HOME directory.  Instead I see the  
following error:


E15: Invalid expression: /Users/pjuhas . '/.vimrc'

It seems that $HOME gets expanded _before_ parsing the VimL expression in  
backticks.  This would be OK for shell-expanded backtick expressions, but  
not for Vim expressions of the `=expr` kind.


What version of the product are you using? On what operating system?

Vim 7.4.712 on OS X Yosemite 10.10.4.  This is likely independent of the OS.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
--
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

--- 
You received this message because you are subscribed to the Google Groups vim_dev group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.