Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

In fact, there is a different explanation for the mark as deleted approach. Depending on how it's handled, it can even make the undeletion explanation untenable. The point of "mark as deleted" was, at least originally, a matter of *SPEED*. MS-DOS would mark a file as deleted in the directory,

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Paul B. Gallagher wrote: Michael Lueck wrote: A Williams wrote: Michael Lueck wrote: One remaining question... is there some command line way to instruct SM to gracefully exit if possible (no unsaved emails open, etc...)? I would require that if I am to automate a daily local backup. That s

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Michael Lueck wrote: Greetings, Since no promising suggestions were made as to where ALL of the folders and emails disappeared to, I ended up rolling this one account's Inbox and folders under it back to the last available backup. One remaining question... is there some command line way to inst

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Chris Ilias wrote: On 2013-07-17 11:00 PM, Paul B. Gallagher wrote: Chris Ilias wrote: On 2013-07-17 12:14 PM, Paul B. Gallagher wrote: The point of doing it this way is to make undo possible. Are you assuming that is the reason, or do you have a source to cite? Sorry, didn't realize I ha

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

On 2013-07-17 11:00 PM, Paul B. Gallagher wrote: Chris Ilias wrote: On 2013-07-17 12:14 PM, Paul B. Gallagher wrote: The point of doing it this way is to make undo possible. Are you assuming that is the reason, or do you have a source to cite? Sorry, didn't realize I had strayed into acade

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Daniel wrote: Doesn't lend itself for automation, I suppose!! Exactly... now you are seeing my point... -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Michael Lueck wrote: Daniel wrote: but could you just copy your profile from its current location to some other location whilst SM is still operational?? SM might receive an email while the backup is running... Oh! picky-picky! ;-P How about switching SM off-line then, but I guess that's

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Daniel wrote: but could you just copy your profile from its current location to some other location whilst SM is still operational?? SM might receive an email while the backup is running... -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ __

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Michael Lueck wrote: Greetings, Since no promising suggestions were made as to where ALL of the folders and emails disappeared to, I ended up rolling this one account's Inbox and folders under it back to the last available backup. One remaining question... is there some command line way to inst

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Ed Mullen wrote: checks for an instance of SM in memory, kills the process (if it exists), and then the backup program executes the scheduled backup. I was hoping for a cross-platform way to script exit SM rather than a brutal kill. Looks like I will have to check for the run file, if there

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Michael Lueck wrote: A Williams wrote: Michael Lueck wrote: One remaining question... is there some command line way to instruct SM to gracefully exit if possible (no unsaved emails open, etc...)? I would require that if I am to automate a daily local backup. That sounds very risky. Why not

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

In , Michael Lueck wrote: > A Williams wrote: > > Michael Lueck wrote: > > > >> One remaining question... is there some command line way to > >> instruct SM to gracefully exit if possible (no unsaved emails > >> open, etc...)? I would require tha

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Michael Lueck wrote: A Williams wrote: Michael Lueck wrote: One remaining question... is there some command line way to instruct SM to gracefully exit if possible (no unsaved emails open, etc...)? I would require that if I am to automate a daily local backup. That sounds very risky. Why not

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

On 2013-07-18 15:14 (GMT+1000) Daniel composed: Felix Miata wrote: I compact more often than I empty trash. For each and every empty trash (normally 20-30 minutes after midnight) I immediately follow with compact. If I find some fool has emailed me binaries, after deleting attached binaries I

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

A Williams wrote: Michael Lueck wrote: One remaining question... is there some command line way to instruct SM to gracefully exit if possible (no unsaved emails open, etc...)? I would require that if I am to automate a daily local backup. That sounds very risky. Why not test for the existenc

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Michael Lueck wrote: Greetings, Since no promising suggestions were made as to where ALL of the folders and emails disappeared to, I ended up rolling this one account's Inbox and folders under it back to the last available backup. One remaining question... is there some command line way to inst

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Greetings, Since no promising suggestions were made as to where ALL of the folders and emails disappeared to, I ended up rolling this one account's Inbox and folders under it back to the last available backup. One remaining question... is there some command line way to instruct SM to graceful

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Felix Miata wrote: On 2013-07-17 20:02 (GMT+1000) Daniel composed: Felix Miata wrote: I compact more often than I empty trash. For each and every empty trash (normally 20-30 minutes after midnight) I immediately follow with compact. If I find some fool has emailed me binaries, after deleting

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Chris Ilias wrote: On 2013-07-17 12:14 PM, Paul B. Gallagher wrote: Felix Miata wrote: If it was up to me, delete would always mean delete rather than hide, regardless of context. Delete that increases disk consumption by even one bit is not deletion, it's a lie. Compaction would never be a s

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

