lynx-dev
[Top][All Lists]
Advanced

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

Re: lynx-dev [PATCH] remove extension to EXTERNAL command, extend CERN r


From: Klaus Weide
Subject: Re: lynx-dev [PATCH] remove extension to EXTERNAL command, extend CERN rules support for mailto: URLs
Date: Wed, 12 Jul 2000 16:27:17 -0500 (CDT)

On Mon, 10 Jul 2000, Vlad Harchev wrote:
> On Sun, 9 Jul 2000, Klaus Weide wrote:
> > Another problem is that we haven't even defined what we are talking about.
> > There are many ways in which lynx can be made to send mail (already, with
> > its built-in code).  Try to come up with a list as an exercise, it should
> > have at least 5 or 6 entries... only one of which is "following a link to
> > a mailto: URL".
> 
>   Does it really matter? I think we don't have a lot to borrow from them,
> execpt some mailto: URL parsing code and code that generates subject line.

To quote yourself from other recent messages:
|   Let's think about entire spectrum of problems with respect to timeout on
| reading, not just described in original post.
and
|   We should thinkin more generic ways.

On the one hand, you think now your first patch isn't good because it
isn't general enough, it handles only a special case: ACTIVATE on a
mailto link.  On the other hand, it's perfectly fine with you to handle
some kinds of mail sending with an external program, but not all of
them?

Realize that any of the recently discussed "solutions" don't apply
to comments sent with the COMMENT ('c') key.
Realize that any of the recently discussed "solutions" don't apply
to mail that is sent when a FORM with ACTION="mailto:..."; is submitted.
Realize that any of the recently discussed "solutions" don't apply
to mail that is sent because of MAIL_SYSTEM_ERROR_LOGGING.
Realize that any of the recently discussed "solutions" don't apply
to "Mail the file" from the "Printing Options" screen.

Does this make sense?  Wouldn't a user expect that an "external
mail handler" (or however it is going to be described) applies to
all of those cases, too?  Or at least some?  Forgetting about those
seems just as incomplete to me as limiting a mechanism to ACTIVATE only.

What is the problem you are trying to solve?  The answers depends on
that.

  Klaus


; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

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