unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Cc: texinfo-pretest@texinfo.org
Subject: Re: A new online publishing tool for Texinfo   documents.
Date: Wed, 26 Nov 2003 11:37:55 -0700	[thread overview]
Message-ID: <3FC4F303.9040201@yahoo.com> (raw)
In-Reply-To: m1AOnQt-000UNaC@rattlesnake.com

Robert J. Chassell wrote:

[completely missing the point]


Nic said, "It's an additional format to solve the specific problem of reading
documentation that you don't happen to have on your local machine."

First of all, I question whether an additional format is required, since that
will demand that Emacs and other Info readers be modified to support the new
format.


Second, everyone seems to agree that Info's search and navigation facilities
are superior to HTML; so shouldn't we take advantage of that?

Third, Info files can be rendered very quickly (especially compared to HTML)
because they have already been pre-processed from the Texinfo source, but
the download time for Info is no worse than HTML because it's not much bigger
than the source.  So use a network transport that's likely to be supported
by a remote server like ftp or http, and be happy you've got access to remote
documentation at all.  Searching an entire document, whether it's in Info
format or HTML and whether it's a monolithic entity or split into pieces
still requires that the data be downloaded.  So download Info files as
needed, and cache them in the /tmp filesystem.

BTW, I just did `g (/@foo:/usr/local/info/gcc)Invoking GCC' and
was able to use the `i' and `s' commands just the way I expected.

What am I missing?  It seems to me different people are trying to solve
different problems within this single discussion thread.

-- 
Kevin Rodgers

  parent reply	other threads:[~2003-11-26 18:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-22 20:50 A new online publishing tool for Texinfo documents Nic Ferrier
2003-11-23 16:34 ` Richard Stallman
2003-11-23 16:56   ` Nic Ferrier
2003-11-25 18:36     ` Kevin Rodgers
2003-11-25 20:05       ` Nic Ferrier
2003-11-25 22:38         ` Kim F. Storm
2003-11-26  0:21       ` Robert J. Chassell
2003-11-26  6:25         ` Eli Zaretskii
2003-11-26 18:37         ` Kevin Rodgers [this message]
2003-11-26 21:36           ` Robert J. Chassell
2003-12-02 18:54             ` Kevin Rodgers
2003-12-02 21:56               ` Robert J. Chassell
2003-12-03  0:42                 ` Kevin Rodgers
  -- strict thread matches above, loose matches on Subject: below --
2003-11-22 21:18 Karl Berry
2003-11-22 21:37 ` Nic Ferrier
2003-11-24  7:57   ` Juri Linkov
2003-11-24  9:11     ` Nic Ferrier
2003-11-25  4:27       ` Richard Stallman
2003-11-25  7:52       ` Juri Linkov
2003-11-25 11:21         ` Kim F. Storm
2003-11-24 14:10     ` Karl Berry
2003-11-25 21:45       ` Juri Linkov
2003-11-24 16:22   ` Richard Stallman
2003-11-24 16:39     ` Nic Ferrier
     [not found] <200311222102.hAML20T05380@f7.net>
2003-11-23  9:16 ` Stepan Kasal
2003-11-23  9:28   ` Miles Bader
2003-11-23 12:33     ` Stepan Kasal
2003-11-23 21:19       ` Miles Bader
2003-11-24  8:57         ` Stepan Kasal
2003-11-25 13:58 Karl Berry

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=3FC4F303.9040201@yahoo.com \
    --to=ihs_4664@yahoo.com \
    --cc=texinfo-pretest@texinfo.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/emacs.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).