On 2013-07-17 17:51 (GMT-0400) Paul B. Gallagher composed: Felix Miata wrote: Delete means cancel, expunge or eradicate. It's been around a very very long time. A hide operation that's reversible needs a different word that does not connote increase available free space. Current delete usage

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Paul B. Gallagher wrote: Felix Miata wrote: On 2013-07-17 12:14 (GMT-0400) Paul B. Gallagher composed: Felix Miata wrote: If it was up to me, delete would always mean delete rather than hide, regardless of context. Delete that increases disk consumption by even one bit is not deletion, it'

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

On 2013-07-17 12:14 PM, Paul B. Gallagher wrote: Felix Miata wrote: If it was up to me, delete would always mean delete rather than hide, regardless of context. Delete that increases disk consumption by even one bit is not deletion, it's a lie. Compaction would never be a separate menu item or

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Felix Miata wrote: On 2013-07-17 12:14 (GMT-0400) Paul B. Gallagher composed: Felix Miata wrote: If it was up to me, delete would always mean delete rather than hide, regardless of context. Delete that increases disk consumption by even one bit is not deletion, it's a lie. Compaction would

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

On 2013-07-17 12:14 (GMT-0400) Paul B. Gallagher composed: Felix Miata wrote: If it was up to me, delete would always mean delete rather than hide, regardless of context. Delete that increases disk consumption by even one bit is not deletion, it's a lie. Compaction would never be a separate m

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Felix Miata wrote: If it was up to me, delete would always mean delete rather than hide, regardless of context. Delete that increases disk consumption by even one bit is not deletion, it's a lie. Compaction would never be a separate menu item or process. The point of doing it this way is to ma

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

On 2013-07-17 20:02 (GMT+1000) Daniel composed: Felix Miata wrote: I compact more often than I empty trash. For each and every empty trash (normally 20-30 minutes after midnight) I immediately follow with compact. If I find some fool has emailed me binaries, after deleting attached binaries I

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Felix Miata wrote: On 2013-07-16 10:02 (GMT-0400) Michael Lueck composed: Felix Miata wrote: Not a fix, just a suggestion for the future: Back up daily. Well, I do weekly backups on Saturday... this was to be the last email sent prior to weekly mailbox compaction, then backup. Forgot an

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

On 2013-07-16 10:02 (GMT-0400) Michael Lueck composed: Felix Miata wrote: Not a fix, just a suggestion for the future: Back up daily. Well, I do weekly backups on Saturday... this was to be the last email sent prior to weekly mailbox compaction, then backup. Forgot another suggestion. I

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Felix Miata wrote: Not a fix, just a suggestion for the future: Back up daily. Well, I do weekly backups on Saturday... this was to be the last email sent prior to weekly mailbox compaction, then backup. I know of no way to gracefully exit Mozilla products via command line. I leave SM up "all

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

On 2013-07-13 18:26 (GMT-0400) Michael Lueck composed: Suggestions other than roll that account back to my most recent profile backup? Not a fix, just a suggestion for the future: Back up daily. I think that's the only way to prevent inexplicable failures. Using Linux, the only time I've nee

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

A Williams wrote: Have you found out what happened and how? There was no step I could suggest that you had not tried anyway. No I have not. Limping along with webmail access to the various accounts I use with SM. -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ ___

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Bill Davidsen wrote: Can you fall back to 2.17.1 and try the rebuild option again? What is the silver bullet about that particular build of SM? I suppose I could force the UbuntuZilla package for that version to get back to that version. Sincerely, -- Michael Lueck Lueck Data Systems http:/

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Michael Lueck wrote: Greetings, I had a most odd / scary thing happen this morning. I was sending an email via a SM POP account with a few MB of files attached to it. I remember accidentally clicking / doing something while it was sending via my SMTP (TLS) connection... and POOF that account's I

Re: SeaMonkey/2.19 on Linux nuked all messages in InBox and ALL folders underneath

Michael Lueck wrote: Greetings, I had a most odd / scary thing happen this morning. I was sending an email via a SM POP account with a few MB of files attached to it. I remember accidentally clicking / doing something while it was sending via my SMTP (TLS) connection... and POOF that account's I

Re: Seamonkey 2.19

