[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: epub init file, and questions

From: Per Bothner
Subject: Re: epub init file, and questions
Date: Sun, 26 Dec 2021 12:18:18 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0

On 12/25/21 22:48, Eli Zaretskii wrote:

Your comments are all on-point, but I'll just add a few notes.

Date: Sat, 25 Dec 2021 11:44:34 -0800
From: Per Bothner <per@bothner.com>

Note that using eww-mode running in a terminal displays texi2any-generated
html work pretty decently, so that could potentially replace the
standalone info program, once we have an html-supporting info mode.

Two issues with this:

   . the stand-alone Info reader is a much leaner program than Emacs

Who cares? On modern computers, Emacs is relatively lean, and almost
everyone who would use 'info' is likely to have Emacs installed.
Using an emacs-server of course helps.

   . the eww mode is _slow_, especially on GUI displays, because it
     performs layout calculations in Lisp.  eww mode was never designed
     to handle large bodies of text.

It seems fast enough on my laptop.  (Though I notice an annoying bug,
in that eww doesn't seem to reflow on window resize.)

I also tried xwidget-webkit-browse-url, which worked pretty well,
and of course handles info.js as well.  That is of course less portable,
though Windows and MacOS have similar embeddable browsers.

To toot my own horn: if your terminal is DomTerm (https://domterm.org),
you can type:

  $ domterm --tab browse file:///path/to/manual.html
  $ domterm --above browse file:///path/to/manual.html

and new tab or pane is opened containing the manual.
        --Per Bothner
per@bothner.com   http://per.bothner.com/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]