Re: update vim to 9.2.0161 (i know editors are supposed to do that, but someone totally forgot to update it)

"Bruce Dubbs" ([email protected] via blfs-dev Mailing List) <[email protected]> Sat, 21 Mar 2026 02:06:57 -0500
Newsgroups gmane.linux.lfs.beyond.devel
Message-ID <[email protected]>
This is a multi-part message in MIME format...

------------=_1774076827-1253-17621
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 3/20/26 10:53 PM, lfs ([email protected] via blfs-dev Mailing List) wrote:
> On Monday, March 16th, 2026 at 23:48, Zeckma <[email protected]> wrote:
>>
>> On 3/16/26 17:36, Hotdog wrote:
>>   > i sent this in blfs-dev, not lfs-dev
>>   > check the BLFS book vim is outdated
>>
>> My bad, I keep forgetting Vim is also in BLFS.
>> ...
> 
> Easy mistake to make.
> 
> I know it's been discounted, for a number of different reasons,
> on a few occasions over the years, but this issue should remind
> us that it is a bit of a shame that the LFS and BLFS Books still
> aren't being developed within, and rendered from, the same XML
> source tree, and appear as parts of a Set of Books.

We prefer to keep LFS manageable.  The LFS PDF is 336 pages and is
designed to be followed sequentially.

I did a recent PDF render of BLFS and it was 2216 pages.  It
is definitely not designed to be followed sequentially.  Specifically,
I think only (some) editors build everything in BLFS.

> Funnily enough, I have just seen a posting, on the systemd from
> scratch list, where Bruce postulates moving a couple of packages
> from the systemd from scratch Book into the BLFS Book, but notes
> that there'd be a lot of work to fix up the ID/XREF space, whereby
> references between the two standalone books are currently made via
> a URI targeting a "view" in the other Book's online rendering.
> 
> Always thought it was a bit perverse that, even if one had downloaded
> both the LFS and BLFS Books, switching between content in them required
> one to have an internet connection to the website.

There really is no way for a link in a static html page to know whether to
go to a website or a local system.  As long as the network is working,
the website is the better option.

   -- Bruce

------------=_1774076827-1253-17621
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page
------------=_1774076827-1253-17621--