Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Setting Thunderbird defaut format as Body text (definitively

  • 2 përgjigje
  • 2 e kanë hasur këtë problem
  • 3 parje
  • Përgjigjja më e re nga decebal1

more options

Hello, Since a few years, Thunderbird sets "Paragraph" as the default format for any new message or reply to an existing message. Although setting "Not use paragraph as default format", its reverts to the initial status (Paragraph = default) after re-opening Thunderbird. This is painful. I never use this mode and I have to change the setting in "parameters" each time I open Thunderbird. My version : 108.0.1 (64 bits) (French) OS/ Linux Ubuntu Can this bug be fixed ? Regards,

Hello, Since a few years, Thunderbird sets "Paragraph" as the default format for any new message or reply to an existing message. Although setting "Not use paragraph as default format", its reverts to the initial status (Paragraph = default) after re-opening Thunderbird. This is painful. I never use this mode and I have to change the setting in "parameters" each time I open Thunderbird. My version : 108.0.1 (64 bits) (French) OS/ Linux Ubuntu Can this bug be fixed ? Regards,

Krejt Përgjigjet (2)

more options

First, if you have any addons, turn them all off and retry. If that doesn't work, this next approach may be worth a try... go to settings>general and click on the config editor and look for mail.compose.default_to_paragraph and change the value there.

more options

Thank you david. The very first thing I did is to de-activate or uninstall add-on. No effect at all. The boolean parameter that allows to switch from true to false mail.compose.default_to_paragraph can be changed but automatically reverts to its original and apparently default value ("True") after you quit Thunderbird. And this behavior is not the one expected I suppose. So it looks that old bug (I have been facing this issue for years) persists, for unknown reason. Regards,