Re: size of profile

2020-02-04 Thread mozilla-lists . mbourne 

alexyu wrote:

mozilla-lists.mbou...@spamgourmet.com wrote, on 01 Feb 20 16:19:


alexyu wrote:


NFN Smith wrote, on 31 jan 20 13:44:
For me, one minor annoyance is that there's no way of discarding 
graphical content that's embedded in a message body.




Frequently, you can get rid of such content using this option:

View / Message Body As / All Body Parts

That way, items which are not considered "attachments" can be still 
'deleted' (or perhaps 'detached'), and then you can compact the message.


I'm intrigued, since I occasionally want to do similar (even more 
occasionally, in extreme cases, I've resorted to manually editing the 
mailbox file).  However, on SeaMonkey 2.49.5, the only options I see 
under View / Message Body As are Original HTML, Simple HTML and Plain 
Text.  Is "All Body Parts" a new addition in 2.53 or perhaps added by 
an extension?


It's been a part of SM for a long time, but it's not a default.
In 'about:config', just set: "mailnews.display.show_all_body_parts_menu" 
to 'true'.


All these years and I didn't know about that one.  Thanks for that.  I 
just happened to have need to do this again.  Enabling that option and 
deleting the "attachment" for an inline image has exactly the same 
effect as what I'd done manually a few times - but much quicker, easier 
and less error-prone!  I'd even been manually tweaking the MIME parts 
for the deleted images so that they show up as "Deleted: ..." in the 
attachments list like normal deleted attachments do.


To edit messages' headers, or even their full source, there is an 
extension:


"Header Tools Lite", by Paolo "Kaosmos"


That could be useful on the odd occasion.  I don't often want to edit 
existing messages other than to delete large attachments - which take 
less space saved as separate files and avoids huge mailbox files.


--
Thanks,
Mark.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Twitter will not show any pictures

2020-02-04 Thread mozilla-lists . mbourne 

RainerBielefeldNG wrote:

Hi,

since today my unofficial (by wg9s) De SeaMonkey 2.53.2 beta 1 pre 
Mozilla/5.0  (NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 
Build 20200131130001  (Default Classic Theme, newly created User 
Profile) on German WIN7 64bit

has stopped to show Pictures on Twitter:


a) Other Web pages not affected, Imgur, Instagram, ... work without 
problems


b) Related to my SeaMonkey User Profile. Using a different User Profile 
the problem isnot visible.


c) Not related to my Twitter Profile: Using different Twitter Profile 
does not heal the problem


d) Safe Mode does not help.

e) Error console shows many Errors

and Warnings


No Errors shown in different SM User Profile


f) 
contains one of the very few pictures which will work

g) also happens with older 2.53 SM versions, also 32 bit.

I am helpless. Any ideas from your side?


A few thoughts, which may or may not help...

Make sure you're not blocking images or JavaScript from twitter.com or 
twimg.com (check for site-specific permissions in the Data Manager and 
any ad/script-blocking add-ons, as well as the global preferences).


Try deleting any cookies for twitter.com and twimg.com.  I've 
occasionally had sites break after something is updated at their end, 
but only if you have cookies which were set by their old version - it 
works if there are no cookies to start with (so they think there's no 
problem, since it all works fine from a clean state).


It might also be worth clearing the cache, in case you're picking up an 
old cached version of one of their scripts.


--
Mark.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Build error on FreeBSD

2020-02-04 Thread Frank-Rainer Grahl 

Best to install an additional rust version. 1.36 is tested.


rustup toolchain list should list the installed ones and

rustup  toolchain install 1.36- installs a second one.

Can be used with

rustup default 1.36.0-

Also use
ac_add_options --disable-webrender
ac_add_options --disable-stylo

FRG

BERTRAND Joël wrote:

Hello,

As seamonkey is not available in FreeBSD ports, I have tried to build
2.53.1 from sources.

gmake -f client.mk build aborts with following rust (rust 1.38) error:


error[E0506]: cannot assign to `self.input.cached_token` because it is
borrowed
-->
/root/seamonkey/seamonkey-2.53.1b1/mozilla/third_party/rust/cssparser/src/parser.rs:388:17
 |
364 | pub fn next_including_whitespace_and_comments(&mut self) ->
Result<&Token<'i>, BasicParseError<'i>> {
 |   - let's call the
lifetime of this reference `'1`
...
377 | Some(ref cached_token) if cached_token.start_position
== token_start_position => {
 |   borrow of
`self.input.cached_token` occurs here
...
388 | self.input.cached_token = Some(CachedToken {
 | ^^^ assignment to borrowed
`self.input.cached_token` occurs here
...
400 | Ok(token)
 | - returning this value requires that
`self.input.cached_token.0` is borrowed for `'1`

How can I fix this issue to build Seamonkey on FreeBSD ? I have found
some patches to fix this error but no one seems to works.

Best regards,

JKB


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Build error on FreeBSD

2020-02-04 Thread BERTRAND Joël 
Hello,

As seamonkey is not available in FreeBSD ports, I have tried to build
2.53.1 from sources.

gmake -f client.mk build aborts with following rust (rust 1.38) error:


error[E0506]: cannot assign to `self.input.cached_token` because it is
borrowed
   -->
/root/seamonkey/seamonkey-2.53.1b1/mozilla/third_party/rust/cssparser/src/parser.rs:388:17
|
364 | pub fn next_including_whitespace_and_comments(&mut self) ->
Result<&Token<'i>, BasicParseError<'i>> {
|   - let's call the
lifetime of this reference `'1`
...
377 | Some(ref cached_token) if cached_token.start_position
== token_start_position => {
|   borrow of
`self.input.cached_token` occurs here
...
388 | self.input.cached_token = Some(CachedToken {
| ^^^ assignment to borrowed
`self.input.cached_token` occurs here
...
400 | Ok(token)
| - returning this value requires that
`self.input.cached_token.0` is borrowed for `'1`

How can I fix this issue to build Seamonkey on FreeBSD ? I have found
some patches to fix this error but no one seems to works.

Best regards,

JKB
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey