unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org,  Kyle Meyer <kyle@kyleam.com>
Subject: Re: master c86995d07e9: Enable code block evaluation when generating .org manuals
Date: Fri, 07 Jun 2024 11:54:55 +0800	[thread overview]
Message-ID: <87r0d9flv4.fsf@yahoo.com> (raw)
In-Reply-To: <87h6e6i1mg.fsf@gmail.com> (Robert Pluim's message of "Thu, 06 Jun 2024 16:31:35 +0200")

Robert Pluim <rpluim@gmail.com> writes:

>>>>>> On Thu,  6 Jun 2024 08:36:16 -0400 (EDT), Eli Zaretskii <eliz@gnu.org> said:
>
>     Eli> diff --git a/doc/misc/Makefile.in b/doc/misc/Makefile.in
>     Eli> index 2841916dc89..b26d3525a22 100644
>     Eli> --- a/doc/misc/Makefile.in
>     Eli> +++ b/doc/misc/Makefile.in
>     Eli> @@ -250,6 +250,7 @@ define org_template
>     Eli>   $(1:.org=.texi): $(1) ${top_srcdir}/lisp/org/ox-texinfo.el
>     Eli>  	$${AM_V_GEN}cd "$${srcdir}" && $${emacs} -l ox-texinfo \
>     Eli>  	  --eval '(setq gc-cons-threshold 50000000)' \
>     Eli> +	  --eval '(setq org-confirm-babel-evaluate nil)' \
>     Eli>  	  -f org-texinfo-export-to-texinfo-batch $$(notdir $$<) $$(notdir $$@)
>     Eli>  endef
>
> This has set off my paranoia alarm. So anyone that manages to
> sneak malicious emacs lisp code into the org manual gets to run that
> code on the machines of everyone who builds emacs from source?

No doubt you meant that anyone who manages to sneak malicious code into
Emacs gets to run that code on the machines of everyone who builds Emacs
from source, which is stating the obvious...



  parent reply	other threads:[~2024-06-07  3:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <171767737644.19678.784876979840850798@vcs2.savannah.gnu.org>
     [not found] ` <20240606123616.DE7C9C1F9EF@vcs2.savannah.gnu.org>
2024-06-06 14:31   ` master c86995d07e9: Enable code block evaluation when generating .org manuals Robert Pluim
2024-06-07  2:39     ` Kyle Meyer
2024-06-07  8:50       ` Stefan Kangas
2024-06-09 17:55         ` Ihor Radchenko
2024-06-09 18:26           ` Stefan Kangas
2024-06-09 18:45             ` Ihor Radchenko
2024-06-09 19:19               ` Stefan Kangas
2024-06-15 14:38                 ` Ihor Radchenko
2024-06-15 14:47                   ` Stefan Kangas
2024-06-17 11:46                     ` Ihor Radchenko
2024-06-18 19:37                       ` Stefan Kangas
2024-06-07  3:54     ` Po Lu [this message]
2024-06-07  4:26       ` tomas
2024-06-07  5:13         ` Po Lu
2024-06-07  6:38           ` tomas
2024-06-07  6:42         ` Eli Zaretskii
2024-06-07  7:38           ` Robert Pluim
2024-06-07 11:01             ` Eli Zaretskii
2024-06-07 11:17               ` Po Lu
2024-06-07  8:12           ` tomas
2024-06-09  2:16     ` Richard Stallman
2024-06-09 18:12     ` Ihor Radchenko
2024-06-09 18:27       ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0d9flv4.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=rpluim@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).