El 2/04/19 a las 5:10 p. m., Per Bothner escribió:
On 4/2/19 1:12 PM, Ricardo Wurmus wrote:
As far as I know GNOME’s Yelp is a frontend to different kinds of
documentation and it does support Info files.
That reads *info* files. We're talking about reading *html* files.
See Gavin's original m
Hello,
Per Bothner writes:
> On 1/28/19 12:05 PM, Gavin Smith wrote:
>> On Tue, Jan 01, 2019 at 05:46:11PM -0800, Per Bothner wrote:
>>
>> diff --git a/js/info.js b/js/info.js
>> index 10a2b1d..0175d35 100644
>> --- a/js/info.js
>> +++ b/js/info.js
>> @@ -1170,7 +1170,7 @@
>> if (linkid
On 4/2/19 1:12 PM, Ricardo Wurmus wrote:
As far as I know GNOME’s Yelp is a frontend to different kinds of
documentation and it does support Info files.
That reads *info* files. We're talking about reading *html* files.
See Gavin's original message for why we want to use html.
--
--Per
Hi Gavin,
Gavin Smith writes:
[...]
> A manual with this interface added is at
> https://www.gnu.org/software/texinfo/manual/texinfo-html/Overview.html.
> All the important keyboard commands that work in the Info viewers are
> implemented, including index lookup.
Nice! I like seeing Info command
Ludovic Courtès writes:
> I hear the argument; it’s true that not everyone uses Emacs or is
> familiar with the standalone Info reader. Rendering of Info manuals in
> Emacs is not bad, but a modern browser can do a better job.
>
> Yet I’m not completely sold to the everything in the browser ap
Ricardo Wurmus writes:
> Ludovic Courtès writes:
>
>> I hear the argument; it’s true that not everyone uses Emacs or is
>> familiar with the standalone Info reader. Rendering of Info manuals in
>> Emacs is not bad, but a modern browser can do a better job.
>>
>> Yet I’m not completely sold to
On 4/2/19 8:02 AM, Gavin Smith wrote:
Using JavaScript within a web browser has big drawbacks due to its
"sandboxed" nature. (You can't access environment variables, for
example.) However, we'd want to avoid having to re-implement too much
of the web browser; for example, input file parsing, te
On 4/2/19 2:37 AM, Ludovic Courtès wrote:
Yet I’m not completely sold to the everything in the browser approach,
and everything in JavaScript. In an ideal world (for me), we’d rather
provide a local documentation viewer
I don't think we're aiming for "everything in the browser". A closer
app
On Tue, Apr 02, 2019 at 11:37:51AM +0200, Ludovic Courtès wrote:
> (For some reason ‘i’ does open the index search box for me, but then
> hitting enter doesn’t produce any effect. The other navigation commands
> work fine, though.)
It works on Firefox 53, at least.
> Yet I’m not completely sold
Hello Gavin,
Gavin Smith skribis:
> Documentation for GNU packages and others is often installed in the
> Info format, a plain text format. Using a plaintext based format for
> documentation does not take advantage of bitmapped displays that have
> been available for decades. It does not allow
10 matches
Mail list logo
