#2262: Vim instructions have an error
----------------------------------------+-----------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  [email protected]
     Type:  defect                      |       Status:  reopened               
      
 Priority:  normal                      |    Milestone:  6.4                    
      
Component:  Book                        |      Version:  SVN                    
      
 Severity:  normal                      |   Resolution:                         
      
 Keywords:                              |  
----------------------------------------+-----------------------------------
Comment (by Bryan Kadzban):

 OK, I figured that was the idea, but it helps to know for sure.  Thanks!

 Something like this should work as well then (it also makes it a bit more
 explicit what the critical part is: the existence of man1/vim.1 under the
 language directory):

 {{{
 for i in /usr/share/man/*/man1/vim.1 ; do
   ln -s vim.1 $(dirname $i)/vi.1
 done

 ln -s vim.1 /usr/share/man/man1/vi.1
 }}}

 That way we don't end up missing future vim.1 pages in different
 directories.

 I did, however, think up another solution to this whole loop thing late
 last night (and forgot about it until now):  depending on whether man-db
 re-searches the man directories when it sees a ".so" include, it may work
 to create a simple vi.1 wrapper:

 {{{
 echo '.so man1/vim.1' >/usr/share/man/man1/vi.1
 }}}

 But I have not tested this.  I don't know if that .so will cause man-db to
 include ru.UTF-8/man1/vim.1 if that's your locale, for instance, or if it
 will use the unlocalized /usr/share/man/man1/vim.1 file instead.  The
 latter would be bad (or at least, worse than the fixed loop).

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2262#comment:11>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to