From: Per Bothner <bothner@cygnus.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: egcs@cygnus.com
Subject: Re: [OFFTOPIC] Info files vs Man pages
Date: Wed, 16 Sep 1998 22:59:00 -0000 [thread overview]
Message-ID: <199809161850.LAA06213@cygnus.com> (raw)
In-Reply-To: <199809161821.LAA22292@atrus.synopsys.com>
> Waste of time. Extend Lynx if necessary (Lynx is under the GPL).
OK, I wasn't sure about that.
> I can't think of anyone who prefers the standalone info browser
> to Lynx that has used both.
I have used both and prefer info, perhaps mainly because I use info a
lot more.
However, a few tweaks to lynx would help. Mainly, if it could be
more intelligent about the navigation, and recognize the various
<link> tags texi2html emits, I think it would be nicer. I do
like the "intelligent space" command of info mode, and
I would like that for lynx. Having that, plus searching,
would help convince peopel to switch. (A traditional info-compatible
user interface *option* would also help us old-time info users.)
> Millions of people use HTML tools; hardly anyone uses info tools.
> Given this, you don't bend the HTML tools to look like info tools;
> rather you make the info data accessible to the HTML users.
I think that is a bogus point - "hardly anyone" uses lynx,
compared to the millions who point-and-click. I think we
can tweak the lynx interface, adding the best features of info,
and come up with something quite nice.
> The only extension that people have been asking for is the ability to
> search across multiple files; it would be possible to come up a convention
> to use META tags for this purpose (to mark the URL corresponding to
> the next file).
Well, if you look at texi2html-generated html, you will find it does
emit navigation information in the links:
http://www.cygnus.com/~bothner/kawa/kawa_2.html:
<HTML>
<HEAD>
<!-- This HTML file has been created by texi2html 1.54
from kawa.texi on 20 March 1998 -->
<TITLE>Kawa, the Java-based Scheme system - Features</TITLE>
<link href="kawa_3.html" rel=Next>
<link href="kawa_1.html" rel=Previous>
<link href="kawa_toc.html" rel=ToC>
</HEAD>
<BODY>
<p>Go to the <A HREF="kawa_1.html">first</A>, <A HREF="kawa_1.html">previous</A>
, <A HREF="kawa_3.html">next</A>, <A HREF="kawa_11.html">last</A> section, <A HR
EF="kawa_toc.html">table of contents</A>.
<P><HR><P>
--Per Bothner
Cygnus Solutions bothner@cygnus.com http://www.cygnus.com/~bothner
next prev parent reply other threads:[~1998-09-16 22:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-14 14:04 Alex Buell
1998-09-14 21:49 ` Joe Buck
1998-09-15 14:14 ` Dave Love
1998-09-15 14:14 ` Alex Buell
1998-09-16 11:34 ` Dave Love
1998-09-16 21:52 ` Joe Buck
1998-09-17 9:59 ` Dave Love
1998-09-15 1:12 ` Jeffrey A Law
1998-09-15 8:17 ` Alex Buell
1998-09-16 3:07 ` Kamil Iskra
1998-09-16 3:07 ` Alex Buell
1998-09-16 11:34 ` Per Bothner
1998-09-16 21:52 ` Joe Buck
1998-09-19 12:03 ` Dave Love
1998-09-21 9:44 ` Joe Buck
1998-09-17 9:59 ` Andreas Schwab
1998-09-17 9:59 ` Alex Buell
1998-09-19 12:03 ` Dave Love
1998-09-19 18:47 ` Alex Buell
1998-09-25 10:17 ` Nicholas J. Leon
1998-09-25 19:05 ` Alex Buell
1998-09-25 22:53 ` Scott A Crosby
1998-09-15 18:39 ` Dave Love
1998-09-15 19:05 ` Carlo Wood
1998-09-15 19:05 ` Jeffrey A Law
1998-09-16 3:04 ` Per Bothner
1998-09-16 22:59 ` Joe Buck
1998-09-16 22:59 ` Per Bothner [this message]
1998-09-16 22:55 ` Joe Buck
1998-09-17 11:14 ` Dave Love
1998-09-16 21:52 ` Joe Buck
1998-09-19 12:03 ` Dave Love
[not found] ` <rzqg1dodknl.fsf.cygnus.egcs@djlvig.dl.ac.uk>
1998-09-21 14:55 ` Jason Merrill
1998-09-22 14:12 ` Dave Love
1998-09-15 7:06 ` Clayton Weaver
1998-09-15 11:28 ` Alex Buell
1998-09-15 13:47 ` Tim Waugh
1998-09-15 14:14 ` Joern Rennecke
1998-09-16 1:48 ` Andreas Schwab
1998-09-17 10:03 David Ross
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199809161850.LAA06213@cygnus.com \
--to=bothner@cygnus.com \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.com \
/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.
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).