On Sat, Feb 19, 2005, Ralf S. Engelschall wrote:

> On Sat, Feb 19, 2005, Matthias Kurz wrote:
> 
> > On Sat, Feb 19, 2005, Ralf S. Engelschall wrote:
> >
> > > On Sat, Feb 19, 2005, Matthias Kurz wrote:
> > >
> > > > I would prefer HTML-docs (->texi2html).
> > >
> > > With the regular info(1) command the .info files are fully useless IMHO.
> > > But with pinfo(1) (see our "pinfo" package) they are as good to read as
> > > the results from texi2html are with w3m(1).
> >
> > Well, i did not read your last sentence carefully enough. Thought, you
> > meaned, that w3m has special info support.
> > Does this mean, you use w3m as your preferred browser ?
> 
> For reading HTML documentation files on my filesystem, yes.
> For reading HTML pages on the Web I also use Mozilla, of course.

Well, there will be more and more graphics... I use Mozilla also for local
files. Why use different tools for the same work ?
I still use mutt, to read my mails, though :-) Or vi (or emacs/viper) and
less. But this works only, because i use it locally. Using text based tools
with a "rich" interface (even less, vi, mutt) remotely can fast become a
horror szenario. Especially in heterogenous environments. "xterm" is by far
not "xterm" on every machine. I'm often near an heart attack, i.e. when i
log in from a Solaris machine to a Linux machine (Solaris xterm) and try
to use less or vi on the remote machine.
I prefer to read documentations in my browser (no PDF, either, thanks).
Apart from the easier remote access, there are other advantages like
indexing, bookmarks, forking multiple windows/tabs, navigation between
different documentations (not all come with .info docs and even text
only docs look acceptable in a browser), quick side steps in the global
WWW...
Well, this holds at least for the more detailed docs. I still prefer a clean
and concise man page with some nice, short examples over most.


   (mk)

-- 
Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47
  >> Im prämotorischen Cortex kann jeder ein Held sein. (bdw) <<
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   openpkg-dev@openpkg.org

Reply via email to