On Wed, Aug 08, 2001 at 03:45:12PM -0400, Thomas Dickey wrote:
> > > still won't work (xterm won't retain it as a single line if it wasn't
> > > written as a single line, and you can't count on any screen optimization
> > > library to do this).
> >
> > I thought that if mutt had written it as a s
On Wed, Aug 08, 2001 at 04:15:54PM -0400, Andrew Pimlott wrote:
> On Wed, Aug 08, 2001 at 03:45:12PM -0400, Thomas Dickey wrote:
> > > > still won't work (xterm won't retain it as a single line if it wasn't
> > > > written as a single line, and you can't count on any screen optimization
> > > > li
> > still won't work (xterm won't retain it as a single line if it wasn't
> > written as a single line, and you can't count on any screen optimization
> > library to do this).
>
> I thought that if mutt had written it as a single line to the screen
> library, the screen library would leave it alo
On Wed, Aug 08, 2001 at 02:25:01PM -0400, Thomas E. Dickey wrote:
> On Wed, 8 Aug 2001, Andrew Pimlott wrote:
>
> > When the "markers" and "smart_wrap" options are both off, it would
> > be nice if mutt would print long lines to the screen without a
> > newline. This way, if I copy the line in a
On Wed, 8 Aug 2001, Andrew Pimlott wrote:
> When the "markers" and "smart_wrap" options are both off, it would
> be nice if mutt would print long lines to the screen without a
> newline. This way, if I copy the line in an xterm, the whole line
> goes into the cut buffer unbroken. As it is, I ge
