[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] lynx and ruby, '*.rb' files

From: Steffen Nurpmeso
Subject: Re: [Lynx-dev] lynx and ruby, '*.rb' files
Date: Sat, 15 Aug 2020 19:39:03 +0200
User-agent: s-nail v14.9.19-103-ga01f6c13 wrote in
 | Quoth Mike McClain:
 | 'As per your suggestion I put this in ~/.mailcap:
 | text/plain; cat %s; copiousoutput'
 |The first field (the part before ;) identifies the type of file.  This
 |entry instructs mail (and lynx) how to treat 'text/plain' files, not
 |ruby files.
 | 'When that didn't help I created ~/.lynxcap with the same
 | .lynxcap is my invention.  To get lynx to use it one must add:
 | PERSONAL_MAILCAP:~/.lynxcap
 |to lynx.cfg; lynx uses .mailcap by default.

Not that it matters, but RFC 1524 specifies $MAILCAPS with
a default of


where this is not a search path, but a path search (they can

 | 'Reading up on mailcap led to mime.types and in /etc/mime.types
 |commenting out this line:
 |    #application/x-ruby                             rb
 |allowed lynx to open ruby source files.'

Mysterious, shouldn't that be text/x-ruby.  That is what i use,
and what is found a lot on the web.  In general i totally dislike
the missings standards which require so many x- things, and that
we have quite a lot of application/ things where this is not truly
useful, say x-sh (doh), but x-awk, x-perl, x-java, and more of
this sort.

 | Lines that begin with # are comments, not acted upon.  I would
 |have tried:
 | text/rb;     less %s

This requires an explicit temporary file, whereas

  text/x-ruby; less

would/should not.

|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]