Files
margin-mail/src-tauri/fixtures/golden/quoted-reply-blockquote.txt
T
pj eb59cb5f8d build the app, and ship it on Linux and Windows as well as macOS
The client itself: the sync engine and mirror, the Gmail and IMAP providers,
the screener, the three boxes and two piles, compose and send, the sanitiser
and tracker stripping, contacts, clips, backup, notifications and the guide.

The pipeline that ships it. Three runners now build in parallel and the
publish gate wants all four platform keys in latest.json before a release
leaves draft. Linux gets two more packages Tauri does not build: a flatpak
repackaged from the deb against GNOME 48, and a Nix package that relinks the
deb against nixpkgs so it runs as a native Wayland client rather than through
Xwayland. CI runs the Rust suite on all three desktops rather than on Linux
alone, and rebuilds the flatpak manifest on every push to main.

Two things that were only ever exercised on macOS and were wrong everywhere
else. The menu bar was built by adjusting the submenus macOS is given, so on
a platform whose default menu has no File or View the new File menu landed
after Edit, Check for Updates landed nowhere, and the three places and the
reading pane had no menu at all. The deb declared libwebkit2gtk-4.1-0 and
libgtk-3-0 twice, because tauri.conf.json named the dependencies Tauri
already emits.

The updater key exists now, so releases can sign their artifacts.
2026-09-06 12:15:30 +05:30

48 lines
1.6 KiB
Plaintext

render-version: 2
message-id: [email protected]
in-reply-to: [email protected]
references-first: [email protected]
from: Dev Patel <[email protected]>
to: Priyanshu Jain <[email protected]>
cc: -
bcc: -
reply-to: -
date-ms: 1788191095000
subject: Re: Slides from the talk
is-html: true
surface: theme
snippet: Here they are, plus the reading list I mentioned. The paper on cache oblivious layouts is the one to start with.
list-id: -
auto-submitted: -
precedence: -
unsubscribe: -
blocked-images: 0
--- html ---
<div dir="ltr">Here they are, plus the reading list I mentioned. The paper
on cache oblivious layouts is the one to start with.</div>
--- quoted ---
<br>
<div>
<div dir="ltr">On Mon, 31 Aug 2026 at 18:40, Priyanshu
Jain &lt;<a href="mailto:[email protected]" target="_blank" rel="noopener noreferrer">[email protected]</a>&gt; wrote:</div>
<blockquote style="margin:0 0 0 0.8ex;border-left:1px solid #ccc;padding-left:1ex">
<div dir="ltr">Good talk. Could you send the slides, and the reading list
you put up at the end?</div>
<br>
<div>
<div dir="ltr">On Fri, 28 Aug 2026 at 12:02, Dev Patel
&lt;<a href="mailto:[email protected]" target="_blank" rel="noopener noreferrer">[email protected]</a>&gt;
wrote:</div>
<blockquote style="margin:0 0 0 0.8ex;border-left:1px solid #ccc;padding-left:1ex">
<div dir="ltr">Talk is on Monday at six, room 4.02. Come if you are free.</div>
</blockquote>
</div>
</blockquote>
</div>
--- text ---
Here they are, plus the reading list I mentioned. The paper on cache
oblivious layouts is the one to start with.