Mark Berger wrote: chicagofan wrote: Mark Berger wrote: chicagofan wrote: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size problem you mentioned before? bj Font size problem is enou

Re: Seamonkey 2.19

Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size problem you mentioned before? bj ___ support-seamonkey mailing list support-seamonkey@lists.

Re: Seamonkey 2.19

Paul B. Gallagher wrote: Janine Starykowicz wrote: Ray_Net wrote: Paul B. Gallagher wrote, On 07/07/2013 00:04: Ray_Net wrote: Janine Starykowicz wrote, On 06/07/2013 18:13: When I open it in Notepad and try to save it, I get a popup saying "Access is denied." Change mms.cfg to mms.cfg-o

Re: Seamonkey 2.19

Janine Starykowicz wrote: Ray_Net wrote: Paul B. Gallagher wrote, On 07/07/2013 00:04: Ray_Net wrote: Janine Starykowicz wrote, On 06/07/2013 18:13: When I open it in Notepad and try to save it, I get a popup saying "Access is denied." Change mms.cfg to mms.cfg-original Copy mms.cfg-origi

Re: Seamonkey 2.19

Philip TAYLOR schreef: Robert Kaiser wrote: Philip TAYLOR schrieb: A new release of an application on which I rely is terminally broken when used with medium-sized fonts (125%) as opposed to the default of small (100%). No, from all I know, it's now actually respecting that 125% setting whil

Re: Seamonkey 2.19

Philip TAYLOR wrote: Robert Kaiser wrote: Philip TAYLOR schrieb: A new release of an application on which I rely is terminally broken when used with medium-sized fonts (125%) as opposed to the default of small (100%). No, from all I know, it's now actually respecting that 125% setting while

Re: Seamonkey 2.19

Philip TAYLOR wrote: Robert Kaiser wrote: Philip Taylor schrieb: Now reverted to 2.17.1. 2.19 cannot be used in its present state. OK, so when your OS is reporting things to your applications that you consider wrong, then your solution is to use old, insecure versions of the applications? M

Re: Seamonkey 2.19

Ray_Net wrote: Paul B. Gallagher wrote, On 07/07/2013 00:04: Ray_Net wrote: Janine Starykowicz wrote, On 06/07/2013 18:13: When I open it in Notepad and try to save it, I get a popup saying "Access is denied." Change mms.cfg to mms.cfg-original Copy mms.cfg-original to mms.txt Edit and sav

Re: Seamonkey 2.19

Ed Mullen wrote: Janine Starykowicz wrote: It won't let me save anything in the Flash folder, keeps sending mms.txt to Documents. Keeps telling me to talk to admin, but I am admin. ... Does your User Account have Administrative privleges? She said so -- see the excerpt above remaining afte

Re: Seamonkey 2.19

Unbelievable--right after sending of msg to you--it started downloading email again. Either you are just good luck, or the whole SM is weird. In any case--thanks for whatever. angels...@usa.net Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Tayl

Re: Seamonkey 2.19

Ray_Net wrote: Janine Starykowicz wrote, On 06/07/2013 18:13: When I open it in Notepad and try to save it, I get a popup saying "Access is denied." Change mms.cfg to mms.cfg-original Copy mms.cfg-original to mms.txt Edit and save mms.txt Change mms.txt to mms.cfg Works fine if the file is

Re: Seamonkey 2.19

Paul B. Gallagher wrote, On 07/07/2013 00:04: Ray_Net wrote: Janine Starykowicz wrote, On 06/07/2013 18:13: When I open it in Notepad and try to save it, I get a popup saying "Access is denied." Change mms.cfg to mms.cfg-original Copy mms.cfg-original to mms.txt Edit and save mms.txt Change

Re: Seamonkey 2.19

rob wrote: On Fri, 05 Jul 2013 01:14:54 -0500, Janine Starykowicz wrote: but the busy cursor is back everywhere, I'm getting frequent "not responding" messages, and there's a javascript hang that is happening on several websites. It's not quite as bad as in January, but almost. I'm on Win7 64

Re: Seamonkey 2.19

Andrea Govoni wrote: > IMHO, the advantages to go for the easy fix route is that you'll be able > to stay on the current stable version line, with all the security fixes > and function/code benefits that it means. > For example, if you encounter a bug or experience a SM crash you'll not > have to

Re: Seamonkey 2.19

Paul B. Gallagher wrote: Janine Starykowicz wrote: How can I revert? I'm not having any font problems, but the busy cursor is back everywhere, I'm getting frequent "not responding" messages, and there's a javascript hang that is happening on several websites. It's not quite as bad as in January

