From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:700:3204::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id uIWAChENlGV4OgEAkFu2QA (envelope-from ) for ; Tue, 02 Jan 2024 14:18:09 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id COQpAxENlGX4UQEAe85BDQ (envelope-from ) for ; Tue, 02 Jan 2024 14:18:09 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; none 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 EE2F13FEBB for ; Tue, 2 Jan 2024 14:18:08 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rKedt-0007S1-6q; Tue, 02 Jan 2024 08:17:13 -0500 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 1rKedo-0007Rd-Je for emacs-orgmode@gnu.org; Tue, 02 Jan 2024 08:17:08 -0500 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 1rKedm-0006xs-H5 for emacs-orgmode@gnu.org; Tue, 02 Jan 2024 08:17:08 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 49130240104 for ; Tue, 2 Jan 2024 14:17:03 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1704201423; bh=2mQaid2I29FVKIQM+B+9XmmHaC180Hz58ExlU6dk0QE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=Z9XtMXok55Yt4NzlzkWTWqjn36tvxRKXp4Q6Ex06Nsfzt0z/OXYlXUY9/FnO9CPcP L1RM039BEziEwSqKdvMaHUL88m7ahSRJVIhVIQk+fT1AOgxcr2fhHWEcPQ++mU4uC4 FQg4CFIvXaNZC8e6r4VmJVlJ/v2CthWsdmQ85/db05dPCFx0gU/Zo4WC6xmytnEL5a kiyV5C90dSb8oz8HLWqYWj6Yv7AqpUGrt/mB0wrWKB2NzydYQADQDM6gmRWCZKK0gI zi1cwudlj3DjUnPag2PqYksHGI0rqKI9WHjTqwmKPw2S7KhI6LmRCEpMxnHHNOHDmW faU2auZqn/wiA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4T4D0G1hrpz6tw1; Tue, 2 Jan 2024 14:17:01 +0100 (CET) From: Ihor Radchenko To: Joseph Turner Cc: emacs-orgmode@gnu.org, Adam Porter Subject: Re: Should org-link-parser add type "file" when link has no "file:" prefix? In-Reply-To: <87wmss1r51.fsf@ushin.org> References: <87o7e9ei3p.fsf@ushin.org> <87wmsx3vyc.fsf@localhost> <87a5pro14q.fsf@ushin.org> <87le9a76mk.fsf@localhost> <87wmss1r51.fsf@ushin.org> Date: Tue, 02 Jan 2024 13:20:13 +0000 Message-ID: <87ttnvan3m.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_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-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -4.00 X-Spam-Score: -4.00 X-Migadu-Queue-Id: EE2F13FEBB X-Migadu-Scanner: mx11.migadu.com X-TUID: q24Xx4YpWlcW Joseph Turner writes: >> See `org-open-file' IN-EMACS argument - we may use different handlers >> to open file links. Currently, IN-EMACS can be 'system or 'emacs. But >> nothing stops us from adding more options. > > Thanks! Are you suggesting something like [[file+hyper:/README.org]] ? Yes. >> This will cause major issues when trying to export such links. >> Except for HTML export that utilizes `org-html-link-use-abs-url', but >> only for relative links. > > Yes, there are many users who rely on [[file:/index.html]] exporting to > instead of . This is not what Org HTML export does. Only relative links are affected by `org-html-link-use-abs-url': Documentation Should we prepend relative links with HTML_LINK_HOME? Absolute links always remain absolute. >> Why not make [[hyper:/README.org]] use the "default" hyperdrive the >> Org file belongs to. > > I'd like for users to be able to take an existing directory of Org mode > documents and copy them all into a hyperdrive. I think the least > surprising behavior is for the links between those files to continue > working. Perhaps the best option is for hyperdrive.el to make all "file" > type links, explicit or not, point to other files inside the hyperdrive? > > In that case, there would be no way for Org mode files in a hyperdrive > to point to the local filesystem. Similarly, when Org documents are > exported to HTML, there's no way to export . May you please elaborate? How is hyperdrive directory different from local directory? >> For example, see WIP patch where we expose setting id: link properties: >> https://list.orgmode.org/orgmode/c98a38b0-6dea-4b5c-b00f-a39ea922537f@app.fastmail.com/ > > How would the :follow function for "file:" links get access to the link > search option? IIUC, `org-link-open' handles "file:" links specially because > they require > > (org-element-property :search-option link) :follow functions are passed both path and search option. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at