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 KE0aOYusC2c3BAEAqHPOHw:P1 (envelope-from ) for ; Sun, 13 Oct 2024 11:18:36 +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 KE0aOYusC2c3BAEAqHPOHw (envelope-from ) for ; Sun, 13 Oct 2024 13:18:36 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=Jd3sZyRN; dmarc=pass (policy=none) header.from=posteo.net; 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" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1728818315; a=rsa-sha256; cv=none; b=lYRmbHZOBZkKdxl/Ngs6Y1HcqWOrQJMDRtFqoXOK+OyAETmaCL/J2NBRPMpalXNSiA7vPu nf91Qsfw31W+mbFybvz2+kmEHGIL4pzFPJR8cfCcxViJrHgpBfKdFUWNl8MD+FOBmjR0te ItkU/sDfwU30n0bjMaJalu9A3iRTNiucbe0r9dKhGERfh8LUkuO5MbghPrZZKJ71Cnbhw6 zrDuY/A8hTzZQyWUI1IndYVo5Tn1UNwiL6bwk9gp/LLwYJsF8NzUDLz4taPN/VT77UgcIH dY0+IvoHW7B9D6gwetmwd/sgkQrVg69ZYtAh7fRr6CKWvgfdgOIQe7GO4inD9A== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=Jd3sZyRN; dmarc=pass (policy=none) header.from=posteo.net; 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" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1728818315; 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=wvJ2hfoSzC5dNOq9gpr2gn0Zu9WcbkGsmMUj+hlXTBo=; b=cs51iyvS6KT2awIOMbjzx64eFOySt6BqIarVyUTPPGPvUndSmyWfuQMB5f4slB7WGcowMG hQ1DQSB9Ih3Gq7lr554jlpVX3K6+XZXlyPYArMqVABn02cxYkkc96vT49Pb9pUw7fcEIo0 0+QVSGHXMRDf3Y6UPQcNvxWUywsmAOQUehkMQYQpH/yH2pGvrlc9rLAnq0CoE9CqlosS8D 5gtRE11+YIMKN5tg92AkkvfHWrhb0TPYixIGysT4MWKAbo7YoWAFfmDDg6Jceti9XONy23 d3mKFK6GTIOICGqsflRStRtfIZtKtO4ogCKWTmmF49t8nhJvMq27QqQwMAdIww== 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 7BE94436B for ; Sun, 13 Oct 2024 13:18:35 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1szwbm-0005yo-R2; Sun, 13 Oct 2024 07:17:58 -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 1szwbj-0005yE-Uw for emacs-orgmode@gnu.org; Sun, 13 Oct 2024 07:17:56 -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 1szwbh-00057t-5U for emacs-orgmode@gnu.org; Sun, 13 Oct 2024 07:17:55 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id A3AA7240101 for ; Sun, 13 Oct 2024 13:17:50 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1728818270; bh=xhWSLLaK0VOOKhZSWOauGogo8VE8dtjONvtvnzDJIH0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=Jd3sZyRNq/buWaPoAzulRUki+xefxZfJq6//mMePRNLykGf5GlIYe+QyfKqz7SjyA yU86Tqfmkv/96RorNvx6CUuzPtj5i6wtyRoTCnF/VHFzeAPX5P5JSpWurdomqD7w6a ZGLp2SC5Uw4sTj4/1RUWcw8YEJ7UpesdCwBF+AWciVoAZ6jEBbNZVFU6cn6OeTT+l8 La/6esKLrBc2pl23pwRvg9SVXGzm9ZxD7MprMP75UYfdyy3j5GAPfiv1qCzVhpjlcU Roqk8HF6coXAqXPKW2hfoUDVuXIis6qARu9Kt4jEaUtf21/mLhc8XXmA5pwJordO6N IsjSTaOOLSvNg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4XRHs93J8Vz6tvZ; Sun, 13 Oct 2024 13:17:49 +0200 (CEST) From: Ihor Radchenko To: a4ofubmq@anonaddy.com Cc: emacs-orgmode@gnu.org Subject: [FR] Allow searching by outline path in file: links to Org files [file: References: Date: Sun, 13 Oct 2024 11:19:39 +0000 Message-ID: <87v7xwz1v8.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, 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-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -1.26 X-Spam-Score: -1.26 X-Migadu-Queue-Id: 7BE94436B X-Migadu-Scanner: mx12.migadu.com X-TUID: ihjN3ArrQPUb a4ofubmq@anonaddy.com writes: > there is ambiguity right now if you want to org-store-link to heading 2 >> subheading 1. By default org stores > [[file:::*subheading1]], which would incorrectly point to > heading 1. > > Instead it could be [[file:::*heading 2**subheading1]] > > Please let me know what you think, if this has been already suggested. > I know that you could create unique UUID in PROPERTIES, but wouldn't it > be more informative if org-store-link used parent headings instead? I > think it would be more elegant and not dissimilar from other popular > addressing schemes (e.g. file paths or urls). I think that such feature does make sense. In a way, we already use something similar in org-refile - search by outline path. I am not sure if I like the format you proposed though. Maybe we can instead try to implement nested search options. Something like [file:::*heading 2::*subheading1] You may refer to the existing code in `org-id-open' that allows to narrow down link search to an existing subtree. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at