From: Stuart Morrow <morrow.stuart@gmail.com>
To: 9front@9front.org
Subject: [9front] Re: speaking of screenlock
Date: Thu, 15 Jul 2021 22:47:37 +0100 [thread overview]
Message-ID: <CABB-WO85Vy27QfK7pZ=Vt+REhDMiC9ERSRd0q3OaAryk18eNqg@mail.gmail.com> (raw)
In-Reply-To: <CABB-WO9cLWnt62EbCQx8SSx=2s_mJJtB7GpjaUi5f15cSNAs=A@mail.gmail.com>
Actually, I don't get what it is about screenlock in the first place
that different procs can't access each other's malloc'd objects. It
seems other programs can do this just fine.
next prev parent reply other threads:[~2021-07-15 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 14:27 [9front] " Stuart Morrow
2021-07-15 21:47 ` Stuart Morrow [this message]
2021-07-15 23:04 ` [9front] " ori
2021-07-16 9:07 ` Stuart Morrow
2021-07-16 10:01 ` cinap_lenrek
2021-07-16 10:50 ` Stuart Morrow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABB-WO85Vy27QfK7pZ=Vt+REhDMiC9ERSRd0q3OaAryk18eNqg@mail.gmail.com' \
--to=morrow.stuart@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).