On 06/13/1999 (11:29:29), [EMAIL PROTECTED] wrote:
> The problem has been around for so long because it's an
> s-lang problem, not a mutt problem, so discussing it on the mutt mailing
> lists isn't going to do diddly-squat, since for the most part, the
> s-lang developers are not on the mutt mailing lists.  The solution is to
> compile with ncurses instead of s-lang -- though it was also announced
> that a new version of s-lang has recently been released, and people who
> are concerned with this problem should try the new s-lang and see if
> it's fixed.

        Again, you obviously did not read the thread.

        It is *NOT* a slang problem. One cannot blame slang entirely
        for this madness -- ncurses does _THE EXACT SAME THING_. I
        have tested this thoroughly with ncurses 1.8.6 and 4.2.

        Do not blow this problem off entirely on slang.

        The new version of slang (1.3.7) does not "fix this problem."

> If it's not fixed, complaining about it on mutt mailiing lists is not
> useful; nothing in mutt can fix this except compiling with ncurses
> instead of s-lang, which is already a supported option.  If you want
> this problem fixed, complain to (or better, volunteer to help) the
> s-lang developers, who can actually do something about it.

        You keep thinking it's a slang problem -- it is not. The
        problem is not entirely slang, nor is it entirely ncurses.

        This is a very common thing in the "free software world."
        Blaming someone else for one's own problems. This is why I
        said I have yet to receive an answer (and still waiting).

> The stripping-trailing-spaces-with-vi answer is very useful for the
> specific problem of people who cannot compile with ncurses and are only
> concerned with the difficulty s-lang causes for cut-and-paste.  It's a
> band-aid for one part of the problem, since people continually ask about
> it & then reject "compile with ncurses" as the answer.

        Since when did mutt pipe all of it's text output through vi?
        I don't see the builtin pager for Email viewing running through
        vi, do you? vi is not the solution, nor related to the problem.
        Using vi (somehow; it's beyond my comprehension how it could
        even be used for this) to rectify the problem is nothing more
        than a way to *AVOID* the problem (e.g. getting me to shut up),
        rather than fixing it.

        I think you are confused regarding what my complaint is about.
        I made it very clear what I was complaining about, yet everyone
        blames slang when it is not entirely slang which is the problem.

        Possibly GIF-based screenshots of the problem (under slang and
        ncurses) made available via a URL would be appropriate? Possibly
        then you and others would then understand the severity of this
        problem.

-- 
| Jeremy Chadwick                                   [EMAIL PROTECTED] |
| Parodius Networking                             [EMAIL PROTECTED] |
| UNIX System Administrator                   http://www.parodius.com/ |

Reply via email to