From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <emacs-orgmode-bounces+larch=yhetil.org@gnu.org>
Received: from mp2 ([2001:41d0:2:4a6f::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by ms0.migadu.com with LMTPS
	id 6AAmGbk6wGAswgAAgWs5BA
	(envelope-from <emacs-orgmode-bounces+larch=yhetil.org@gnu.org>)
	for <larch@yhetil.org>; Wed, 09 Jun 2021 05:51:21 +0200
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 0LmOFLk6wGAJEQAAB5/wlQ
	(envelope-from <emacs-orgmode-bounces+larch=yhetil.org@gnu.org>)
	for <larch@yhetil.org>; Wed, 09 Jun 2021 03:51:21 +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 96F6A24EC1
	for <larch@yhetil.org>; Wed,  9 Jun 2021 05:51:20 +0200 (CEST)
Received: from localhost ([::1]:54254 helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-orgmode-bounces+larch=yhetil.org@gnu.org>)
	id 1lqpFO-0000RR-F0
	for larch@yhetil.org; Tue, 08 Jun 2021 23:51:18 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10]:56216)
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <sbaugh@catern.com>) id 1lqlCS-0008VF-EV
 for emacs-orgmode@gnu.org; Tue, 08 Jun 2021 19:32:00 -0400
Received: from venus.catern.com ([68.183.49.163]:48876)
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <sbaugh@catern.com>) id 1lqlCP-0001Jf-Db
 for emacs-orgmode@gnu.org; Tue, 08 Jun 2021 19:32:00 -0400
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=98.7.229.235;
 helo=localhost; envelope-from=sbaugh@catern.com; receiver=<UNKNOWN> 
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=catern.com; s=mail;
 t=1623195116; bh=0lCUaPKQReJQsKutIVbWH13g74aKUI4JIhRT6whhn+A=;
 h=From:To:Cc:Subject:In-Reply-To:References:Date;
 b=XLIzmx30wWgZT8Y4qDxBj2Mhuk3SAxP5j2XaNpyeJRT9VdCtFW5O2QP7gHUoEfYp0
 HJbTvjWgzNMiQ+EMb4Xmu+VVZl9hCWMPbvw2OKBPG9/fcZkLWC/XXDkmXy7tXsAwAR
 gU00YuZujx7HDcNF0z1ZqNzbhbdy/EO9WXpX3tLQ=
Received: from localhost (cpe-98-7-229-235.nyc.res.rr.com [98.7.229.235])
 by venus.catern.com (Postfix) with ESMTPSA id 552012EB70D;
 Tue,  8 Jun 2021 23:31:56 +0000 (UTC)
From: Spencer Baugh <sbaugh@catern.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: HTML export uses anchor ids which change on every export
In-Reply-To: <87bl8tz5dr.fsf@nicolasgoaziou.fr>
References: <87wnrhl7z7.fsf@catern.com> <87bl8tz5dr.fsf@nicolasgoaziou.fr>
Date: Tue, 08 Jun 2021 19:31:55 -0400
Message-ID: <87im2okk5w.fsf@catern.com>
MIME-Version: 1.0
Content-Type: text/plain
Received-SPF: pass client-ip=68.183.49.163; envelope-from=sbaugh@catern.com;
 helo=venus.catern.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, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Mailman-Approved-At: Tue, 08 Jun 2021 23:50:55 -0400
X-BeenThere: emacs-orgmode@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Cc: emacs-orgmode@gnu.org
Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org
Sender: "Emacs-orgmode" <emacs-orgmode-bounces+larch=yhetil.org@gnu.org>
X-Migadu-Flow: FLOW_IN
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org;
	s=key1; t=1623210680;
	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:in-reply-to:in-reply-to:
	 references:references:list-id:list-help:list-unsubscribe:
	 list-subscribe:list-post:dkim-signature;
	bh=0lCUaPKQReJQsKutIVbWH13g74aKUI4JIhRT6whhn+A=;
	b=oWYdwTXVJpK89564TNogTOtPbk2YSJLBNNTd5HGT2RWbcDdLwdK0ujd2+LAE1xeMLM3fWK
	2A/Bgz+cY4/MLkGoVvXXK5vEaPIzZaEoKE1wYz1VIX/oNeuGo8x2jr4CmL50P8jl8tX4mM
	UFosYwrdU8KweKEob2Jn7J2+TIQ71hPNTCkKUA1YmKi39/JtiG/hmmOcfMnTwOjL1gsTCc
	kEAugu5oiD+dBmvmmbHDpE9JBHCOVQTvncWXHUSHHtLvN0hCHIlnJ/Kzt9YpQWQoOCoMo1
	S7pjRd7Hci/gnRIu/9RRqMvO7gYj7Ik03Nx/5c7+ZBRO35S81wsviiYSsrvmaQ==
ARC-Seal: i=1; s=key1; d=yhetil.org; t=1623210680; a=rsa-sha256; cv=none;
	b=NcJTznsxCvEZmP10q+H3t1VgNLgYB4B6RzoNfWx2cfOYCfPz0WrI2iJpbH3O2c7J8DRsPp
	tigq431T39hxZryv8x2b/qk/bdJu7sn4jegPtqBtC/O8uuzr0MZ9VtZsvJJHiQeS6qNKI2
	O75JjOkeG5AWpiadmWxHGSYR94VdaGU5m5tIOSMphekEa29c0xH9dHcr3t7VvXaX0w4eIo
	lUfiwMQH+kz+jISVUVJxu5VmbsfvYR9FMR4BtoUc4u2mlsnWw3bJY4puR2Yy6pEQNQpEdC
	G8fMpJFgskqTZYDv1moipDJA0rF/fNFPn0OQNYYhE1b+Q83AsLw+nTRzguwktg==
ARC-Authentication-Results: i=1;
	aspmx1.migadu.com;
	dkim=pass header.d=catern.com header.s=mail header.b=XLIzmx30;
	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-Spam-Score: -3.12
Authentication-Results: aspmx1.migadu.com;
	dkim=pass header.d=catern.com header.s=mail header.b=XLIzmx30;
	dmarc=pass (policy=none) header.from=catern.com;
	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: 96F6A24EC1
X-Spam-Score: -3.12
X-Migadu-Scanner: scn0.migadu.com
X-TUID: qIj9SannONMI

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> No, for public links, CUSTOM_ID is the only sane way to handle this.
> Even "sec-2" could betray you if you slightly modify the document.

I understand and agree. However, "sec-2" is strictly better than the
current situation in terms of link stability: There are many document
modifications that don't change "sec-2", and there are no document
modifications that don't change the current id format.

If some user likes link stability a litle bit, but not enough to add
CUSTOM_ID to every single heading, then providing some option to
generate ids like "sec-2", which are stable in some situations for very
little cost, is good for that user.