Re: [Lynx-dev] lynx.cfg - mime types - viewer for text terminal audio player mpg123
Klaus-Peter Wegge wrote:
> It's in the PATH and full path spec doesn't make a difference.
> But the change in .mailcap is a work arround.
> audio/mpeg; mpg123 -v %s
>
> The VIEWER definition seems to check for the
> DISPLAY env. It's set to DISPLAY=0
> May be there is something wrong with the VIEWER defintion.
As a general troubleshooting technique for this sort of thing, run:
$ strace -e trace=file -s250 -f -o lynx.strace lynx [url]
... then Do The Thing which ends up in running the wrong viewer. Then
look inside lynx.strace. Start by truncating it at the point where it
runs the wrong viewer, since it has with 100% certainty already picked
up the wrong info before that point. Then look for it accessing other
files with names like 'mime.types' or 'mailcap', anywhere in the
filesystem.
You may see ENOENT -- attempts to open files which turn out not to
exist. These might seem like useless noise, but in fact show you the
exact path of files it *tried* to use. These will of course include the
one with the unwanted viewer info; they may also point out other points
of leverage -- files it fails to open, but which you could create so
that next time it succeeds and gets the settings you want.
Overall, you should learn of (1) system files which you as admin could
edit, (2) own files which you could edit, (3) possibly, other places it
looks, which you could create to give you additional points of leverage.
Trying on my system, I got (heavily truncated trace output):
open("/etc/mailcap")
lstat("~/.mailcap")
open("~/.mailcap")
open("~/.mailcap") (yes, twice)
open("/etc/mime.types")
lstat("~/.mime.types") = -1 ENOENT
-- showing that I could add a personal .mime.types if needed for
override purposes.
>Bela<
PS: there is also `lynx -trace`, which very likely would lead to the
same discoveries. But is program-specific, so less generally helpful to
learn. It would certainly be the right thing to look at if you were
e.g. trying to understand some mis-parsing of HTML; but for questions
about what files it accesses, probably not the best tool.
Re: [Lynx-dev] Adding a style
On Wed, Apr 03, 2024 at 11:08:42AM -0600, rbell--- via Lynx-dev wrote: > > Quoth mouse: > > 'since there is a spec, there is a well-defined "correct", at > least to the extent that the spec is properly done.' > > Quoth https://www.w3.org/Library/src/HTStyle.html (the spec): > 'The manager doesn't contain any styles - it only provides a > mechanism for registering styles, looking them up and deleting them. > That is, it doesn't have any idea of what a style actually looks like > - as this is highly application dependent,' to cook: just add water :-) > It points to an HTStyle.c from 'W3C Sample Code Library' which > is a lot different from lynx's. lynx uses an _early_ version of libwww It was discussed long ago (in the 1990s) whether to use a newer version. As I recall it, it would have been a lot of (re)work which no one did. (Look for "libwww" in the mailing list archives) -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Re: [Lynx-dev] editors and spell checking?
Well, I am not sure if only NANO has "search-and-replace"? I like some specific options, so I alias nano -tzxk as I like cut from cursor, also suspend, which they've made more of a challenge. And some items I put in a nanorc Chime
Re: [Lynx-dev] editors and spell checking?
I have no idea if pico had a configuration file or not, but I never use one, just use the default mode of the editors, and it's always worked exactly the same for me without having to do anything at all. As I said, (and as you seem to indicate), if there's a difference, it's because her host made a change, not because the program changed. On 4/3/2024 11:45 AM, Jude DaShiell wrote: Did pico have a configuration file? Nano has nano.conf available for use. -- Jude "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Wed, 3 Apr 2024, tsie...@softcon.com wrote: Pico and nano are basically the same editor, just a later version, (you know, pico is version 1.0, nano is version 2.0). The way to run aspell or spell is exactly the same regardless of the name of the editor in this case. ctrl-t asks you what program to run, type spell or aspell, depending on what you have installed, and you're all done. That's all there is to it. And, just for reference, Nano uses the same exact keystrokes as pico, I know, because I used pico for years before it got switched to nano, and I've not changed a single thing in how I use the program, and it still does everything exactly the same as it did before. No difference. On 4/2/2024 11:25 PM, Karen Lewellen wrote: apparently? There is more to this solution, at least where the speller is concerned. the editor in lynx in use is pico..cannot fault them there, I prefer it to nano as well. Alpine in their setup is using aspell for spell checking, so they want to add this on the editor line. Pico runs fine by itself when added to the editor line in the lynx options menu. but it does not seem to provide things like alternative words, or look up or anything as if a speller was in use...meaning something else is required. Apparently adding the line as it appears in the alpine setup screen is not working either. Does pico need a configuration file to run with a spell checker? thanks, Karen On Tue, 2 Apr 2024, Tim Chase wrote: Replying inline On 2024-04-02 15:33, Karen Lewellen wrote: I am helping someone resolve an issue, they have access to lynx, but the editor field is blank. They are using Ubuntu. If they're already comfortable with a preferred editor, you can tell Lynx to use that on the command-line with the "-editor" option: $ lynx -editor=/usr/bin/nano http://example.com They might even have configured their system to use "sensible-editor" in which case $ lynx -editor=/usr/bin/sensible-editor http://example.com should invoke their preferred editor. Alternatively, you can use "o" to go to the lynx options, check the "Save options to disk" checkbox, set the Editor value in there, and save the options. Strangely, lynx doesn't honor the common method of setting either the $EDITOR or $VISUAL environment variable. In alpine for example there is a field for editor, and one for spell checking, I admit to thinking they worked together as in are software dependent. They can be the same thing or they can be different tools. Some editors have spell-check support, some don't; so you might want an external spell-checker. Does lynx work the same? meaning does there need to be one field for the editor and one for spell checker? I don't think lynx has anything spell-checking-related, just editor-related. However, if they use an editor with built-in spell-checking, that would do the trick. or is it enough to make sure the chosen editor is configured to use the desired spell checker. meaning adding the editor will allow for spell checking as well? I believe this is the case. I know that vim and emacs both have support for spell-checking. And nano does too if you enable it and add a spell-checking package: $ sudo apt-get install spell With the spell-checker installed, you should be able to use control+t in nano to spell-check the file. Hopefully that helps, -tim
Re: [Lynx-dev] editors and spell checking?
Karen. Any differences you're experiencing between pico and nano are purely a difference of configuration. By default, they there is absolutely no difference between the two. In fact, if it wasn't for the name of the program being shown on the screen when you run it, I'd challenge anyone to tell the difference. Like I said, I've been running linux boxes since the early 90s, and I've changed absolutely nothing between the time when the default was pico, and the time it switched to nano, and I do absolutely nothing different now that I did then, and everything still works exactly the same for me. If your copy is acting different, then I suggest you complain to your ISP, because that means they changed something, especially the whole starting at the end of the document, because my versions have never done that. On 4/3/2024 1:50 AM, Karen Lewellen wrote: My pico is edition 5.0 plus. Pico is more flexible, speaking personally. nano, again speaking personally makes odd choices, like going to the end of a a document. The recent nano on the Ubuntu setup for dreamhost no longer even uses the control t for spell checking. Personal preferences are the soul of personal computing laughs. On Wed, 3 Apr 2024, tsie...@softcon.com wrote: Pico and nano are basically the same editor, just a later version, (you know, pico is version 1.0, nano is version 2.0). The way to run aspell or spell is exactly the same regardless of the name of the editor in this case. ctrl-t asks you what program to run, type spell or aspell, depending on what you have installed, and you're all done. That's all there is to it. And, just for reference, Nano uses the same exact keystrokes as pico, I know, because I used pico for years before it got switched to nano, and I've not changed a single thing in how I use the program, and it still does everything exactly the same as it did before. No difference. On 4/2/2024 11:25 PM, Karen Lewellen wrote: apparently? There is more to this solution, at least where the speller is concerned. the editor in lynx in use is pico..cannot fault them there, I prefer it to nano as well. Alpine in their setup is using aspell for spell checking, so they want to add this on the editor line. Pico runs fine by itself when added to the editor line in the lynx options menu. but it does not seem to provide things like alternative words, or look up or anything as if a speller was in use...meaning something else is required. Apparently adding the line as it appears in the alpine setup screen is not working either. Does pico need a configuration file to run with a spell checker? thanks, Karen On Tue, 2 Apr 2024, Tim Chase wrote: > Replying inline > > On 2024-04-02 15:33, Karen Lewellen wrote: > > I am helping someone resolve an issue, they have access to lynx, but > > the > > editor field is blank. > > They are using Ubuntu. > > If they're already comfortable with a preferred editor, you can > tell Lynx to use that on the command-line with the "-editor" option: > > $ lynx -editor=/usr/bin/nano http://example.com > > They might even have configured their system to use "sensible-editor" > in which case > > $ lynx -editor=/usr/bin/sensible-editor http://example.com > > should invoke their preferred editor. > > Alternatively, you can use "o" to go to the lynx options, check the > "Save options to disk" checkbox, set the Editor value in there, and > save the options. > > Strangely, lynx doesn't honor the common method of setting either > the $EDITOR or $VISUAL environment variable. > > > In alpine for example there is a field for editor, and one for spell > > checking, I admit to thinking they worked together as in are software > > dependent. > > They can be the same thing or they can be different tools. Some > editors have spell-check support, some don't; so you might want an > external spell-checker. > > > Does lynx work the same? meaning does there need to be one field > > for the editor and one for spell checker? > > I don't think lynx has anything spell-checking-related, just > editor-related. However, if they use an editor with built-in > spell-checking, that would do the trick. > > > or is it enough to make sure the chosen editor is configured > > to use the desired spell checker. meaning adding the editor will > > allow for spell checking as well? > > I believe this is the case. I know that vim and emacs both have > support for spell-checking. And nano does too if you enable it and > add a spell-checking package: > > $ sudo apt-get install spell > > With the spell-checker installed, you should be able to use control+t > in nano to spell-check the file. > > Hopefully that helps, > > -tim > > > > > > >
Re: [Lynx-dev] Adding a style
Quoth mouse: 'since there is a spec, there is a well-defined "correct", at least to the extent that the spec is properly done.' Quoth https://www.w3.org/Library/src/HTStyle.html (the spec): 'The manager doesn't contain any styles - it only provides a mechanism for registering styles, looking them up and deleting them. That is, it doesn't have any idea of what a style actually looks like - as this is highly application dependent,' It points to an HTStyle.c from 'W3C Sample Code Library' which is a lot different from lynx's. russell bell
Re: [Lynx-dev] Adding a style
> 'That's correct for s in general' > There is no correct. I decide what I want. How do I add a style? Well, since there is a spec, there is a well-defined `correct', at least to the extent that the spec is properly done. (I don't know the spec well enough myself to know what it says is correct for s in general.) That said, you are of course welcome to arrange for the software you run to interpret HTML (or anything else) any way you please, regardless of any specs. But don't be surprised if others are uninterested (in using it, in helping you arrange it, in interoperating with it, whatever). No, I don't know how to add a style to lynx. I'd probably do more or less what it sounded as though you did, then treat the crashes you described as a bug to be debugged. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTMLmo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Re: [Lynx-dev] Adding a style
'That's correct for s in general' There is no correct. I decide what I want. How do I add a style? You un-answered my question, a waste of everyone's time. russell bell
Re: [Lynx-dev] Adding a style
rbell--- via Lynx-dev dixit: > NEJM has started using to demarcate the >beginning of a paragraph. lynx renders this the same as , which >makes it hard to read. That’s correct for s in general, though: upon encountering the start tag, if not at column 1, emit a newline. Tell NEJM to use the p tag instead. bye, //mirabilos -- 22:20⎜ The crazy that persists in his craziness becomes a master 22:21⎜ And the distance between the craziness and geniality is only measured by the success 18:35⎜ "Psychotics are consistently inconsistent. The essence of sanity is to be inconsistently inconsistent
[Lynx-dev] Adding a style
NEJM has started using to demarcate the beginning of a paragraph. lynx renders this the same as , which makes it hard to read. I tried to add a new style, ST_Div, in WWW/Library/Implementation/HTStyle.h and rely on the fall-through handling of div in src/HTML.c and src/LYCharUtils.c but the lynx I build crashes. russell bell
Re: [Lynx-dev] editors and spell checking?
Did pico have a configuration file? Nano has nano.conf available for use. -- Jude "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Wed, 3 Apr 2024, tsie...@softcon.com wrote: > Pico and nano are basically the same editor, just a later version, (you know, > pico is version 1.0, nano is version 2.0). > > The way to run aspell or spell is exactly the same regardless of the name of > the editor in this case. > > ctrl-t asks you what program to run, type spell or aspell, depending on what > you have installed, and you're all done. > > That's all there is to it. > > And, just for reference, Nano uses the same exact keystrokes as pico, I know, > because I used pico for years before it got switched to nano, and I've not > changed a single thing in how I use the program, and it still does everything > exactly the same as it did before. > > No difference. > > > On 4/2/2024 11:25 PM, Karen Lewellen wrote: > > apparently? > > There is more to this solution, at least where the speller is concerned. > > the editor in lynx in use is pico..cannot fault them there, I prefer it to > > nano as well. > > Alpine in their setup is using aspell for spell checking, so they want to > > add this on the editor line. > > Pico runs fine by itself when added to the editor line in the lynx options > > menu. but it does not seem to provide things like alternative words, or > > look up or anything as if a speller was in use...meaning something else is > > required. > > Apparently adding the line as it appears in the alpine setup screen is not > > working either. > > Does pico need a configuration file to run with a spell checker? > > thanks, > > Karen > > > > > > On Tue, 2 Apr 2024, Tim Chase wrote: > > > >> Replying inline > >> > >> On 2024-04-02 15:33, Karen Lewellen wrote: > >>> I am helping someone resolve an issue, they have access to lynx, but the > >>> editor field is blank. > >>> They are using Ubuntu. > >> > >> If they're already comfortable with a preferred editor, you can > >> tell Lynx to use that on the command-line with the "-editor" option: > >> > >> $ lynx -editor=/usr/bin/nano http://example.com > >> > >> They might even have configured their system to use "sensible-editor" > >> in which case > >> > >> $ lynx -editor=/usr/bin/sensible-editor http://example.com > >> > >> should invoke their preferred editor. > >> > >> Alternatively, you can use "o" to go to the lynx options, check the > >> "Save options to disk" checkbox, set the Editor value in there, and > >> save the options. > >> > >> Strangely, lynx doesn't honor the common method of setting either > >> the $EDITOR or $VISUAL environment variable. > >> > >>> In alpine for example there is a field for editor, and one for spell > >>> checking, I admit to thinking they worked together as in are software > >>> dependent. > >> > >> They can be the same thing or they can be different tools. Some > >> editors have spell-check support, some don't; so you might want an > >> external spell-checker. > >> > >>> Does lynx work the same? meaning does there need to be one field > >>> for the editor and one for spell checker? > >> > >> I don't think lynx has anything spell-checking-related, just > >> editor-related. However, if they use an editor with built-in > >> spell-checking, that would do the trick. > >> > >>> or is it enough to make sure the chosen editor is configured > >>> to use the desired spell checker. meaning adding the editor will > >>> allow for spell checking as well? > >> > >> I believe this is the case. I know that vim and emacs both have > >> support for spell-checking. And nano does too if you enable it and > >> add a spell-checking package: > >> > >> $ sudo apt-get install spell > >> > >> With the spell-checker installed, you should be able to use control+t > >> in nano to spell-check the file. > >> > >> Hopefully that helps, > >> > >> -tim > >> > >> > >> > >> > >> > >> > >> > > > > >
