unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: guix-devel@gnu.org
Subject: Re: Any interest in using HTML for locally-installed Texinfo documentation?
Date: Tue, 2 Apr 2019 17:58:51 -0500	[thread overview]
Message-ID: <daf42691-9d12-546a-42f4-40b172e1eb41@zoho.com> (raw)
In-Reply-To: <87d0m4ywyi.fsf@elephly.net>

El 2/04/19 a las 3:27 p. m., Ricardo Wurmus escribió:
> 
> Ricardo Wurmus <rekado@elephly.net> writes:
> 
>> Ludovic Courtès <ludo@gnu.org> 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 approach,
>>> and everything in JavaScript.  In an ideal world (for me), we’d rather
>>> provide a local documentation viewer that renders Texinfo directly.
>>
>> As far as I know GNOME’s Yelp is a frontend to different kinds of
>> documentation and it does support Info files.
>>
>> It may not work out of the box without setting some environment
>> variables first, but I remember viewing Info manuals in Yelp not too
>> long ago when I first learned that it supports Info.
> 
> It actually does seem to just work.  Try this:
> 
>     yelp info:guix


It works for me too (even searching). But I see some things missing,
although I'm using Yelp 3.18 from the host distro:

* Clicking any index result in an error:
   error on line 1114 at column 428: PCDATA invalid Char value 8
* Info manuals are not in the list of manuals available.

Being able to use Yelp would be great, in my opinion. After all, GNOME 
is the GNU Desktop.


-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.io/

  reply	other threads:[~2019-04-02 22:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 12:55 Any interest in using HTML for locally-installed Texinfo documentation? Gavin Smith
2019-04-01 14:01 ` sirgazil
2019-04-02  9:37 ` Ludovic Courtès
2019-04-02 15:02   ` Gavin Smith
2019-04-02 16:46     ` Per Bothner
2019-04-07 16:28       ` Gavin Smith
2019-04-08 15:12         ` Ludovic Courtès
2019-04-08 15:39           ` Pierre Neidhardt
2019-04-08 23:46           ` Gavin Smith
2019-04-09  6:25             ` Eli Zaretskii
2019-04-13 16:21           ` Gavin Smith
2019-04-14 19:25             ` Pronaip
2019-10-15 19:27             ` Gavin Smith
2019-10-15 20:20               ` P
2019-10-15 20:35                 ` Gavin Smith
2019-10-15 20:40                 ` Per Bothner
2019-10-15 21:00                   ` Gavin Smith
2019-10-15 21:09                     ` Per Bothner
2019-10-15 21:30                       ` Gavin Smith
2019-10-16  1:39               ` Ricardo Wurmus
2019-10-19 20:31               ` Ludovic Courtès
2019-10-22 19:00                 ` Gavin Smith
2019-10-22 20:18                   ` Gavin Smith
2019-11-03 14:04                   ` Ludovic Courtès
2019-11-03 15:37                     ` Gavin Smith
2019-11-06 21:49                       ` Ludovic Courtès
2019-04-03 21:21     ` Ludovic Courtès
2019-04-04 10:33       ` Gavin Smith
2019-04-02 15:31   ` Per Bothner
2019-04-03 21:11     ` Ludovic Courtès
2019-04-03 22:44       ` Per Bothner
2019-04-04 10:23       ` Gavin Smith
2019-04-04 16:02         ` Ludovic Courtès
2019-04-02 20:12   ` Ricardo Wurmus
2019-04-02 20:27     ` Ricardo Wurmus
2019-04-02 22:58       ` sirgazil [this message]
2019-04-02 22:10     ` Per Bothner
2019-04-02 23:09       ` sirgazil
2019-04-03  8:43         ` Gavin Smith
2019-04-03 14:23           ` sirgazil
2019-04-03 14:40             ` Per Bothner
2019-04-03 14:49       ` Ricardo Wurmus
2019-04-02 21:02 ` George Clemmer
2019-04-07 11:08   ` Gavin Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=daf42691-9d12-546a-42f4-40b172e1eb41@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).