From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id kLc+JNtT118ybwAA0tVLHw (envelope-from ) for ; Mon, 14 Dec 2020 12:00:27 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id HeECINtT11+PXwAAB5/wlQ (envelope-from ) for ; Mon, 14 Dec 2020 12:00:27 +0000 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 4AEE19402C8 for ; Mon, 14 Dec 2020 12:00:27 +0000 (UTC) Received: from localhost ([::1]:51346 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kolPu-00071g-L0 for larch@yhetil.org; Mon, 14 Dec 2020 05:49:22 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:47096) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kolNH-0003vH-PX for emacs-orgmode@gnu.org; Mon, 14 Dec 2020 05:46:41 -0500 Received: from msg-2.mailo.com ([213.182.54.12]:34098) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kolND-0004Gk-Ch for emacs-orgmode@gnu.org; Mon, 14 Dec 2020 05:46:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=netc.fr; s=mailo; t=1607942787; bh=D3PNx9GJMS5Bko9Ma4HKWP9ShUfDcIox3pmWWNlG2rw=; h=X-EA-Auth:From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=DUj3s9qp67XuGjdSj0oxmQOyca/cqVpxrPSv2qpHF7hYU14Z249BQOdjbyFxpwg8h N8OeKY0sjbApxbNck4GJRZQZVh/6xJarwwL72luZNG/9ZtveFr0ohZ8u5JlaDV64VU Fz+Oa519sjMLmgV+lKJ9C+VksMivyAd3J1hiYqIY= Received: by b-3.in.mailobj.net [192.168.90.13] with ESMTP via ip-206.mailobj.net [213.182.55.206] Mon, 14 Dec 2020 11:46:27 +0100 (CET) X-EA-Auth: YRTWUnbxfTl2WL7CXi0KMOiraatwr6X7ZzOlAhrXjzOuFJfxa0T6OsMckecfrDVxqRuUNpF485k91Sq91oyMTSrOIPZUxC0RYoX4yrye6l4= From: Dominique Dumont To: emacs-orgmode@gnu.org Subject: Re: stability of toc links Date: Mon, 14 Dec 2020 11:46:27 +0100 Message-ID: <3089351.44csPzL39Z@ylum> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Received-SPF: pass client-ip=213.182.54.12; envelope-from=dominique.dumont@netc.fr; helo=msg-2.mailo.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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.23 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-Spam-Score: -0.21 Authentication-Results: aspmx1.migadu.com; dkim=fail (headers rsa verify failed) header.d=netc.fr header.s=mailo header.b=DUj3s9qp; dmarc=fail reason="SPF not aligned (relaxed)" header.from=netc.fr (policy=none); spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 4AEE19402C8 X-Spam-Score: -0.21 X-Migadu-Scanner: scn0.migadu.com X-TUID: TlJ8EcBfBvjF On Wednesday, 9 December 2020 00:28:46 CET Samuel Wales wrote: > when you link to a section using toc, you get a link like > > https://thekafkapandemic.blogspot.com/2020/02/crimes-against-humanity_3.htm > l#org080f0ab > > will these links break if somebody copies them and pastes them > elsewhere? what if you add a section? I have a similar problem. I write documentation for a customer in org format. I also have to generate Markdown files that are archived in a git repo (Unlike Github, Azure DevOps doesn't support org files). Currently, TOC and headers lines change every time the markdown files are regenerated, which makes git diff much bigger, which also impacts code reviews. So stabilizing the generated toc would be much welcome All the best