Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Updates: Labels: patch Comment #10 on issue 369 by chrisbr...@googlemail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 I think, this patch fixes it. Attachments: issue_369.diff 1.8 KB -- 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: Issue 368 in vim: Temporary file creation non-comprehensively fails when all the variations are taken for the name
Updates: Status: Invalid Comment #1 on issue 368 by chrisbr...@googlemail.com: Temporary file creation non-comprehensively fails when all the variations are taken for the name https://code.google.com/p/vim/issues/detail?id=368 Note, you can always get help for each error number. And there you'll see: ,[ :h E138 ]- | When you get error E138: Can't write viminfo file | check that no old temp files were left behind (e.g. | ~/.viminf*) and that you can write in the directory of | the .viminfo file. ` Therefore closing. -- 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.
add vsplit to switchbuf to enable vertical split before opening file from quickfix
Hi,
switchbuf now has four options: useopen, usetab, split and newtab.
I need an option to vertical split(vsplit).
Here is the patch.
--
--
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.
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 21cf650..4593d0b 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -7067,6 +7067,9 @@ A jump table for the options with a short description can be found at |Q_op|.
split If included, split the current window before loading
a buffer for a |quickfix| command that display errors.
Otherwise: do not split, use current window.
+ vsplit If included, vertically split the current window before loading
+ a buffer for a |quickfix| command that display errors.
+ Otherwise: do not split, use current window.
newtab Like split, but open a new tab page. Overrules
split when both are present.
diff --git a/src/buffer.c b/src/buffer.c
index 6dfe007..f4879fe 100644
--- a/src/buffer.c
+++ b/src/buffer.c
@@ -2077,11 +2077,11 @@ buflist_getfile(n, lnum, options, forceit)
wp = buf_jump_open_tab(buf);
/* If 'switchbuf' contains split or newtab and the current buffer
* isn't empty: open new window */
- if (wp == NULL (swb_flags (SWB_SPLIT | SWB_NEWTAB)) !bufempty())
+ if (wp == NULL (swb_flags (SWB_VSPLIT | SWB_SPLIT | SWB_NEWTAB)) !bufempty())
{
if (swb_flags SWB_NEWTAB) /* Open in a new tab */
tabpage_new();
- else if (win_split(0, 0) == FAIL) /* Open in a new window */
+ else if (win_split(0, (swb_flags SWB_VSPLIT) ? WSP_VERT : 0) == FAIL) /* Open in a new window */
return FAIL;
RESET_BINDING(curwin);
}
diff --git a/src/option.h b/src/option.h
index b031466..7c7d35a 100644
--- a/src/option.h
+++ b/src/option.h
@@ -765,12 +765,13 @@ EXTERN char_u *p_sws; /* 'swapsync' */
EXTERN char_u *p_swb; /* 'switchbuf' */
EXTERN unsigned swb_flags;
#ifdef IN_OPTION_C
-static char *(p_swb_values[]) = {useopen, usetab, split, newtab, NULL};
+static char *(p_swb_values[]) = {useopen, usetab, split, newtab, vsplit, NULL};
#endif
#define SWB_USEOPEN 0x001
#define SWB_USETAB 0x002
#define SWB_SPLIT 0x004
#define SWB_NEWTAB 0x008
+#define SWB_VSPLIT 0x010
EXTERN int p_tbs; /* 'tagbsearch' */
EXTERN long p_tl; /* 'taglength' */
EXTERN int p_tr; /* 'tagrelative' */
Re: [PATCH] fix asciidoc syntax highlight performance
On Monday, June 1, 2015 at 9:02:11 PM UTC+3, Christian Brabandt wrote: On Mo, 01 Jun 2015, Atte Peltomäki wrote: Vim includes AsciiDoc syntax highlight definition, but it's very, very slow. Fix attached. Disclaimer: I don't really understand what the removed options are for, but removing them fixes the issue without causing perceivable adverse effects. Thanks for the contribution. Please note, that runtime files are maintained by their maintainers, so the first step should always be to contact them first. They will send updates of the runtime files to Bram for inclusion with Vim. Added maintainer Stuart Rackham to Cc. -- -- 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.
