> > > > elinks -eval 'set document.browse.margin_width = 0' -dump [...]
> >
> > That works too. And is probably a better solution, as it fixes *this*
> > issue without introducing a bunch of sed or awk that might paper over
> > an actual issue later down the road...
Less is more, I suppose.
>What I like about attach is that it just does the right thing and I don't
>have to know how it does it internally. It would be really nice if the
>same were true with other parts of the ui. The nmh MIME support comes
>across to me as a wart. No offense intended, it's a really useful wart and
>I
>To deal with the false directives when using attach:
>WhatNow could look for any lines that begin with # during
>the first call to "attach", and warn or refuse. Those who
>use # for replied-to text would have to find something else.
>Or we could get more sophisticated, back to the "challenging"
>
>Gave this a bit more thought. What *exactly* is the issue? Is it a lack of
>confidence that attach will do the *right thing* and the desire to check and
>change it if desired?
No, I read it as people are suggesting to solve the mime/attach conflict
to change attach to appending mhbuild directiv
Ken Hornstein writes:
> >Gave this a bit more thought. What *exactly* is the issue? Is it a lack of
> >confidence that attach will do the *right thing* and the desire to check and
> >change it if desired?
>
> No, I read it as people are suggesting to solve the mime/attach conflict
> to change at
Ken wrote:
> Can the people who want to have "attach" append mhbuild directives
> explain what their thinking is, specifically why they think their
> approach is preferrable? I went back and looked at the thread very
> carefully, and none of the proponents of this approach really covered
> why th
