From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id KAYvNItHmmeCLgAAqHPOHw:P1 (envelope-from ) for ; Wed, 29 Jan 2025 15:21:48 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id KAYvNItHmmeCLgAAqHPOHw (envelope-from ) for ; Wed, 29 Jan 2025 16:21:47 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=mailbox.org header.s=mail20150812 header.b=NKqxwGqh; 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=reject) header.from=mailbox.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1738164107; 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:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=H+TebYZ0qD8VV3+7iUenFWWt+oB1qhy6JbtJx1sQTb8=; b=dXeU8gL+6Mztv/ZpW/tR7jSpkuWwywTuhLtx2Gzbzjr6AeVXR1lZyL33Z1Z1NdVmSmu4UP FgOpyqcbM+rgCD56UOI5pImurWAB0NnYCPsubDauXd17oKZef/sA3BFr07D/GNXVbEiA5t FgvYgyE6mTOsxLumVj4n226N09UVhf1+Ly678iRk+YNTqxWe4D7Ae3QhxPk+MaQj2iQKGf G2GhIpuR2oOzQuSaeaEirMhBoQmzLIx1oPsH/SReNm9eylo0y72yiehSMxHVO1lm0KpMgK WFU42hLnM1F5sTeddMTyk2EsZTjgPNN7WbVe0EJGST64OrRtB9n++8JVjZYlpw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=mailbox.org header.s=mail20150812 header.b=NKqxwGqh; 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=reject) header.from=mailbox.org ARC-Seal: i=1; s=key1; d=yhetil.org; t=1738164107; a=rsa-sha256; cv=none; b=M7KtsUsX49V3A/K/HbHY9EBRBu3mEwjQbfQqFajW1FE/uKjZEncSc4jYC03BWDvdUBxic/ M90lA835+DIJ/hjWZ/3vknDq3qVlRylwl3J8jj+7wWdaix5tIJnAsoSdMppP83z2C5bc9c Nm6L6ZtzJ/W2WnQK+6w8SAJW4IKUY/ZkndSuvQPxigxm81o7kqQN0wdzRGkoWLpvIv7Kfp Y4gAr7vxE7dFrP2Yd6z7XOElMesxVuoQUMr+qLjhqgn2jbR3pKteJGNJDkeBmcAr+vnTOv bzZLr37Rb4HmA6JB1RzctXwDsdIKhZaXnqxYyqw+M9TpXT/P8H8a7olFYb1uRg== 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 859D5303AA for ; Wed, 29 Jan 2025 16:21:47 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1td9sM-0002hB-NE; Wed, 29 Jan 2025 10:21:10 -0500 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 1td9sE-0002ft-4H for emacs-orgmode@gnu.org; Wed, 29 Jan 2025 10:21:03 -0500 Received: from mout-p-202.mailbox.org ([2001:67c:2050:0:465::202]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_CHACHA20_POLY1305:256) (Exim 4.90_1) (envelope-from ) id 1td9sB-0006EJ-4j for emacs-orgmode@gnu.org; Wed, 29 Jan 2025 10:21:01 -0500 Received: from smtp1.mailbox.org (smtp1.mailbox.org [10.196.197.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-202.mailbox.org (Postfix) with ESMTPS id 4Yjm7X48Z4z9t5p for ; Wed, 29 Jan 2025 16:20:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1738164040; h=from:from: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; bh=H+TebYZ0qD8VV3+7iUenFWWt+oB1qhy6JbtJx1sQTb8=; b=NKqxwGqhVZB0Yv2Zp2uzxsPdmP+SAMISnu+QyUrAg2c6yy+7t94E4b1X0URbuko4DjuHXD ARY6Gy0eYZ2zydE8h5OVCMkOhEhPqpZcRlh0HmvAVh73bBk4OyCjUzPKRPcq0pDr+YV5Uo veQ26nb1IHWkQ7kZewkZhLAzzr46Ond9M2L2b4FMxe7OmW5RQ2nL3Gyr2TuhhTEIoFdxB0 mV7IlmB9u6SFmOUTezT6giDiaeZlaDYqgcsRSlMDRxevnSjvRfLuSkSIBb5TDK/Fu060DM X8/T+YoIBBUcLE3gaXOF3iAmNSRJNGtLWAvqlZQJLtyn5IW52vMnVLoXzJkAjg== Message-ID: <570c92e1-00a1-40d5-94ea-7b6518c6c9e1@mailbox.org> Date: Wed, 29 Jan 2025 16:20:38 +0100 MIME-Version: 1.0 From: juh Content-Language: de-DE To: org-mode-email Subject: Automatic indexing for objects like in Sphinx Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-MBO-RS-ID: c34d9795a7d1c487b1b X-MBO-RS-META: pz67e6mk55wk4jt6539sipx3e6rtzhnn Received-SPF: pass client-ip=2001:67c:2050:0:465::202; envelope-from=juh+org-mode@mailbox.org; helo=mout-p-202.mailbox.org X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 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-Migadu-Scanner: mx12.migadu.com X-Migadu-Spam-Score: -5.53 X-Spam-Score: -5.53 X-Migadu-Queue-Id: 859D5303AA X-TUID: kznWkosHHUUo Dear all, I do some software documentation using Sphinx (https://www.sphinx-doc.org/). When compiling pdfs Sphinx + LaTeX generates a huge index using a semi automatic mechanism. You can eg. do this: ----- This is my normal text. Now comes the description of a Python module. .. py:module:: foo Description of module foo This is normal text. In the next sentence I want to reference the foo description. Learn more about :py:mod:`foo`. ------ It is quite simple. You mark something as a specific object and can reference it elsewhere. Additionally Sphinx builds an index with links to all modules. And the syntax is extensible, and you could define something like .. mode:: org-mode Description of org-mode. Late I can reference the description with :mode:`org-mode`. And it will show up in my index. I wonder how I could achieve this in org-mode. The foo description in Sphinx is not a headline but an anchor-reference thing. How could I achieve this in org-mode in a way that it gets exported correctly to be of use in Latex or HTML? Can I make "foo" a subtree with a special tag that triggers the anchorization, referencing and indexing? I know that there are tags and an index mechanism, but I miss the way how to chain it all together. TIA juh