Re: [Evolution] Composer Word Wrap, Revisited
- From: "E. Joshua Rigler" <jrigler colorado edu>
- To: "Dustin D. Trammell" <dtrammell sipera com>
- Cc: evolution-list gnome org
- Subject: Re: [Evolution] Composer Word Wrap, Revisited
- Date: Tue, 06 Sep 2005 11:24:44 -0600
Well, as one might notice in the quoted text below, the message *I*
received from Dustin wrapped at column 72. Something I've noticed in my
version 1.4.5 (I know that's old, but I use RH-EL v3 at work) is that
the compose window simply starts out too narrow and forces words to wrap
early in order to stay visible. Once I send the message, however, the
lines are re-formatted to wrap at column 72. I can also drag the
compose window wider, and the lines are continually reformatted to fit
within the window until a maximum column width of 72 is reached, at
which point lines wrap as expected. All of my email is written in
plain-text, so I can't say anything about HTML email composition.
That said, it would be nice if the compose window width could be set or
remembered from session to session so I don't have to drag my window
wider for true WYSIWYG email composition.
-EJR
On Tue, 2005-09-06 at 09:20, Dustin D. Trammell wrote:
Now, before you all groan "oh no, not this topic again", let me explain
that yes, I know that you cannot change the upper column bound value at
which the Evolution composer wraps lines. I've also gathered from the
list archives that it should be wrapping at column 72, and that value is
hard-coded.
My problem however, is that lines are wrapping at column 55, as I'm sure
you can see is demonstrated by this message. All previous installations
of Evolution I've used in the past (packaged bins as well as built from
source) have wrapped at column 72, which is perfectly reasonable. 55 is
way too soon. I'm currently using Evolution 2.2.3, as is packaged by
Dropline Gnome 2.10.2. Is this likely an issue with Evolution itself
(or a recent change that I can't find reference for), or with some other
component in Gnome that may be causing Evolution to behave this way?
Thanks for any assistance you may be able to provide,
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]