Re: forcing html rendering for files without extensions
rbell--- via Lynx-dev <[email protected]>
| Newsgroups | gmane.comp.web.lynx.devel |
|---|---|
| Message-ID | <[email protected]> |
Quoth Mouse: 'Well...keying things off filename extensions is a useful heuristic. But there is a problem with it, more or a problem in the abstract than a pragmatic problem: what is an extension?...' lynx keys off them. (lynx calls them suffixes but they're the same thing). emacs does too, and has the problem you outlined. Theoretically one could add a handler for no suffix to lynx.cfg as one does for all the other extensions - why not for no extension? Quoth Thorsten Glaser: 'I think lynx shouldn't change what it already does, to default to plaintext, but making the backslash into a toggle *towards* HTML for files rendered as plaintext is a good idea.' I think that's a lot of work. Hitting backslash to see a plaintext file as plaintext isn't. russell bell