Re: Changing signatures in TB

[David E. Ross]

On 3/21/12 3:16 PM, Larry in AZ wrote:
> What's the best/easiest add-on for changing signatures in TB 11..?
>

I like Signature Switch at <http://mozext.achimonline.de/>.

--

David E. Ross
<http://www.rossde.com/>.

Anyone who thinks government owns a monopoly on inefficient, obstructive
bureaucracy has obviously never worked for a large corporation.
© 1997 by David E. Ross

[Cy Burnot]

David E. Ross has written on 3/21/2012 6:19 PM:

> On 3/21/12 3:16 PM, Larry in AZ wrote:
>> What's the best/easiest add-on for changing signatures in TB 11..?
>>
>
> I like Signature Switch at <http://mozext.achimonline.de/>.
>

+1

[Keith Nuttle]

I use Clipping since what ever signatures I put in Thunderbird are
available in Firefox for filling out forms and posting to web forums.

Clippings will take any string you need from parts of addresses for
completing web forms, to full address. You can also add strings for
other repetitive entries that you make, such as email addresses.

The are available from any active window in either TB or FF, with a
right click in the active window.

[Peter]

Now on the latest version, and it seems to me to be pretty good.
Congratulations to the team.
One question though: how do I control the line length? There used to be
an option in Tools\Options but I can't locate it. Help, please

[Mike Easter]

Peter wrote:

> how do I control the line length? There used to be
> an option in Tools\Options but I can't locate it.

about:config

mailnews.wraplength default integer 72


--
Mike Easter

[Bill B]

This has always puzzled me. For me, it never does what it purports to
do. It does not limit the line to the declared length when composing a
message, and neither does it limit the line when published.

Mine is set at Mike described - 72 characters. When composing this
message, it wrapped at the edge of the physical window. Unless I am
proven wrong, when this message shows up in the newsgroup, the first
line will be 140 characters (the 72nd character is the end of the first
sentence).

What is the behavior I ought to see?

Bill Braun

[Bill B]

Follow-on...

I was proven wrong but for the reason noted. The message pane in TB is
wider than the compose window, and the message wrapped to that width,
longer than the 140 characters I noted.

Bill.

[Ron Hunter]

Your message fills my window width, which is as it should be. If you
wish it to wrap at 72, then you will need to insert a carriage return,
but the receiver can still let it flow. When I hit reply, the message
was copied as it was written, and the wrap happened at the end of the
last full word that would have put it over 72 characters.

[Bill B]

Thanks, Ron. Then I misunderstood what wrap really means. I took it too
literally.

What would be the display difference between wrap (at 72, for example)
and no wrap (or wrap set to 10000, for example)?

[Greywolf]

Oddly, your first post does not wrap, your follow-on post (above) does
wrap.

Weird. TB 7.0.1

Wolf K.

[Peter]

Thanks for all the replies. I have now realised that the
mailnews.wraplength is set at 72 but when receiving and
replying/forwarding mail messages the lines fly off to the right. How do
I change this

[Bill B]

On 3/22/2012 11:18 AM, Ron Hunter wrote:

On rereading your response, I think I assumed that setting line wrap to
a number (e.g., 72) had the effect of inserting a carriage return and a
line feed at that character count (or after the end of the word if 72
fell in the middle) either a) during compose or b) as the message was
being sent to the newsgroup. That is where I went wrong.

[Mike Easter]

Bill B wrote:
> Mike Easter wrote:
>> Peter wrote:
>>
>>> how do I control the line length? There used to be
>>> an option in Tools\Options but I can't locate it.
>>
>> about:config
>>
>> mailnews.wraplength default integer 72
>
> This has always puzzled me. For me, it never does what it purports to
> do. It does not limit the line to the declared length when composing a
> message, and neither does it limit the line when published.
>
> Mine is set at Mike described - 72 characters. When composing this
> message, it wrapped at the edge of the physical window.

There is a setting for that. My Tb 12 default is

mail.compose.wrap_to_window_width default boolean false

so my compose doesn't wrap to the window, but wraps at 72.

Also, my default for the source wrap is false

view_source.wrap_long_lines default boolean false

> Unless I am proven wrong, when this message shows up in the
> newsgroup, the first line will be 140 characters (the 72nd character
> is the end of the first sentence).

When you are viewing your message in the newsgroup, the format=flowed
function 'takes over' so that your 72 char wraps (seen in the source)
appear to be wrapped to the window.

You can also configure the f=f display from the default which is:

mailnews.display.disable_format_flowed_support default boolean false

> What is the behavior I ought to see?

? ought ? Personally I like the defaults. If your compose is going to
the window that is different from mine.


--
Mike Easter

[Mike Easter]

If the meaning of your question is correctly understood by me to mean:

I am configured for format=flowed (you are), but when I am reading such
flowed messages, I want to disable f=f display, and instead have the
soft wraps wrap the display.

Then you would change:

mailnews.display.disable_format_flowed_support default boolean false

to true instead of false.


--
Mike Easter

[Mike Easter]

Bill B wrote:

> On rereading your response, I think I assumed that setting line wrap to
> a number (e.g., 72) had the effect of inserting a carriage return and a
> line feed at that character count (or after the end of the word if 72
> fell in the middle) either a) during compose or b) as the message was
> being sent to the newsgroup. That is where I went wrong.

If you configure to wrap at 72, but use format=flowed, then the readers
who do not display f=f will display your lines wrapped at 72, but if you
are configured to display as f=f, then such f=f wrapped lines will
display to you to wrap to the window, not 72.

However, even in f=f mode, if you are configured to display /compose/
wrap at 72, then you will see that 72 wrap.

Also, the default is to wrap the source view, so if you want to see your
message as the 'wrapped viewers' will see it, you can look at the source
with ctrl-U.


--
Mike Easter

[Bill B]

Well, knock me upside the head with the closest thing at hand. The two
configurations were competing with each other, with mail.compose.wrap
winning out over mailnews. wraplength.

Mike, you get the prize. Thank you.

Bill

[Bill B]

Except...when I read my own response in the newsgroup it was wrapped to
the window.

Oh, well, in the end, it doesn't really matter, does it? Too much time
on my hands?

[Mike Easter]

Bill B wrote:
> Bill B wrote:
>> Mike Easter wrote:

>>> You can also configure the f=f display from the default which is:
>>>
>>> mailnews.display.disable_format_flowed_support default boolean false

> Except...when I read my own response in the newsgroup it was wrapped to
> the window.

Your posts here are f=f.

If you change the above about:config line I posted to true instead of
false then your view will be wrapped to 72 instead of the window.



--
Mike Easter

[Herb]

On 21.03.2012 22:16 UK Time, Larry in AZ wrote:
> What's the best/easiest add-on for changing signatures in TB 11..?
>

See
<http://groups.google.com/group/mozilla.support.thunderbird/browse_thread/thread/e9ba9d1cfa05f216/>

FWIW, I use QuickText and can highly recommend it.

--
Herbert Eppel
www.HETranslation.co.uk