Re: New feature: cursor at the beginning of tab character in normal mode
That seems unexpected to me. Cheers, Craig Think about this. Changing it would be unexpected to the vast majority of vim users. I agree with Bram, this is best left alone. - Ian --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch 7.2.010
On Sat, Sep 06, 2008 at 04:56:25PM +0200, Bram Moolenaar wrote:
Patch 7.2.010
Problem:When using K in Visual mode not all characters are properly
escaped. (Ben Schmidt)
Solution: Use a function with the functionality of shellescape(). (Jan
Minar)
Files:src/mbyte.c, src/misc2.c, src/normal.c
This ended up breaking the functionality of K all together. The entire
line, starting from the beginning of the word under the cursor, is used
in the command instead of just the word itself. This can be verified by
placing the cursor on the word popen in the following line and pressing
K.
FILE *popen(const char *command, const char *type);
The attached patch fixes the problem.
--
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega [EMAIL PROTECTED]
diff --git a/src/normal.c b/src/normal.c
index c1e630a..785de7c 100644
--- a/src/normal.c
+++ b/src/normal.c
@@ -5519,8 +5519,11 @@ nv_ident(cap)
*/
if (cmdchar == 'K' !kp_help)
{
+ /* Use only the chars in the identifier, instead of the whole line */
+ char_u s[n+1];
+ vim_strncpy(s, ptr, n);
/* Escape the argument properly for a shell command */
- p = vim_strsave_shellescape(ptr, TRUE);
+ p = vim_strsave_shellescape(s, TRUE);
if (p == NULL)
{
vim_free(buf);
signature.asc
Description: Digital signature
View this page Vim patches
vimGdb patch added to Vim patches Xavier de Gaye Click on http://groups.google.com/group/vim_dev/web/vim-patches - or copy paste it into your browser's address bar if that doesn't work. --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: View this page Vim patches
On 03/10/08 21:51, [EMAIL PROTECTED] wrote: vimGdb patch added to Vim patches Xavier de Gaye Click on http://groups.google.com/group/vim_dev/web/vim-patches - or copy paste it into your browser's address bar if that doesn't work. I took the liberty of adding Bill McCarthy's additional floating-point functions (with a link to what I think is the right post in this group for 7.2). Bill, of course, feel free to edit or remove any or all of what I added. Best regards, Tony. -- The church is near but the road is icy; the bar is far away but I will walk carefully. -- Russian Proverb --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
!py import weakref breaks vim
Can anyone confirm that typing the following breaks vim? !py import weakref Vim: Caught deadly signal ABRT Vim: Finished. Aborted Does anybody know what might be the source of this bug? --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: !py import weakref breaks vim
I meant :py, not !py... thanks for the feedback. I've confirmed that it's only breaking on one of my builds, and on another it works, so I'm sure it's just a problem with how I'm compiling it. Greg On Fri, Oct 3, 2008 at 3:16 PM, Tony Mechelynck [EMAIL PROTECTED] wrote: On 03/10/08 20:19, Greg wrote: Can anyone confirm that typing the following breaks vim? !py import weakref Vim: Caught deadly signal ABRT Vim: Finished. Aborted Does anybody know what might be the source of this bug? Works for me, with a colon instead of an exclamation mark, in a gvim version compiled with +python and the corresponding python libs installed on the system. No output. Also in Console mode. !p just gives a beep (meaning invalid Normal-mode sequence). Best regards, Tony. -- The road to hell is paved with good intentions. And littered with sloppy analysis! --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: !py import weakref breaks vim
On 04/10/08 00:34, Greg Warner wrote: I meant :py, not !py... thanks for the feedback. I've confirmed that it's only breaking on one of my builds, and on another it works, so I'm sure it's just a problem with how I'm compiling it. Greg Have you kept the make logs? Anything suspicious? Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 196. Your computer costs more than your car. --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
