[Top][All Lists]

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

Re: lynx-dev External Mail programs

From: asgilman
Subject: Re: lynx-dev External Mail programs
Date: Fri, 31 Dec 1999 19:57:49 -0500 (EST)

>                      Re: lynx-dev External Mail programs
>     _________________________________________________________________
>     * Subject: Re: lynx-dev External Mail programs
>     * From: "Eduardo Chappa L." <address@hidden>
>     * Date: Wed, 29 Dec 1999 22:30:36 -0800 (PST)
>     * In-Reply-To: <address@hidden>
>     _________________________________________________________________
>*** Henry Nelson wrote in the Lynx list on Dec 30, 1999:
>:) Does mime treatment of file extensions, ".gif" and ".pdf," have anything to
>:) do with a protocol, "mailto:";?
>No it does not, but the point is that there are many ways to treat
>different choices, It is my opinion that anything which is not
>[12] should be treated in special ways. mailto: can be
>treated by opening an external mail program, like you do with any of your
>other choices. In another words, what I am saying is that there is no need
>for the external command, maybe all this is leading to the external
>command being associated with the return key (too).

Henry, I think that what you don't want is a bigger executable, no?

Making the mailer optionable, as the editor is now, does not require including 
all that mailer code in the Lynx executable.

As far as the UI is concerned, I tend to agree with Eduardo that it would
be more logical if mailto: could be bound to an external call by extension,
just as display of MIME types is helped by extensions.

IIRC the problem was that this change is not localized in the code,
and nobody wanted to
take on a job of that size, so we have been using the EXTERNAL approach 
which is, from the user perspective, a dab more busywork than is really
necessary.  I could be confusing this with background downloads.


>:) > text/html files that are e-mailed to you. I do not see why you have to
>:) > insist that there should be just one and only one way to open "mailto:";
>:) I'm not.  Using a front-end script for your EXTERNAL would allow you to
>:) offer a choice of various ways to execute pine as well as offer you a
>:) choice as to what mailer you wanted to use.
>If you can configure External to open a script, you can also do it from
>this way. I do not see any difference. I have also had to eat my anger
>after not being able to save my letter, which finally did not get sent by
>the lynx mailer, just because I was not smart enough at the time to think
>of a way to keep my letter. If I had been using my mailer I could have
>saved it. I do not see anything wrong in just configuring a mail program.
>I think people in general would appreciate it. If anybody is against this
>please speak, I want to know why it is bad, when I only see something good
>out of it.
>     _________________________________________________________________
>     * References:
>          + [14]Re: lynx-dev External Mail programs
>               o From: Henry Nelson <address@hidden>
>     * Prev by Date: [15]Re: lynx-dev reading sjis docs [was Re: lynxcgi
>       problem]
>     * Next by Date: [16]lynx-dev can't interrupt "LIST" command
>     * Prev by thread: [17]Re: lynx-dev External Mail programs
>     * Next by thread: [18]lynx-dev listelves Lynx/w3m
>       cohabitation/licensing issues (fwd)
>     * Index(es):
>          + [19]Date
>          + [20]Thread
>     _________________________________________________________________
>   [21]Lynx mailing list archives
>   [22][FLORA HOME] [23][LYNX Home] 

reply via email to

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