Re: Seamonkey 2.19

Philip TAYLOR schrieb: A new release of an application on which I rely is terminally broken when used with medium-sized fonts (125%) as opposed to the default of small (100%). No, from all I know, it's now actually respecting that 125% setting while before it wrongly ignored this setting compl

Re: Seamonkey 2.19

Cruz, Jaime wrote, On 05/07/2013 14:03: Ray_Net wrote: chicagofan wrote, On 04/07/2013 22:59: Mark Berger wrote: chicagofan wrote: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size pr

Re: Seamonkey 2.19

Philip Chee wrote: On 05/07/2013 03:53, Paul B. Gallagher wrote: I'm curious which (types of) users are having the problem. I myself didn't notice the slightest difference on either machine. Of course, my customizations or lack thereof might be different, I might use a different set of add-ins

Re: Seamonkey 2.19

Janine Starykowicz wrote: Paul B. Gallagher wrote: Janine Starykowicz wrote: How can I revert? I'm not having any font problems, but the busy cursor is back everywhere, I'm getting frequent "not responding" messages, and there's a javascript hang that is happening on several websites. It's not

Re: Seamonkey 2.19

Philip Taylor schrieb: Now reverted to 2.17.1. 2.19 cannot be used in its present state. OK, so when your OS is reporting things to your applications that you consider wrong, then your solution is to use old, insecure versions of the applications? Maybe you should either correct the OS setti

Re: Seamonkey 2.19

Ray Davison wrote: Paul B. Gallagher wrote: I'm curious which (types of) users are having the problem. I myself didn't notice the slightest difference on either machine. Of course, my customizations or lack thereof might be different, I might use a different set of add-ins, etc. User agent:

Re: Seamonkey 2.19

Janine Starykowicz wrote: Paul B. Gallagher wrote: Janine Starykowicz wrote: This is a newish Gateway laptop (December 2012). I had massive problems in January, only add-in at that point was FlashBlock because I thought Flash was causing the busy cursor. I've also tried disabling Flash protect

Re: Seamonkey 2.19

On 2013-07-06 12:34 PM, Noob42 wrote: Noob42, As per , I'm removing your post from the news server, because it contains a personal attack. -- Chris Ilias Newsgroup moderator __

Re: Seamonkey 2.19

On 7/6/2013 3:47 AM, Rob wrote: Andrea Govoni wrote: IMHO, the advantages to go for the easy fix route is that you'll be able to stay on the current stable version line, with all the security fixes and function/code benefits that it means. For example, if you encounter a bug or experience a SM

Re: Seamonkey 2.19

Geoff Welsh wrote: Paul B. Gallagher wrote: Mark Berger wrote: chicagofan wrote: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size problem you mentioned before? bj Font size problem

Re: Seamonkey 2.19

chicagofan wrote: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size problem you mentioned before? bj Font size problem is enough to stop using it. __

Re: Seamonkey 2.19

On 05/07/2013 03:53, Paul B. Gallagher wrote: > Mark Berger wrote: >> chicagofan wrote: >>> Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor >>> >>> What specifically is wrong with 2.19, besides the size problem you >>> mentioned before

Re: Seamonkey 2.19

