Changeset 83d6546


Ignore:
Timestamp:
02/12/2007 02:58:24 AM (17 years ago)
Author:
Dan Nichilson <dnicholson@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
e83c2d1
Parents:
609fcf0
Message:

Vim testsuite info

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@6603 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:
3 edited

Legend:

Unmodified
Added
Removed
  • general.ent

    r609fcf0 r83d6546  
    44-->
    55
    6 <!ENTITY day          "10">                   <!-- Always 2 digits -->
     6<!ENTITY day          "11">                   <!-- Always 2 digits -->
    77<!ENTITY month        "02">                   <!-- Always 2 digits -->
    88<!ENTITY year         "2007">
  • introduction/welcome/changelog.xml

    r609fcf0 r83d6546  
    4141
    4242-->
     43
     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>
    4353
    4454    <listitem>
  • postlfs/editors/vim.xml

    r609fcf0 r83d6546  
    44  <!ENTITY % general-entities SYSTEM "../../general.ent">
    55  %general-entities;
    6 
    7     <!-- Inserted as a reminder to do this. The mention of a test suite
    8          is usually right before the root user installation commands. Please
    9          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 the
    13          test suite uses syntax other than "make check", revise the
    14          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> -->
    186
    197  <!ENTITY vim-download-http "http://ftp.at.vim.org/pub/vim/unix/vim-&vim-version;.tar.bz2">
     
    140128make</userinput></screen>
    141129
     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
    142142    <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
    143143
Note: See TracChangeset for help on using the changeset viewer.