Re: Is there a way to know which extensions may break when upgrading?

2020-03-08 Thread Daniel
Steve Dunn wrote on 9/03/2020 1:39 AM: On 2020-03-08 04:43, Daniel wrote: If "I mostly use SeaMonkey for email and newsgroups" why not use Thunderbird in place of SeaMonkey?? That would save using resources on the unused Browser portion of SM! Eventually that will probably be necessary,

Re: SM already has a clone tab -- Re: For those who use PrefBar v7.1.1, does its clone button not work anymore for you too?

2020-03-08 Thread alexyu
Ant wrote, on 08 Mar 20 01:03: On 3/7/2020 6:43 PM, alexyu wrote: Frank-Rainer Grahl wrote, on 07 Mar 20 20:16: alexyu wrote: I commented on using "Duplicate Tab", which I have been using since before FF (and, I think, SM too) introduced the "middle-click on 'reload' button" for this. 

Re: Preference Expired

2020-03-08 Thread Paul in Houston, TX
Larry S. wrote: Paul in Houston, TX wrote: Larry S. wrote: Paul in Houston, TX wrote: Larry S. wrote: David E. Ross wrote: On 3/2/2020 1:11 PM, Larry S. wrote: I was suddenly denied access to Fox News. Checked my settings, and discovered that one preference expired today, and another one

Re: Preference Expired

2020-03-08 Thread Hartmut Figge
Hartmut Figge: >Curious as I sometimes be I have tried to get that message. First asking >ixquick about Fox News and then visiting https://www.foxnews.com/politics > >No problem with Mozilla/5.0 (X11; Linux x86_64; rv:60.0) >Gecko/2020030200 SeaMonkey/2.53.2-h For testing I have changed my UA to

Re: Preference Expired

2020-03-08 Thread Hartmut Figge
Larry S.: >O.K., it didn't work. Still get the message "You don't have permission >to access Fox News on this server". >Any other thoughts? Curious as I sometimes be I have tried to get that message. First asking ixquick about Fox News and then visiting https://www.foxnews.com/politics No

Re: Preference Expired

2020-03-08 Thread Larry S.
Paul in Houston, TX wrote: Larry S. wrote: Paul in Houston, TX wrote: Larry S. wrote: David E. Ross wrote: On 3/2/2020 1:11 PM, Larry S. wrote: I was suddenly denied access to Fox News. Checked my settings, and discovered that one preference expired today, and another one tomorrow.

Re: Building Seamonkey 2.53.1 error on nsstring v0.1.0, both on Devuan and on Arch Linux

2020-03-08 Thread Hartmut Figge
Frank-Rainer Grahl: >We are trying to get latest rust support into 2.53.2 at least for Linux. >Unfortunately rust is more or less alpha/early beta quality wrt features and >deprecation and a constantly moving target. FWIW, TB-Trunk now requires at least rust-1.41.0. Hartmut

Re: Seamonkey-2.53.1 build segmentation fault on Debian, AMD Ryzen

2020-03-08 Thread Hartmut Figge
Frank-Rainer Grahl: >Bill had at least one problem with 9 I think. Unless you use the unofficial >patches on top of the old comm-release and mozilla-release 2.53.1 might not >compile with clang 9. I am only using the official patches from Bill. clang-9.0.1 is installed here since 23. Dec. My

Re: Seamonkey-2.53.1 build segmentation fault on Debian, AMD Ryzen

2020-03-08 Thread Frank-Rainer Grahl
Hartmut Figge wrote: Frank-Rainer Grahl: The official release was done with gcc 6 but I regularly build with gcc 8 in a Cent OS 7 vm. Sorry no idea. gcc 6 to 8 should work. Maybe try clang 6 to 8. 9 might work too. I am using Gentoo and have abandoned gcc for building SM for some time now.

Re: Seamonkey-2.53.1 build segmentation fault on Debian, AMD Ryzen

2020-03-08 Thread Hartmut Figge
Frank-Rainer Grahl: >The official release was done with gcc 6 but I regularly build with gcc 8 in >a Cent OS 7 vm. Sorry no idea. gcc 6 to 8 should work. Maybe try clang 6 to 8. >9 might work too. I am using Gentoo and have abandoned gcc for building SM for some time now. At the moment I am

Re: Seamonkey-2.53.1 build segmentation fault on Debian, AMD Ryzen

2020-03-08 Thread Frank-Rainer Grahl
Hendrik-Jan Heins wrote: Hi again, With the rust issue solved, I now get a next error on Debian. For the build I am using gcc 8.3.0 The error is as below. Is there any way to recover from this? thanks, Hendrik-Jan In file included from

Re: Building Seamonkey 2.53.1 error on nsstring v0.1.0, both on Devuan and on Arch Linux

2020-03-08 Thread Hendrik-Jan Heins
On Sunday, 8 March 2020 16:47:30 UTC+1, Frank-Rainer Grahl wrote: > Hendrik-Jan Heins wrote: > > On Sunday, 8 March 2020 16:20:46 UTC+1, Frank-Rainer Grahl wrote: > >> Hendrik-Jan Heins wrote: > >>> On Sunday, 8 March 2020 00:13:51 UTC+1, Frank-Rainer Grahl wrote: > hjhe...@gmail.com

