From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id WI0IOmahK2LemwAAgWs5BA (envelope-from ) for ; Fri, 11 Mar 2022 20:22:14 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id EIa1NmahK2JgAQAAauVa8A (envelope-from ) for ; Fri, 11 Mar 2022 20:22:14 +0100 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 4C949100DA for ; Fri, 11 Mar 2022 20:22:14 +0100 (CET) Received: from localhost ([::1]:59014 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nSkq4-0002uZ-VG for larch@yhetil.org; Fri, 11 Mar 2022 14:22:12 -0500 Received: from eggs.gnu.org ([209.51.188.92]:52472) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nSkpC-0002sq-Ub for emacs-orgmode@gnu.org; Fri, 11 Mar 2022 14:21:18 -0500 Received: from [2a00:1450:4864:20::432] (port=42575 helo=mail-wr1-x432.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nSkpA-0001GS-6R for emacs-orgmode@gnu.org; Fri, 11 Mar 2022 14:21:18 -0500 Received: by mail-wr1-x432.google.com with SMTP id u10so14386224wra.9 for ; Fri, 11 Mar 2022 11:21:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:subject:date:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=sC9lvDJ02AmytAqvdsPsGbDtoSc8gdfjOaTw/2JGOdQ=; b=q1WZT7rFjq15oWTtRm6mtdhI0u19+N5Lz9Ry9OzfIcv6OBdj9gz4uVQCKPXMTWZIwA nXaqMZQiyUVlKrJ8/u1UhlgWMp0oHx6/yMvpkYH0A+dqtxKzAV4yUkPAoX94/yQNiDvi Ld+WA27pFDfXpDCa6HmDrGK2+x6x/no8JJ4bmni2XfMPb0lkN1Xbwo8iuM9N7/bbj0Zj GzRiGFMj9o1kCsy+xDmv00ksqwmRcKZ54lrUWS3eNOow9Pnvgqa1+K2QzDJ4u7dGFOF0 dIg0IZZ6VD5848tc19KBgiM02riTcrXTtfRZq8sAUzlW4ev1mY1ET2oM7KkKlkpWBmoL CWPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=sC9lvDJ02AmytAqvdsPsGbDtoSc8gdfjOaTw/2JGOdQ=; b=74znjvL8CmbAzJdCYVEcLTqXmhJvlQOzpxP7tXTEYs4pysot3pTzCdK+GOvn9Pwhy3 bceTMW2I6Dpo5+i0x2hfAsdUuPhumnZUVkVU4VDDX17QAPvnhsM8KraZxzS4Pls2qX1K gv+C/GcFYDF+xUlhgHrEUrzSSM8nVEzATm7Femh6Y+JfsrkcqDJarMElD4virAPZdkYS LpB50RQlWyRzAfzVzXdJAeIUeLcokwx7lMhHUhP4FC9RR3biGgn0wuolqMurOKxc3iMK WrikJPRb2paLwA8QV1ezA/xQFsmRjmYjytqxXRqf4NCnmXsd9Qlgcb6MqITGkXxn3w+w 2q6w== X-Gm-Message-State: AOAM531SDNIbU615dh4CBa5AGero9YpF8g9rWwYgosgWdq3aq0OCJX5E qchG7MFHIgtCxw52ruq/2ZvKVgMAVjk= X-Google-Smtp-Source: ABdhPJxve8yx/Kzbj1M4B5Mqp2uMiU/egyMwKj47B+LEQXD989ZcY0iwylAA4H1PB0dMkuk7z5Mbtg== X-Received: by 2002:a5d:58f2:0:b0:1f9:7df6:c857 with SMTP id f18-20020a5d58f2000000b001f97df6c857mr8560006wrd.81.1647026474249; Fri, 11 Mar 2022 11:21:14 -0800 (PST) Received: from pluto.localnet (aaubervilliers-654-1-108-126.w86-212.abo.wanadoo.fr. [86.212.240.126]) by smtp.gmail.com with ESMTPSA id n15-20020a05600c4f8f00b003842f011bc5sm11805854wmq.2.2022.03.11.11.21.13 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 11 Mar 2022 11:21:13 -0800 (PST) From: chris To: emacs-orgmode@gnu.org Subject: Re: ox-publish: Some starting problems Date: Fri, 11 Mar 2022 20:21:12 +0100 Message-ID: <5552297.DvuYhMxLoT@pluto> In-Reply-To: <7395938a0e6b06139239bc70ba7c2b19@posteo.de> References: <4f18b7eac091dd14cfaf5ed10e7c63ed@posteo.de> <7395938a0e6b06139239bc70ba7c2b19@posteo.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart5806142.lOV4Wx5bFT" Content-Transfer-Encoding: 7Bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a00:1450:4864:20::432 (failed) Received-SPF: pass client-ip=2a00:1450:4864:20::432; envelope-from=inkbottle007@gmail.com; helo=mail-wr1-x432.google.com X-Spam_score_int: -3 X-Spam_score: -0.4 X-Spam_bar: / X-Spam_report: (-0.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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, PDS_HP_HELO_NORDNS=0.659, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no 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" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1647026534; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=sC9lvDJ02AmytAqvdsPsGbDtoSc8gdfjOaTw/2JGOdQ=; b=NyFcpMA5DQ//eQS1cmRCd8v1whXz5sEIW27H+xHBTVvBMuyLQR2VL7L7SXNR5UGkzSlOIr orHiT/LGTbHCw/U8U06boayQuDYbamYRQEyvPRsCEOLfpG0IeH9u2AMz8HEHlFoy2QBO/f Xd6WhxvLgnA2l7xcf53jTVgrvH6VFXVin7Z99riAV/BvLihz5STVeK0ER/McSC/3D6CeBQ 4BCBL6QTP+W5M7c2B2TktYvvF+GwsjolKgRa/a0bfGncuJeyqgeISm33PyfKhB499qLmyu mGIsk8bdd5eedby2S3lSXur/X/On0u6jDuarFq2sPSlZsorFmsPqF0JPZtSaNg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1647026534; a=rsa-sha256; cv=none; b=bJnvw/uh01uVCUOm0rfaDImf7UcN3Xuw4w51juRr0ArgLrNdIse1YbLbm6YXLeGB1C+4ob gha8IxQZWrcA2e9OyKOvIEeXsn3Uki1BShD2boIYFcnwHO8t1XhC2/8XPViub8ia2uhhap vxi+SCP/sixxV4JmgqJwR4T4md+os3rVS3iwpjxCjNb9izGwwUFElBUhF9q3I2rbZkxu/f Z7RvS1Dp0P7+lKT9BOYZPEXlUdSfRAo5ImTbvNAi/n5qUeneesk69PcALg29EvJ9t0YhdM tA8zLuQ7vBPz0YsffY7v/VUY+awrmrjNfeJuKeXd/v6OVNk1dnCM/1S+uzEw2Q== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=q1WZT7rF; dmarc=pass (policy=none) header.from=gmail.com; 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" X-Migadu-Spam-Score: -6.69 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=q1WZT7rF; dmarc=pass (policy=none) header.from=gmail.com; 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" X-Migadu-Queue-Id: 4C949100DA X-Spam-Score: -6.69 X-Migadu-Scanner: scn0.migadu.com X-TUID: pUSRtfiagHy8 This is a multi-part message in MIME format. --nextPart5806142.lOV4Wx5bFT Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Hi Christian, I've received the following in my personal email box, and I think it is related to this thread, so I paste it here: On Thursday, 10 March 2022 06:54:22 CET c.buhtz@posteo.jp wrote: > Hello together, > > I do not understand all details. But it seems to me that currently > ox-publish is not fully capable to generate a linked together HTML > files out of org-roam-v2 generated org files because of the ID-linking > of org-roam-v2. > > In my tests it sometimes work and sometimes not. I was not able to > reproduce this. While writing to the list about that problem I was > pointed to that bug report here. > > Kind > Christian And I think that I understand the question, and the general setting related to it. So, on the one hand you have `org-mode/org-id` links like `[[id:32ba80a3-1982-4f43-becb- b0e346a91b0d][hello]]`, which seem the thing to do in the 21st century, the most sensible thing to do IMO, I only use those, `org-roam` only use those. When with `emacs` the links are followed/resolved through a database. For example, the database can be updated through functions like `org-id-update-id-locations`, part of https://github.com/tkf/org-mode/blob/master/lisp/org-id.el[1]. However the use of them is controversial because some deem them as not human friendly enough. So I suppose guidelines should be defined for anything to happen, but I'm not sure people would agree on what to do. And internal ID links, resolved locally through reading in a database, should be thoroughly translated to something accurate and consistent at export-time, and that seems a lot. I myself use `org-roam` and `ID`; considering the difficulties of exporting to html through emacs/org-mode, I just gave up. Thanks, Chris PS: I think you are doing an awesome job at trying to have all that working. On Wednesday, 9 March 2022 17:39:46 CET c.buhtz@posteo.jp wrote: > Dear Max, > > thank's a lot for your help and your patience with a newbie. > > Am 09.03.2022 16:32 schrieb Max Nikulin: > >> 3. > >> I use (setq org-export-with-broken-links t) with and without > >> ":with-broken-links "mark"" to prevend ox-publish stopping when there > >> are broken links. I swear and I also checked that there are only a few > >> of them. But in the HTML output all links are gone. No links. No text > >> for the links. > > > > If you insist on setq than try > > > > (setq org-export-with-broken-links 'mark) > > > > without :with-broken-links. You can get correct value using easy > > customization interface. It does not matter for > > `org-export-with-broken-links', but some custom variables have :set > > property, so the following may be generally better > > > > (custom-set-variables > > > > '(org-export-with-broken-links 'mark)) > > Do you mean that (setq org-export-with-broken-links 'mark) is the same > as :with-broken-links mark? This are just two different ways to set the > same thing? > How do I know as a newbie? ;) > > Why using custom-set variables here? Is there something wrong with just > doing > (org-export-with-broken-links t) > ? > > >> I tried to reproduce this in a minimal example with two new nodes. But > >> for them the links are generated. > > > > It seems, changing project options or global variables does not lead > > to updating of the files if the sources have not modified. > > I do not understand. Do you a see a solution for the problem? > > > There is a known problem with id links. They may be broken if they > > lead to another file: > > inkbottle. org-id with ox-html. Sat, 14 Aug 2021 00:28:35 +0200 > > https://list.orgmode.org/4617246.m1MCmUpgFQ@pluto/ --nextPart5806142.lOV4Wx5bFT Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="UTF-8"

Hi Christian,

I'v= e received the following in my personal email box, and I think it is relate= d to this thread, so I paste it here:

On = Thursday, 10 March 2022 06:54:22 CET c.buhtz@posteo.jp wrote:

>= ; Hello together,

>= ;

>= ; I do not understand all details. But it seems to me that currently

>= ; ox-publish is not fully capable to generate a linked together HTML

>= ; files out of org-roam-v2 generated org files because of the ID-linking

>= ; of org-roam-v2.

>= ;

>= ; In my tests it sometimes work and sometimes not. I was not able to

>= ; reproduce this. While writing to the list about that problem I was

>= ; pointed to that bug report here.

>= ;

>= ; Kind

>= ; Christian

And= I think that I understand the question, and the general setting related to= it.


So, on the one hand you have `org-mode/org-id` links like `[[id:32ba80a3= =2D1982-4f43-becb-b0e346a91b0d][hello]]`, which seem the thing to do in the= 21st century, the most sensible thing to do IMO, I only use those, `org-ro= am` only use those.


When with `emacs` the links are followed/resolved through a database. Fo= r example, the database can be updated through functions like `org-id-updat= e-id-locations`, part of https://github.com/tkf/org-mode/blob/master/lisp/org-i= d.el.


However the use of them is controversial because some deem them as not h= uman friendly enough. So I suppose guidelines should be defined for anythin= g to happen, but I'm not sure people would agree on what to do. And interna= l ID links, resolved locally through reading in a database, should be thoro= ughly translated to something accurate and consistent at export-time, and t= hat seems a lot.


I myself use `org-roam` and `ID`; considering the difficulties of export= ing to html through emacs/org-mode, I just gave up.

Tha= nks,

Chr= is

PS:= I think you are doing an awesome job at trying to have all that working.

On = Wednesday, 9 March 2022 17:39:46 CET c.buhtz@posteo.jp wrote:

>= ; Dear Max,

>= ;

>= ; thank's a lot for your help and your patience with a newbie.

>= ;

>= ; Am 09.03.2022 16:32 schrieb Max Nikulin:

>= ; >> 3.

>= ; >> I use (setq org-export-with-broken-links t) with and without

>= ; >> ":with-broken-links "mark"" to prevend ox-pu= blish stopping when there

>= ; >> are broken links. I swear and I also checked that there are only= a few

>= ; >> of them. But in the HTML output all links are gone. No links. No= text

>= ; >> for the links.

>= ; >

>= ; > If you insist on setq than try

>= ; >

>= ; >=C2=A0=C2=A0=C2=A0 (setq org-export-with-broken-links 'mark)

>= ; >

>= ; > without :with-broken-links. You can get correct value using easy

>= ; > customization interface. It does not matter for

>= ; > `org-export-with-broken-links', but some custom variables have :set<= /p>

>= ; > property, so the following may be generally better

>= ; >

>= ; >=C2=A0=C2=A0=C2=A0 (custom-set-variables

>= ; >=C2=A0=C2=A0=C2=A0

>= ; >=C2=A0=C2=A0=C2=A0=C2=A0 '(org-export-with-broken-links 'mark))

>= ;

>= ; Do you mean that (setq org-export-with-broken-links 'mark) is the same

>= ; as :with-broken-links mark? This are just two different ways to set the

>= ; same thing?

>= ; How do I know as a newbie? ;)

>= ;

>= ; Why using custom-set variables here? Is there something wrong with just

>= ; doing

>= ; (org-export-with-broken-links t)

>= ; ?

>= ;

>= ; >> I tried to reproduce this in a minimal example with two new node= s. But

>= ; >> for them the links are generated.

>= ; >

>= ; > It seems, changing project options or global variables does not lead=

>= ; > to updating of the files if the sources have not modified.

>= ;

>= ; I do not understand. Do you a see a solution for the problem?

>= ;

>= ; > There is a known problem with id links. They may be broken if they

>= ; > lead to another file:

>= ; > inkbottle. org-id with ox-html. Sat, 14 Aug 2021 00:28:35 +0200

>= ; > https://list.orgmode.org/4617246.m1MCmUpgFQ@pluto/

>= ;

>= ; Great to know. Is there a way to monitor (subscribe) to the "dashboa= rd"?

>= ; A bugtracker where I can not track a bug is not a bugtracker. :D

>= ; OK, bugs going to the mailing list. But am I allowed to attach extra

>= ; files (zip) to my mails to the mailinglist? Some bug reports need

>= ; attached files. But I learned and agree that it is rude to attach files

>= ; to a mailing list.

>= ;

>= ; Back to the bug.

>= ; The bug-thread is hard for me to understand because of a lot of internal<= /p>

>= ; details. What is the current essence? Currently there is no way to use

>= ; ox-publish with org-roam-v2 generated org files which use IDs as links?

>= ; But as I told sometimes the links are generated.

>= ;

>= ; Btw: Also in my minimal working example I was not able to surly

>= ; reproduce the problem. Sometimes it works sometimes not. I also deleted

>= ; ~/.emacs.d/org-roam.db, ~/.org-timestamps and ~/.emacs-d/.orgid-indexes

>= ; (I forget the correct name for the latter).

>= ;

>= ; > org-mode is a mode, ox-publish maybe a package (actually unsure).

>= ;

>= ; I thought it was a separate thing because of "(require ox-publish)&q= uot;.

>= ; Again: How do I as a newbie know?

>= ;

>= ; > That page specifies related global variable, so you can try

>= ; > `describe-variable' C-h v with the related name.

>= ;

>= ; I know that and I did. But this is waste of time when I have to do this

>= ; for each of the variable in that big list.

>= ;

>= ; >> 6.

>= ; >> Is there a way to integrated backlinks into output?

>= ; >

>= ; > Do you mean something specific to org-roam?

>= ;

>= ; I am not sure but maybe yes. ;)

>= ; I can do C-c n l which invokes org-roam-buffer-toogle and shows me an

>= ; extra buffer with a list of all nodes (org-files?) which are linking to

>= ; the current open node.

--nextPart5806142.lOV4Wx5bFT--