Changeset 8be8228
- Timestamp:
- 02/12/2007 03:03:11 AM (17 years ago)
- Branches:
- 6.2, 6.2.0
- Children:
- 22845f9
- Parents:
- e726c165
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
general.ent
re726c165 r8be8228 4 4 --> 5 5 6 <!ENTITY day "1 0"> <!-- Always 2 digits -->6 <!ENTITY day "11"> <!-- Always 2 digits --> 7 7 <!ENTITY month "02"> <!-- Always 2 digits --> 8 8 <!ENTITY year "2007"> -
introduction/welcome/changelog.xml
re726c165 r8be8228 43 43 44 44 <listitem> 45 <para>February 11th, 2007</para> 46 <itemizedlist> 47 <listitem> 48 <para>[dnicholson] - Add information for running the Vim 49 testsuite. Patch from Ag Hatzimanikas.</para> 50 </listitem> 51 </itemizedlist> 52 </listitem> 53 54 <listitem> 45 55 <para>February 10th, 2007</para> 46 56 <itemizedlist> -
postlfs/editors/vim.xml
re726c165 r8be8228 4 4 <!ENTITY % general-entities SYSTEM "../../general.ent"> 5 5 %general-entities; 6 7 <!-- Inserted as a reminder to do this. The mention of a test suite8 is usually right before the root user installation commands. Please9 delete these 12 (including one blank) lines after you are done.-->10 11 <!-- Use one of the two mentions below about a test suite,12 delete the line that is not applicable. Of course, if the13 test suite uses syntax other than "make check", revise the14 line to reflect the actual syntax to run the test suite -->15 16 <!-- <para>This package does not come with a test suite.</para> -->17 <!-- <para>To test the results, issue: <command>make check</command>.</para> -->18 6 19 7 <!ENTITY vim-download-http "http://ftp.at.vim.org/pub/vim/unix/vim-&vim-version;.tar.bz2"> … … 140 128 make</userinput></screen> 141 129 130 <para>To test the results, issue: <command>make test</command>. 131 The <application>vim</application> test suite outputs a lot of binary 132 data to the screen, which can cause issues with the settings of the 133 current terminal. This can be resolved by redirecting the output to a 134 log file. Even if one of the tests fails to produce the file 135 <filename>test.out</filename> in <filename 136 class="directory">src/testdir</filename>, the remaining tests will still 137 be executed. If all goes well,the final message in the log file will be 138 <literal>ALL DONE</literal>. <emphasis>Note</emphasis>: Some color tests 139 expect to be executed under the <command>xterm</command> terminal 140 emulator.</para> 141 142 142 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 143 143
Note:
See TracChangeset
for help on using the changeset viewer.