Seamonkey-2.53.1 build segmentation fault on Debian, AMD Ryzen

2020-03-08 Thread Hendrik-Jan Heins
Hi again, With the rust issue solved, I now get a next error on Debian. For the build I am using gcc 8.3.0 The error is as below. Is there any way to recover from this? thanks, Hendrik-Jan In file included from

Re: Building Seamonkey 2.53.1 error on nsstring v0.1.0, both on Devuan and on Arch Linux

2020-03-08 Thread Frank-Rainer Grahl
Hendrik-Jan Heins wrote: On Sunday, 8 March 2020 16:20:46 UTC+1, Frank-Rainer Grahl wrote: Hendrik-Jan Heins wrote: On Sunday, 8 March 2020 00:13:51 UTC+1, Frank-Rainer Grahl wrote: hjhe...@gmail.com wrote: Use rust 1.36. rust 1.37 might also work. FRG Thank you FRG! For anyone with

Re: Building Seamonkey 2.53.1 error on nsstring v0.1.0, both on Devuan and on Arch Linux

2020-03-08 Thread Hendrik-Jan Heins
On Sunday, 8 March 2020 16:20:46 UTC+1, Frank-Rainer Grahl wrote: > Hendrik-Jan Heins wrote: > > On Sunday, 8 March 2020 00:13:51 UTC+1, Frank-Rainer Grahl wrote: > >> hjhe...@gmail.com wrote: > >>> On Saturday, 7 March 2020 23:27:45 UTC+1, hjh...@gmail.com wrote: > Hi All, > > I

Re: Building Seamonkey 2.53.1 error on nsstring v0.1.0, both on Devuan and on Arch Linux

2020-03-08 Thread Frank-Rainer Grahl
Hendrik-Jan Heins wrote: On Sunday, 8 March 2020 00:13:51 UTC+1, Frank-Rainer Grahl wrote: hjhe...@gmail.com wrote: On Saturday, 7 March 2020 23:27:45 UTC+1, hjh...@gmail.com wrote: Hi All, I hope someone here is familiar with this issue and can point me in the right direction. I have

Re: Building Seamonkey 2.53.1 error on nsstring v0.1.0, both on Devuan and on Arch Linux

2020-03-08 Thread Hendrik-Jan Heins
On Sunday, 8 March 2020 00:13:51 UTC+1, Frank-Rainer Grahl wrote: > hjhe...@gmail.com wrote: > > On Saturday, 7 March 2020 23:27:45 UTC+1, hjh...@gmail.com wrote: > >> Hi All, > >> > >> I hope someone here is familiar with this issue and can point me in the > >> right direction. I have been

Re: Is there a way to know which extensions may break when upgrading?

2020-03-08 Thread Steve Dunn
On 2020-03-08 04:43, Daniel wrote: If "I mostly use SeaMonkey for email and newsgroups" why not use Thunderbird in place of SeaMonkey?? That would save using resources on the unused Browser portion of SM! Eventually that will probably be necessary, but as long as SeaMonkey works, there's

Re: Lightning extension and cookies

2020-03-08 Thread user
Frank-Rainer Grahl a écrit : user wrote: Hello It seems to exist a relation between the Ligntning extension and cookies in Seamonkey. On most websites, there is no problem. But with some, there is a cookies problem when Lightning extension is enabled. In such a case, it is not possible to

Re: Mail date format changed in 2.53.1

2020-03-08 Thread Manuel Casal Lodeiro
In 08/03/20 10:55, Manuel Casal Lodeiro dixit: In 3/8/20 9:35 AM, mike dixit: On 08.03.2020 08:58, Manuel Casal Lodeiro wrote: The locale format in message headers (in Thread pane in Mail window) has changed from previous versions after updating to 2.53.1. In Edit/Preferences/Appearance/Date

Re: Mail date format changed in 2.53.1

2020-03-08 Thread Manuel Casal Lodeiro
In 3/8/20 9:35 AM, mike dixit: On 08.03.2020 08:58, Manuel Casal Lodeiro wrote: The locale format in message headers (in Thread pane in Mail window) has changed from previous versions after updating to 2.53.1. In Edit/Preferences/Appearance/Date and Time Formatting you can switch between

Re: Is there a way to know which extensions may break when upgrading?

2020-03-08 Thread Daniel
Steve Dunn wrote on 8/03/2020 2:49 AM: On 2020-03-06 18:09, Ant wrote: You could share what extensions you have and we can tell you. Here's mine: The most important ones for me are: * JunQuilla 1.0.4 * Adblock Plus 2.9.1 (which the 2.53.1 release notes say is problematic, but someone

Re: Mail date format changed in 2.53.1

2020-03-08 Thread mike
On 08.03.2020 08:58, Manuel Casal Lodeiro wrote: > The locale format in message headers (in Thread pane in Mail window) has > changed from previous versions after updating to 2.53.1. In Edit/Preferences/Appearance/Date and Time Formatting you can switch between Application locale an Regional