Re: SeaMonkey 2.35..
On 6/08/2015 6:18 AM, Rob Steinmetz wrote: Edmund Wong wrote: Hi, I regret to be the bearer of bad news; but as it stands, the worst case scenario (and likely the actual case) is that 2.35 is not going to be released in July. The new goal is to release it in early August. The past month has been mired in fire-fighting bustages, getting repacks and builds working (as of this writing, trunk is busted) as well as the need to get the backend buildbot code updated to reflect that we no longer depend on CVS. I apologize for the delay and thank everyone for your patience. Edmund Thanks for the update. At this point I'd rather wait until things get sorted out than rush into an unstable situation. FWIW I've been running Callek's contributed win32 2.35 build for a couple of weeks with no issues. But then, I have a pretty simple setup with few addons but do mix POP and Imap mail servers. -- Cheers, djc ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.35..
Thee Chicago Wolf [MVP] wrote: On Thu, 6 Aug 2015 20:52:47 +1000, David Cox wrote: On 6/08/2015 6:18 AM, Rob Steinmetz wrote: Edmund Wong wrote: Hi, I regret to be the bearer of bad news; but as it stands, the worst case scenario (and likely the actual case) is that 2.35 is not going to be released in July. The new goal is to release it in early August. The past month has been mired in fire-fighting bustages, getting repacks and builds working (as of this writing, trunk is busted) as well as the need to get the backend buildbot code updated to reflect that we no longer depend on CVS. I apologize for the delay and thank everyone for your patience. Edmund Thanks for the update. At this point I'd rather wait until things get sorted out than rush into an unstable situation. FWIW I've been running Callek's contributed win32 2.35 build for a couple of weeks with no issues. But then, I have a pretty simple setup with few addons but do mix POP and Imap mail servers. I was running that for a while with good luck as well. I've had good luck with a 2.36 contrib build from here: https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/ I won't be sad if 2.34 > 2.36 is skipped in favor of a 2.37 build to be in parity with FF40. - Thee Chicago Wolf [MVP] +1 -- Gertjan User agent: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 SeaMonkey/2.37a1 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Speaking of brain-dead browser sniffing...
On 06/08/2015 03:51, NFN Smith wrote: > An unexpected source: addons.mozilla.org > > I keep a fairly substantial collection of downloaded software that I use > for troubleshooting purposes, which allows me to work on a computer > almost entirely off-line, when necessary. > > I have quite a bit of Mozilla stuff in my collection, including > extensions for Firefox, Thunderbird and Seamonkey. My habit is that > periodically, I go to addons.mozilla.org, and download copies of > extensions for all three. I normally right-click on the offered > download, and select "save link target as", as I want XPI files with the > full name of the extension and the version. For this, what I'm doing is > longer term storage, that I expect to use more than once, rather than > just grab something, install it, and discard the download, when the > installation is complete. > > I use Seamonkey as my normal browser, and I notice that in the Firefox > sections of AMO, that the the download button is now being overlaid with > a button titled "Only with Firefox! Get Firefox Now!", which resolves to > a link to the Firefox downloads page. And this is happening even for > extensions that explicitly support Seamonkey. > > I can get around the problem easily enough by spoofing Firefox (and I > already spoof the platform for downloading extensions that have > Mac-specific versions), or going to the equivalent Seamonkey page, for > extensions that have Seamonkey support. > > But I never would have expected that I would have had to resort to > spoofing on pages at mozilla.org. I believe it was discussed in #amo and a fix for not just SeaMonkey but for all the other Firefox forks (like Ice Weasel, Pale Moon, etc) is in the works. Phil -- Philip Chee , http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Wrapping Header Lines
On 05/08/2015 1:00 AM, Barry Edwin Gilmour wrote: xxyyz wrote on 05/08/15 11:02: When a received SM email is displayed with All Headers, the header lines don't wrap. To see them all, you have to click on each line and move the cursor to the right. This is even more noticeable if there are Attachments, as the header lines stop at the left-hand edge of the Attachments box. The lines wrap properly when the e-mail is printed. How do I get the header lines to wrap when the e-mail is displayed? You could try "View / Message _S_ource" (Ctrl+U) displaying the entire message source, including headers. This scroll-behavior is a lot better than previously, when text simply was curtailed at the edge of the pane, and we could not scroll through to see the text on the latter part of the line. At least now, you can read it, without going to Message-Source. Thank you - a nice, clear explanation! ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.35..
On 8/6/2015 8:44 AM, Thee Chicago Wolf [MVP] wrote: > On Thu, 6 Aug 2015 20:52:47 +1000, David Cox > wrote: > >> On 6/08/2015 6:18 AM, Rob Steinmetz wrote: >>> Edmund Wong wrote: Hi, I regret to be the bearer of bad news; but as it stands, the worst case scenario (and likely the actual case) is that 2.35 is not going to be released in July. The new goal is to release it in early August. The past month has been mired in fire-fighting bustages, getting repacks and builds working (as of this writing, trunk is busted) as well as the need to get the backend buildbot code updated to reflect that we no longer depend on CVS. I apologize for the delay and thank everyone for your patience. Edmund >>> Thanks for the update. At this point I'd rather wait until things get >>> sorted out than rush into an unstable situation. >> FWIW I've been running Callek's contributed win32 2.35 build for a >> couple of weeks with no issues. But then, I have a pretty simple setup >> with few addons but do mix POP and Imap mail servers. > > I was running that for a while with good luck as well. I've had good > luck with a 2.36 contrib build from here: > https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/ > I won't be sad if 2.34 > 2.36 is skipped in favor of a 2.37 build to > be in parity with FF40. > > - Thee Chicago Wolf [MVP] > I too played with 2.35 and 2.36 (54) without problems, but just in case there may be problems that did not affect what I do, I'm back here on 2.33.1. An apparently all my add-ons worked. I manually changed some of them to work with all versions of 2.* -- Ed, W3BNR HTTP://JonesFarm.us/W3BNR Tags by Pick-a-Tag 1.60ß1 "I made a wrong mistake."-Yogi Berra (1925-) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Speaking of brain-dead browser sniffing...
Philip Chee wrote: I believe it was discussed in #amo and a fix for not just SeaMonkey but for all the other Firefox forks (like Ice Weasel, Pale Moon, etc) is in the works. Good to know about. Thanks for the update. Smith ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
