From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id iLLDJJqpp2T8LQEASxT56A (envelope-from ) for ; Fri, 07 Jul 2023 07:58:50 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id mK/KJJqpp2SPZgEA9RJhRA (envelope-from ) for ; Fri, 07 Jul 2023 07:58:50 +0200 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 707924E49E for ; Fri, 7 Jul 2023 07:58:49 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=qPm8h5jd; 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=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1688709530; 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: 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=1ZgAYLHzxvk8T5xPFaFE6aM9bSzjPZ/T+lR5SVN4Wg8=; b=HUxx91kiLUqLPgqa+YWqTWV7InM5nha/MdLhicJJIqwN7dMcW5qQbGMFXlhPkFkUF+gEXZ dNWYLSAXw5TbSfESh4b4WcaGtIBCq+LR0B3je1v6dLRBMigumUMUaCi5tBnVyYwajFmtPa RKlU5Jc6XH8k5YCFmycrJ59IbSCkFnlMluu2U64+ZrB21y+CY2JQUyoGiJ1bXqcXd2yzw4 NJBKD9kx8lmiJhZoQJlTG10zpXbVRhKdg2zuhOt3enMF4eO82u7Ulovi52O/+Z7DWqzoqR UwVhLoQxhp5Vx2Hj5uOjEkBvoI76ll8yINRAxztCBl4Qve2esQNWzZ60khJqag== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1688709530; a=rsa-sha256; cv=none; b=ClQeYKC3wIn6f9Sylyn4Yoln7sc7opwiYl50Auc7xR6Buwdy0XxYGol9fPDVotBrnvVe9Z hE/Hj5defgO5dmu1MgFJCtpb94CjJdApbsKsxzfjhUsPq0dTcIXlzciPMtNO0Q/kkMlEss YyZJdqZfK0G2Ur+l5/cucayruDRQ/VVJbqa1H5GWHBtkM/Blp3C0SNwD5xo9KoJrAnFFsr 7V0U8gwS0DdyMCRV37dX6faJXYtcSVrgv78kc3jP+128NWqyOepUSjmowaMVm3Mz6qD6GD DzLUlrfm1eSkKu4K3oJH0n9YxSOnITDJpJ6S4xVOsLFECHXILYMPqQ6laywZOA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=qPm8h5jd; 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=posteo.net Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qHeTa-0002xC-7j; Fri, 07 Jul 2023 01:57:54 -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 1qHeTY-0002wx-FW for emacs-orgmode@gnu.org; Fri, 07 Jul 2023 01:57:52 -0400 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qHeTW-0008Df-Eh for emacs-orgmode@gnu.org; Fri, 07 Jul 2023 01:57:52 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 79767240104 for ; Fri, 7 Jul 2023 07:57:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1688709467; bh=BCSWUhFBFllkGET9Kir9e3l3O+Vi/4FpH05za5/xM20=; h=MIME-Version:Content-Transfer-Encoding:Date:From:To:Cc:Subject: Message-ID:From; b=qPm8h5jdMOqwoKh/7JBpHI9U23PJRnoEA5pBBuevdxSgPu+vCk+ubo+UAbhiewq5p jutdmbXW79im8a8g2HhRUWKjF2ksYIO76GD0oTGQh36RqBaw+y+BHfu6iL5CuJwxCj 77iiQO2wF8enWzSxQMSI7G6EXBHyXhL3S/X2V6VH8LrOdgj5+RfdvC5Lpost4s7F94 OoG7ZdkI9DbHb1gC+qFIW3/EBN4a0R0emUJiReCwMlF2tsa8fWD2pg9VKNEzllrVLq HmhW+9lqy0+FBBBN89TRbcsI3sIGSWe4CqA2HZ8Y0VdO/baW1O+YGE1tzAKI/gDhQB 0Nl258TZ+m3AQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Qy2k26ncQz6tyQ; Fri, 7 Jul 2023 07:57:46 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 07 Jul 2023 05:57:46 +0000 From: gerard.vermeulen@posteo.net To: Dan Drake Cc: emacs-orgmode@gnu.org, emacs-orgmode-bounces+gerard.vermeulen=posteo.net@gnu.org Subject: Re: inconsistency links and code line labels In-Reply-To: References: Message-ID: Received-SPF: pass client-ip=185.67.36.66; envelope-from=gerard.vermeulen@posteo.net; helo=mout02.posteo.de 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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-Migadu-Spam-Score: -8.24 X-Spam-Score: -8.24 X-Migadu-Queue-Id: 707924E49E X-Migadu-Scanner: mx2.migadu.com X-TUID: B2bFeq5zI0gd On 06.07.2023 14:49, Dan Drake wrote: > > There's a bug [[(my-code-line-label)][right here]]. > > This seems inconsistent. Why do I have to omit the ref: bit? This > always confuses me; it seems like it would be simpler to just make the > label and the links to that line of code be exactly the same. I don't > see any particular reference to this in the org manual > (https://orgmode.org/manual/Internal-Links.html [2]). Any insights? > > My idea would be to get rid of the special behavior for code line > labels and just make this work with dedicated targets: in regular > parts of my org file, I use <> and can make links to > that. It would be simple and consistent to make that also work the > same when <> is inside a code block. > Such link targets would conflict with <> references See: https://orgmode.org/manual/Noweb-Reference-Syntax.html Therefore something like the behavior described in https://orgmode.org/manual/Literal-Examples.html must have been invented (look at the description of the -n, -r, and -l switches). Regards -- Gerard