Paul B. Gallagher wrote: I'm curious which (types of) users are having the problem. I myself didn't notice the slightest difference on either machine. Of course, my customizations or lack thereof might be different, I might use a different set of add-ins, etc. User agent: Mozilla/5.0 (Windows N

Re: Seamonkey 2.19

Noob42 wrote: > Rob wrote: > >> Migration to IE+Outlook is around the corner. It is a pity, but there >> seems to be no hope for Seamonkey (or other Mozilla products) in a >> production environment. > > Now I know you're just trolling. No, I'm not. The decision was really made to migrate from a

Re: Seamonkey 2.19

Paul B. Gallagher wrote: Janine Starykowicz wrote: Paul B. Gallagher wrote: Janine Starykowicz wrote: How can I revert? I'm not having any font problems, but the busy cursor is back everywhere, I'm getting frequent "not responding" messages, and there's a javascript hang that is happening on

Re: Seamonkey 2.19

Janine Starykowicz wrote, On 06/07/2013 18:13: Paul B. Gallagher wrote: Janine Starykowicz wrote: Paul B. Gallagher wrote: Janine Starykowicz wrote: How can I revert? I'm not having any font problems, but the busy cursor is back everywhere, I'm getting frequent "not responding" messages, and

Re: Seamonkey 2.19

Janine Starykowicz wrote: How can I revert? I'm not having any font problems, but the busy cursor is back everywhere, I'm getting frequent "not responding" messages, and there's a javascript hang that is happening on several websites. It's not quite as bad as in January, but almost. I'm on Win7

Re: Seamonkey 2.19

chicagofan wrote, On 04/07/2013 22:59: Mark Berger wrote: chicagofan wrote: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size problem you mentioned before? bj Font size problem is eno

Re: Seamonkey 2.19

Philip Taylor wrote: > Now reverted to 2.17.1. 2.19 cannot be used in its present state. Out of curiosity, before reverting to 2.17.1 did you try to "change the default value [of layout.css.devPixelsPerPx] -1 to 1 to make it work like in previous Firefox [and SeaMonkey] versions (100%)"? -- An

Re: Seamonkey 2.19

Ray_Net wrote: > Andrea Govoni wrote, On 04/07/2013 14:52: >> Philip Taylor wrote: >>> Now reverted to 2.17.1. 2.19 cannot be used in its present state. >> >> Out of curiosity, before reverting to 2.17.1 did you try to "change the >> default value [of layout.css.devPixelsPerPx] -1 to 1 to make it

Re: Seamonkey 2.19

Ray_Net wrote: chicagofan wrote, On 04/07/2013 22:59: Mark Berger wrote: chicagofan wrote: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size problem you mentioned before? bj Font siz

Re: Seamonkey 2.19

Paul B. Gallagher wrote: Mark Berger wrote: chicagofan wrote: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size problem you mentioned before? bj Font size problem is enough to stop us

Re: Seamonkey 2.19

Rob wrote, On 06/07/2013 09:47: Andrea Govoni wrote: IMHO, the advantages to go for the easy fix route is that you'll be able to stay on the current stable version line, with all the security fixes and function/code benefits that it means. For example, if you encounter a bug or experience a SM

Re: Seamonkey 2.19

Mark Berger wrote: chicagofan wrote: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size problem you mentioned before? bj Font size problem is enough to stop using it. I'm curious whic

Re: Seamonkey 2.19

chicagofan wrote: Mark Berger wrote: chicagofan wrote: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size problem you mentioned before? bj Font size problem is enough to stop using it.

Re: Seamonkey 2.19

Mark Berger wrote: chicagofan wrote: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size problem you mentioned before? bj Font size problem is enough to stop using it. Are you saying you

Re: Seamonkey 2.19

Andrea Govoni wrote, On 04/07/2013 16:51: Ray_Net wrote: Andrea Govoni wrote, On 04/07/2013 14:52: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Out of curiosity, before reverting to 2.17.1 did you try to "change the default value [of layout.css.devPi

Re: Seamonkey 2.19

Paul B. Gallagher wrote: Mark Berger wrote: chicagofan wrote: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor What specifically is wrong with 2.19, besides the size problem you mentioned before? bj Font size problem is enough to stop us

Re: Seamonkey 2.19

On Wed, 03 Jul 2013 23:06:31 +0100, in , Philip Taylor wrote: > Just been updated : web sites and e-mail now > appear two zoom steps larger. What has happened ? See

Re: Seamonkey 2.19

Andrea Govoni wrote, On 04/07/2013 14:52: Philip Taylor wrote: Now reverted to 2.17.1. 2.19 cannot be used in its present state. Out of curiosity, before reverting to 2.17.1 did you try to "change the default value [of layout.css.devPixelsPerPx] -1 to 1 to make it work like in previous Firefox

Re: Seamonkey 2.19

Robert Kaiser wrote: > Philip TAYLOR schrieb: >> A new release of an application on >> which I rely is terminally broken when used with medium-sized >> fonts (125%) as opposed to the default of small (100%). > > No, from all I know, it's now actually respecting that 125% setting > while before it

Re: Seamonkey 2.19

Robert Kaiser wrote: > Philip Taylor schrieb: >> Now reverted to 2.17.1. 2.19 cannot be used in its present state. > > OK, so when your OS is reporting things to your applications that you > consider wrong, then your solution is to use old, insecure versions of > the applications? Maybe you shou

Re: Seamonkey 2.19

Now reverted to 2.17.1. 2.19 cannot be used in its present state. Philip Taylor Philip Taylor wrote: > Just been updated : web sites and e-mail now > appear two zoom steps larger. What has happened ? > > Philip Taylor > ___ > support-seamonkey