From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id QPPbInnR1WaHKAAAqHPOHw:P1 (envelope-from ) for ; Mon, 02 Sep 2024 14:53:45 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id QPPbInnR1WaHKAAAqHPOHw (envelope-from ) for ; Mon, 02 Sep 2024 16:53:45 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=inria.fr header.s=dc header.b=TcW8s0TZ; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=inria.fr ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1725288825; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=bryM5ELnS3QYSI3UBncvmCK+eSD+4V/rqUdcBO/sqlA=; b=lHZUh9HEwurmjOhGN2+cCz32yJnwmhNzEX/HH0JsbpdUXiGzD9uyF8QqkW6fv2hXxFoQkP BHAr5YYya9B0ZKPz3RNmUBFUBKmlATZtG4mkiD+nXx4WDag0puEFr7SwfEeRw6q4FpJU27 YbbiCpTmEkWwwGWO054Duv5jHrf0de6x/TKQGx0kwaLmc/o/oi9UVQXRvlpqzv93zJ1vS5 kx+OC9x4htTGfM2hKPLldd+tU8MFPlgBNceTccSto1rQ1yUJdgTDxaZ/HnprBDz+zxcxgo i17NjuPQ8XRYpx4iCfWtfdhiPLYPII8d90ffS6Z5EcSR3wKVkMee4r3sE260KA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=inria.fr header.s=dc header.b=TcW8s0TZ; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=inria.fr ARC-Seal: i=1; s=key1; d=yhetil.org; t=1725288825; a=rsa-sha256; cv=none; b=NHi1yAuYTjlcIMerHE1uncVLDKNY9Pqt2rZHXdwqUlA8BIRedReIucaxr3G6hr66yw7t4t lOI8c2u4rCRePIeLTN5D+XfM6NeomdzTn/5WUQXN4cr/3ygjSVUu6nUeSLXa9FyawuiJ8s XAcmSuDGHWQwcC8HpwhGy8IqemnH5y3qDbxW9OU6+GW1ec7aG19n3qI7WmknXlMrEikcAI f6GhmuvwEJ0VKT/4zSZTU7Z5cIdq/MowRM3mp+Peu+tbFxykY6dcMPNkfCRaDDkkoUbNVU aO/+nQZbi3RSJA+NBvbraC+O40Frwpm3ak7WXU3dVjCDrWZ9vsHGgUp2QuMZbg== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id ACFD177F0D for ; Mon, 2 Sep 2024 16:53:44 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sl8Q6-0004E1-V1; Mon, 02 Sep 2024 10:52:42 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sl8Q4-0004Dn-9j for emacs-orgmode@gnu.org; Mon, 02 Sep 2024 10:52:40 -0400 Received: from mail2-relais-roc.national.inria.fr ([192.134.164.83]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sl8Pw-0007nn-OT for emacs-orgmode@gnu.org; Mon, 02 Sep 2024 10:52:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=date:from:to:cc:message-id:subject:mime-version; bh=bryM5ELnS3QYSI3UBncvmCK+eSD+4V/rqUdcBO/sqlA=; b=TcW8s0TZNPDYdDSnMhYIWuyqF34M1YMgOnvyhjLhw99xDHa3KAWUJRCd /WWcqN3NpUDQEqsw0ZlwaoVV7K+2erTwHpXTRNOgGEuKgaQim0nixvOER iDUXL/rTM1seQYbLqVazNYT2sq2MY+gIvEIYz3a/9hn8iIuHSq3R4C7J9 g=; Received-SPF: Pass (mail2-relais-roc.national.inria.fr: domain of gilles.marait@inria.fr designates 128.93.142.5 as permitted sender) identity=mailfrom; client-ip=128.93.142.5; receiver=mail2-relais-roc.national.inria.fr; envelope-from="gilles.marait@inria.fr"; x-sender="gilles.marait@inria.fr"; x-conformance=spf_only; x-record-type="v=spf1"; x-record-text="v=spf1 include:mailout.safebrands.com a:basic-mail.safebrands.com a:basic-mail01.safebrands.com a:basic-mail02.safebrands.com ip4:128.93.142.0/24 ip4:192.134.164.0/24 ip4:128.93.162.160 ip4:89.107.174.7 mx ~all" Received-SPF: None (mail2-relais-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@zcs2-store2.inria.fr) identity=helo; client-ip=128.93.142.5; receiver=mail2-relais-roc.national.inria.fr; envelope-from="gilles.marait@inria.fr"; x-sender="postmaster@zcs2-store2.inria.fr"; x-conformance=spf_only X-IronPort-AV: E=Sophos;i="6.10,195,1719871200"; d="scan'208,217";a="181076813" X-MGA-submission: =?us-ascii?q?MDEZ0GocULOkj/38eldNNL3QEWX2ceHFbqDkrn?= =?us-ascii?q?IJuyn9T+G9emy2gOS65QGIYtV5m8fbcw5bTctYMNg914eKRAo+chx4fI?= =?us-ascii?q?8zDbyEc2PQEz/UcCD4y6tKc5Dy8JGm2UdOgiG4jNJLuo3yPYJuyrwGvD?= =?us-ascii?q?IGF+RSbmQ2XrEctY2CveNdwg=3D=3D?= Received: from zcs2-store2.inria.fr ([128.93.142.5]) by mail2-relais-roc.national.inria.fr with ESMTP; 02 Sep 2024 16:52:27 +0200 Date: Mon, 2 Sep 2024 16:52:26 +0200 (CEST) From: Gilles Marait To: emacs-orgmode@gnu.org Cc: emmanuel agullo Message-ID: <652111520.30366591.1725288746643.JavaMail.zimbra@inria.fr> Subject: Change behavior of "org-babel-tangle-publish" from org 9.6 to 9.7 -- deleting source files and not tangling properly MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_8fb4c73a-a26b-49da-a42d-337266218c6b" X-Originating-IP: [194.199.1.52] X-Mailer: Zimbra 10.0.8_GA_4611 (ZimbraWebClient - FF129 (Linux)/10.0.8_GA_4611) Thread-Index: 1kxKrS5ZfJ4KIqqxz1ZvoEmsCiKVIQ== Thread-Topic: Change behavior of "org-babel-tangle-publish" from org 9.6 to 9.7 -- deleting source files and not tangling properly Received-SPF: pass client-ip=192.134.164.83; envelope-from=gilles.marait@inria.fr; helo=mail2-relais-roc.national.inria.fr X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Spam-Score: -12.24 X-Migadu-Queue-Id: ACFD177F0D X-Migadu-Scanner: mx10.migadu.com X-Migadu-Spam-Score: -12.24 X-TUID: nN2UqDacxdwk --=_8fb4c73a-a26b-49da-a42d-337266218c6b Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello everyone, I encountered a change of behavior since org version 9.7 than removes my source files instead of tangling them at the correct location, using "org-babel-tangle-publish". I have not found in the changelog any description of something that could explain this change, so I report it here. I'll try to show a minimal example of this issue. * Description I have the following file structure. . =E2=94=9C=E2=94=80=E2=94=80 org =E2=94=82=C2=A0=C2=A0 =E2=94=94=E2=94=80=E2=94=80 Code.org =E2=94=9C=E2=94=80=E2=94=80 publish.el =E2=94=94=E2=94=80=E2=94=80 src =E2=94=94=E2=94=80=E2=94=80 code.cpp In the "org" directory, I have my org file that describes my code in literate programming. It's content is: #+begin_src c++ :tangle ../src/code.cpp=20 int a =3D 3; #+end_src The expected behavior is to generate the file "code.cpp" in the src directory with the tangle mechanism. In this example code.cpp only contains the line: int a =3D 3; To generate the sources from the org files, I use org-publish. The code of publish.el is: (require 'package) (package-initialize) (require 'org) (require 'ox-publish) (setq org-publish-project-alist =09(list =09 (list "generate-source-code" =09 :base-directory "./org" =09 :base-extension "org" =09 :recursive t =09 :publishing-function '(org-babel-tangle-publish) =09 :publishing-directory "." =09 :auto-sitemap nil))) (provide 'publish) ;;; publish.el ends here To use the publish from a script I use the following command: emacs --batch --load publish.el --eval '(org-publish "generate-source-cod= e")' * With org-mode 9.6 It works as expected, the code in "Code.cpp" is tangled into "src/code.cpp"= . * With org-mode 9.7 I can see "code.cpp" is tangled at the root directory "./code.cpp", but the file "src/code.cpp" that existed previously is deleted. * Additional information emacs version: "29.4" org-version: - Test with version 9.7.10 (commit 5ebd973e09d7a46d056f1cd9b5efc44e878cce9c= ) - Test with version 9.6.30 (commit 071c6e986c424d2e496be7d0815d6e9cd83ae4e6= ) If I use directly "org-babel-tangle-file" I don't have the problem, the file in tangled to the right location: emacs --batch --eval "(require 'org)" --eval '(org-babel-tangle-file "./org= /Code.org")' * Bonus question As a guix user, I use contained environments as much as possible. In the case described above, I generate an environment without git. I get the following warning: Error: (file-missing "Searching for program" "No such file or directory" "g= it") It does not have any consequence on the tangling process, but I was wondering if it was expected that my org-publish process depends on git ? Would there be any benefit to add it to my environment ? * Repository I created a repository with some scripts to reproduce the error, using guix to control the environment. https://gitlab.inria.fr/gmarait/debug-org-9.7=20 Thank you and best regards,=20 Gilles Marait=20 --=_8fb4c73a-a26b-49da-a42d-337266218c6b Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable 
Hello everyone,

I encountered a change of behavior since org version 9.7 than removes
my source files instead of tangling them at the correct location, using
"org-babel-tangle-publish".

I have not found in the changelog any description of something that
could explain this change, so I report it here.

I'll try to show a minimal example of this issue.

* Description

I have the following file structure.

.
=E2=94=9C=E2=94=80=E2=94=80 org
=E2=94=82   =E2=94=94=E2=94=80=E2=94=80 Code.org
=E2=94=9C=E2=94=80=E2=94=80 publish.el
=E2=94=94=E2=94=80=E2=94=80 src
    =E2=94=94=E2=94=80=E2=94=80 code.cpp

In the "org" directory, I have my org file that describes my code in
literate programming. It's content is:

#+begin_src c++ :tangle ../src/code.cpp
    int a =3D 3;
#+end_src

The expected behavior is to generate the file "code.cpp" in the src
directory with the tangle mechanism. In this example code.cpp only
contains the line:

int a =3D 3;

To generate the sources from the org files, I use org-publish. The
code of publish.el is:

  (require 'package)
  (package-initialize)
  (require 'org)
  (require 'ox-publish)
  (setq org-publish-project-alist
=09(list
=09 (list "generate-source-code"
=09       :base-directory "./org"
=09       :base-extension "org"
=09       :recursive t
=09       :publishing-function '(org-babel-tangle-publish)
=09       :publishing-directory "."
=09       :auto-sitemap nil)))
  (provide 'publish)
  ;;; publish.el ends here

To use the publish from a script I use the following command:

  emacs --batch --load publish.el --eval '(org-publish "generate-source-cod=
e")'

* With org-mode 9.6

It works as expected, the code in "Code.cpp" is tangled into "src/code.cpp"=
.

* With org-mode 9.7

I can see "code.cpp" is tangled at the root directory "./code.cpp",
but the file "src/code.cpp" that existed previously is deleted.

* Additional information

emacs version: "29.4"

org-version:
- Test with version 9.7.10 (commit 5ebd973e09d7a46d056f1cd9b5efc44e878cce9c=
)
- Test with version 9.6.30 (commit 071c6e986c424d2e496be7d0815d6e9cd83ae4e6=
)

If I use directly "org-babel-tangle-file" I don't have the problem,
the file in tangled to the right location:

emacs --batch --eval "(require 'org)" --eval '(org-babel-tangle-file "./org=
/Code.org")'

* Bonus question

As a guix user, I use contained environments as much as possible. In
the case described above, I generate an environment without git. I get
the following warning:

Error: (file-missing "Searching for program" "No such file or directory" "g=
it")

It does not have any consequence on the tangling process, but I was
wondering if it was expected that my org-publish process depends on
git ? Would there be any benefit to add it to my environment ?

* Repository

I created a repository with some scripts to reproduce the error, using
guix to control the environment.

https://gitlab.inria.fr/gmarait/debug-org-9.7


Thank you and best=
 regards,
Gilles Marait
--=_8fb4c73a-a26b-49da-a42d-337266218c6b--