<div dir="auto">You can send a link to the screenshot instead of attaching it.</div><div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 16 May 2022 at 9:11 PM Shaping via Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st">cuis-dev@lists.cuis.st</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word"><div class="m_2506470674601867018WordSection1">Has anyone yet read the previous e-mail with the subject shown above? The e-mail contains a Pharo screenshot of an inspector, and discusses rich-text rendering speed. The e-mail was held up by the server. Can it be allowed to go through, so that I can see some meaningful discussion about high-performance text? Slow rendering of rich text is my main pain-point right now. Why are emails with a screenshot being stopped? The e-mail was not that big, and drive space is cheap these days. Why is the Cuis community not using Discord? I find it much easier, quicker, and productive. </div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word"><div class="m_2506470674601867018WordSection1"> Shaping </div></div>-- Cuis-dev mailing list <a href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a> <a href="https://lists.cuis.st/mailman/listinfo/cuis-dev" rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a> </blockquote></div></div>