Archaic wrote these words on 06/30/05 11:57 CST: > Would there be any objections to creating a symlink or wrapper script > named spell that points to ispell? I don't know if the same would work > for aspell. Either that, or both LFS and BLFS could edit > /usr/share/vim/vim63/tools/vimspell.sh. > > I haven't investigated this yet. I just came across it while editing the > vimspell.sh description in LFS.
Having a symlink named spell matters not to me, however, I fail to see how this affects LFS. During an LFS install, Ispell is not installed, why make accommodations for something that doesn't exit. Furthermore, perhaps just a mention in the BLFS Vim instructions to move the vimspell.sh file into the path *and* create a symlink named spell (if Ispell is installed) would be more appropriate. Seeing how the vimspell.sh script can't be used unless it is placed in the path makes creating a symlink to 'spell' needless unless you first move the vimspell.sh script, or somehow else make it available in the path. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 12:15:00 up 89 days, 11:48, 2 users, load average: 0.22, 0.07, 0.02 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
