From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.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 AJ6oLP6R9WTNYAEAG6o9tA:P1 (envelope-from ) for ; Mon, 04 Sep 2023 10:14:54 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id AJ6oLP6R9WTNYAEAG6o9tA (envelope-from ) for ; Mon, 04 Sep 2023 10:14:54 +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 8152C45676 for ; Mon, 4 Sep 2023 10:14:54 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="Kcdm/a20"; 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=1693815294; 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=Z0PN3OIejXA2cv4XrAUSDWJ83ciWrah5csGD+3fmnCM=; b=IcCCidqitr7dvGfAORf3lMQhPO95sX4Q2PAQmB6bGzblnAGg9P0BDZx4OxJbf2scB5I8ZL 5Y/MQ+eHgBjldflOFiQ5Jy7dJ+YuIgz9WmXQBFlqrK3fk4rVaHtm9hYVAEfihnWLSt+Ue4 5PAW0k5FIznAyaKF79N3dSHL7LDXVucVKdRjiHJTybUxCmrzOvo9LJAhzhNI9KsNC2kN3l chs1c6TjmoXGY1cCkgye7OgjeP9ldz5S2fLxDUTSkcVMiFOg3/mdpwenka9sa7PBYewbLg neKNPlr5VB1VPndfSx1XEraW4Cp0tT+9E0xnMIelgg551fcZbyZPLoKa8CME8w== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1693815294; a=rsa-sha256; cv=none; b=KSE8cn+bkLeP+qDf3Kgl+oragOQmYK9HsvAqJzfCcHWZlEYHe1sogtJ0Sabw/LzPyL6/UF 4a2BGXyQFvVk+/djLM5mVN3+w9xwoBsTeuXk6V5jDj7nRvSi35HWaf05lUTUijuzWGvKbJ gYf37byVRrk6w8qNddgrGC80Egnkx6GKyAA8yX9zeiZadKbear95ScTaxlNThBwMcClgI9 Mtn8NsJn4WSSe7XWmPb0WRZVN8bGnuWtQwrIzWX24N0ZahSRsHQNcaZDvECm9Qa5bmQFO5 WkRLn3ygkPMrtHd5GGAapL1gCdoLP+P82g2UMaVYu4hIAyTLy6pB9dTvvNNxBg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="Kcdm/a20"; 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 1qd4ir-0004cM-IB; Mon, 04 Sep 2023 04:14:14 -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 1qd4ij-0004aM-6y for emacs-orgmode@gnu.org; Mon, 04 Sep 2023 04:14:06 -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 1qd4ie-0007zc-CF for emacs-orgmode@gnu.org; Mon, 04 Sep 2023 04:14:04 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id E2F5F240101 for ; Mon, 4 Sep 2023 10:13:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1693815237; bh=a9g7bbGgmhKFUguDDEXx2HzLR82JP4evCA6dL+lGOFw=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version: Content-Transfer-Encoding:From; b=Kcdm/a20qhhXL64yhFVAy8YpG3qgilMivSOrdxMdGhIOIT6cJlptnhJtEiYiSwVy4 FtBMnga11nvteA4Kqk8fPfnO7vgOQn2zVspsbdyVAdLf8NGvP2YE2h9+yHpOyq5PJq s/rNNYLAhaZSCNilzAkcv9m04hUC/Q3srOirwivovozD/9EPuCIc0fGi72StvPE+X5 d9G33q1e6GQPA5qDR9VCZpn6Esbtm/oGapSQ71r5781csyy9oxE+Zvxl5ocyGvusi6 aNf9hr7x37p1pPEL5oXtyuW4+epCwvtPYHYBq6dB52SkXiUmEhqdOcKWRTQbbnQ14G z6ZLM8Iv6bIKw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4RfLxx3gr2z6twT; Mon, 4 Sep 2023 10:13:57 +0200 (CEST) From: Ihor Radchenko To: alain.cochard@unistra.fr Cc: emacs-orgmode@gnu.org Subject: Re: Completion mechanism for headlines when creating a link between 2 Org files? In-Reply-To: <25845.34743.825131.486943@gargle.gargle.HOWL> References: <25845.34743.825131.486943@gargle.gargle.HOWL> Date: Mon, 04 Sep 2023 08:14:44 +0000 Message-ID: <87h6oawe17.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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_H5=0.001, RCVD_IN_MSPIKE_WL=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-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx2.migadu.com X-Spam-Score: -8.34 X-Migadu-Queue-Id: 8152C45676 X-Migadu-Spam-Score: -8.34 X-TUID: YIiwBx4tJxS6 Alain.Cochard@unistra.fr writes: > C-c C-l (org-insert-link) > > [...] > > Completion support > > Completion with TAB helps you to insert valid link prefixes > like =E2=80=98http=E2=80=99 or =E2=80=98ftp=E2=80=99, including the p= refixes defined > through link abbreviations (see Link Abbreviations). If you > press RET after inserting only the prefix, Org offers > specific completion support for some link types. > > but, after I complete for a given file, I cannot find a way to further > complete for a specific (sub)headline. Is there a way that I missed, > even after searching the Internet a bit? You would need to extend the default file: link completion function - `org-link-complete-file'. You can override it with any custom function: (org-link-set-parameters "file" :complete #'your-custom-completion-function) > If not, I am making it a feature request. Indeed it would be great, > especially if one does not really remember where, in a (known) file, > the headline is, nor --even more importantly-- what its name exactly > is. > > (In my naive view, as the completion mechanism already exists for > internal files, it should be easy to extend it for external files...) It is, although even more common request is simply inserting a link to a heading in _a_ file (not known). --=20 Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at