From: Augusto Stoffel <arstoffel@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [RFC] MIME attachments for comint
Date: Tue, 28 Sep 2021 18:05:35 +0200 [thread overview]
Message-ID: <87wnn0lm7k.fsf@gmail.com> (raw)
In-Reply-To: <jwv1r59rc2m.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 27 Sep 2021 16:37:19 -0400")
On Mon, 27 Sep 2021 at 16:37, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> Sounds like a cute package, thanks.
>
>> Here are some more assorted observations:
>
> Anything to say about security implications/measures?
Good question, I didn't think about this. I guess it's safe to feed
`create-image', `svg-image' and shr with any kind of evil data, no?
But TeX markup could in principle execute arbitrary code. I'm relying
on Org for TeX rendering, so I'd have to check how careful it is about
that.
>
>
> Stefan
next prev parent reply other threads:[~2021-09-28 16:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 19:00 [RFC] MIME attachments for comint Augusto Stoffel
2021-09-27 20:37 ` Stefan Monnier
2021-09-28 16:05 ` Augusto Stoffel [this message]
2021-09-28 19:26 ` Stefan Monnier
2021-09-30 6:02 ` Richard Stallman
2021-09-30 7:09 ` Augusto Stoffel
2021-10-02 23:17 ` Richard Stallman
2021-10-03 7:48 ` Augusto Stoffel
2021-10-04 22:23 ` Richard Stallman
2021-09-30 8:49 ` Gregory Heytings
2021-10-04 22:25 ` Richard Stallman
2021-09-30 7:34 ` Colin Baxter
2021-09-28 5:36 ` Lars Ingebrigtsen
2021-09-28 16:09 ` Augusto Stoffel
2021-09-28 16:29 ` Robin Tarsiger
2021-09-28 18:22 ` Augusto Stoffel
2021-09-29 5:35 ` Lars Ingebrigtsen
2021-10-17 16:20 ` Stefan Monnier
2021-10-17 16:32 ` Stefan Monnier
2021-10-18 8:22 ` Augusto Stoffel
2021-10-18 16:44 ` comint-mime and loccur update (was: [RFC] MIME attachments for comint) Stefan Monnier
2021-10-20 12:17 ` Alexey Veretennikov
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=87wnn0lm7k.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.