]>
Commit | Line | Data |
---|---|---|
a2e11672 AG |
1 | To: vim_dev@googlegroups.com |
2 | Subject: Patch 7.3.231 | |
3 | Fcc: outbox | |
4 | From: Bram Moolenaar <Bram@moolenaar.net> | |
5 | Mime-Version: 1.0 | |
6 | Content-Type: text/plain; charset=UTF-8 | |
7 | Content-Transfer-Encoding: 8bit | |
8 | ------------ | |
9 | ||
10 | Note: this is a weird patch, it redoes patches from 7.3.202 and 7.3.203 | |
11 | that failed when applied as a patch, but the mercurial repository | |
12 | already had this, thus won't change anything there. | |
13 | ||
14 | ||
15 | Patch 7.3.231 | |
16 | Problem: Runtime file patches failed. | |
17 | Solution: Redo the patches made against the patched files instead of the | |
18 | files in the mercurial repository. | |
19 | Files: runtime/doc/indent.txt, runtime/doc/os_win32.txt | |
20 | ||
21 | ||
22 | *** ../vim-7.3.230/runtime/doc/indent.txt 2011-05-25 15:16:06.000000000 +0200 | |
23 | --- runtime/doc/indent.txt 2011-05-31 22:23:39.000000000 +0200 | |
24 | *************** | |
25 | *** 356,363 **** | |
26 | BaseClass(3) BaseClass(3) | |
27 | {} {} | |
28 | < | |
29 | ! +N Indent a continuation line (a line that spills onto the next) N | |
30 | ! additional characters. (default 'shiftwidth'). | |
31 | ||
32 | cino= cino=+10 > | |
33 | a = b + 9 * a = b + 9 * | |
34 | --- 357,368 ---- | |
35 | BaseClass(3) BaseClass(3) | |
36 | {} {} | |
37 | < | |
38 | ! *cino-+* | |
39 | ! +N Indent a continuation line (a line that spills onto the next) | |
40 | ! inside a function N additional characters. (default | |
41 | ! 'shiftwidth'). | |
42 | ! Outside of a function, when the previous line ended in a | |
43 | ! backslash, the 2 * N is used. | |
44 | ||
45 | cino= cino=+10 > | |
46 | a = b + 9 * a = b + 9 * | |
47 | *************** | |
48 | *** 509,522 **** | |
49 | --- 514,532 ---- | |
50 | } | |
51 | } | |
52 | < | |
53 | + *cino-)* | |
54 | )N Vim searches for unclosed parentheses at most N lines away. | |
55 | This limits the time needed to search for parentheses. (default | |
56 | 20 lines). | |
57 | ||
58 | + *cino-star* | |
59 | *N Vim searches for unclosed comments at most N lines away. This | |
60 | limits the time needed to search for the start of a comment. | |
61 | + If your /* */ comments stop indenting afer N lines this is the | |
62 | + value you will want to change. | |
63 | (default 70 lines). | |
64 | ||
65 | + *cino-#* | |
66 | #N When N is non-zero recognize shell/Perl comments, starting with | |
67 | '#'. Default N is zero: don't recognizes '#' comments. Note | |
68 | that lines starting with # will still be seen as preprocessor | |
69 | *** ../vim-7.3.230/runtime/doc/os_win32.txt 2010-08-15 21:57:16.000000000 +0200 | |
70 | --- runtime/doc/os_win32.txt 2011-05-28 18:17:58.000000000 +0200 | |
71 | *************** | |
72 | *** 313,318 **** | |
73 | --- 313,349 ---- | |
74 | with :!start do not get passed Vim's open file handles, which means they do | |
75 | not have to be closed before Vim. | |
76 | To avoid this special treatment, use ":! start". | |
77 | + There are two optional arguments (see the next Q): | |
78 | + /min the window will be minimized. | |
79 | + /b" no console window will be opened | |
80 | + You can only one of these flags at a time. A second second one will be | |
81 | + treated as the start of the command. | |
82 | + | |
83 | + Q. How do I avoid getting a window for programs that I run asynchronously? | |
84 | + A. You have two possible solutions depending on what exactly do you want: | |
85 | + 1) You may use the /min flag in order to run program in a minimized state | |
86 | + with no other changes. It will work equally for console and GUI | |
87 | + applications. | |
88 | + 2) You can use the /b flag to run console applications without creating a | |
89 | + console window for them (GUI applications are not affected). But you | |
90 | + should use this flag only if the application you run doesn't require any | |
91 | + input. Otherwise it will get an EOF error because its input stream | |
92 | + (stdin) would be redirected to \\.\NUL (stdoud and stderr too). | |
93 | + | |
94 | + Example for a console application, run Exuberant ctags: > | |
95 | + :!start /min ctags -R . | |
96 | + < When it has finished you should see file named "tags" in your current | |
97 | + directory. You should notice the window title blinking on your taskbar. | |
98 | + This is more noticable for commands that take longer. | |
99 | + Now delete the "tags" file and run this command: > | |
100 | + :!start /b ctags -R . | |
101 | + < You should have the same "tags" file, but this time there will be no | |
102 | + blinking on the taskbar. | |
103 | + Example for a GUI application: > | |
104 | + :!start /min notepad | |
105 | + :!start /b notepad | |
106 | + < The first command runs notepad minimized and the second one runs it | |
107 | + normally. | |
108 | ||
109 | Q. I'm using Win32s, and when I try to run an external command like "make", | |
110 | Vim doesn't wait for it to finish! Help! | |
111 | *** ../vim-7.3.230/src/version.c 2011-06-20 05:02:53.000000000 +0200 | |
112 | --- src/version.c 2011-06-26 03:14:03.000000000 +0200 | |
113 | *************** | |
114 | *** 711,712 **** | |
115 | --- 711,714 ---- | |
116 | { /* Add new patch number below this line */ | |
117 | + /**/ | |
118 | + 231, | |
119 | /**/ | |
120 | ||
121 | -- | |
122 | hundred-and-one symptoms of being an internet addict: | |
123 | 222. You send more than 20 personal e-mails a day. | |
124 | ||
125 | /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ | |
126 | /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ | |
127 | \\\ an exciting new programming language -- http://www.Zimbu.org /// | |
128 | \\\ help me help AIDS victims -- http://ICCF-Holland.org /// |