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 GJ98DeGT+GRQcgEAG6o9tA:P1 (envelope-from ) for ; Wed, 06 Sep 2023 16:59:45 +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 GJ98DeGT+GRQcgEAG6o9tA (envelope-from ) for ; Wed, 06 Sep 2023 16:59:45 +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 C9E215F143 for ; Wed, 6 Sep 2023 16:59:44 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=none; 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=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=gmail.com (policy=none) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1694012385; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to: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; bh=aH2/y45XcbppQFLAvu8RGpQd3m3sUJynabFc4BJtcKY=; b=CYKbW3sakSn8VC323H34RvZNM/vrnKruPi49+OozYmJrfUyow7ZiACy/TrYqmA8lkjiwec +Dv4N2Ve2f0EbWry87z0flRi70gQcLfiVLo0FaBEcO7GExR8I8Q45aoyrqnVzfz5cTTYar BpRyGRuAow0kZr6ogSow/iwjpL0CW4sxbk82qQEZTJoCczLUvAyO3+Qg99pV/a9+E07/Ht JNR6RmViOJs1g21r7Ue5aRG/EXPs4qf1FNANvI59RmXSK2eKZBvfhBHFQBDYN0a+SbUgSK Yr0DdKcwhmEm5RCkidsdMV1kgGcj1IkSEF+/O30E16WpS5cIeltHa6pRaqWZhQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1694012385; a=rsa-sha256; cv=none; b=sP5BYuno2YKBvRmVHfO758dR0Zdc0vU5NNkLTytuntFoqT0W/BA8wQo0i1CYs3Yvn5iBCS K/IXy44jOHJnlGHfWzxJvdiwfB7rQJ3DpZsV18WdgL2o6QP1DB3b3pgYOC+6YNRpevpMEq G2pkaHfYF/xi3+4q3o/cXDgkNIxJhHWyukUzWVXww1UpSagJ/EVS0vUEh36hqP7Z9+D10M Ivw9Se+zLW68p61LGjEfKZ8FGggAfL/X7Atbf5nXxA/GhbOlZ/U7ReeKWVjfe9/f/f0+YH N7TXATtLuwP7LGm99L+aIJE7XfD0036cZeABra0POGN5Y4sodZmeXrn3cFwCLA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; 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=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=gmail.com (policy=none) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qdtVU-0007kl-9Y; Wed, 06 Sep 2023 10:27:48 -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 1qdtVR-0007kL-Qt for emacs-orgmode@gnu.org; Wed, 06 Sep 2023 10:27:45 -0400 Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qdtVO-000497-3R for emacs-orgmode@gnu.org; Wed, 06 Sep 2023 10:27:45 -0400 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qdtVJ-000AGK-Fi for emacs-orgmode@gnu.org; Wed, 06 Sep 2023 16:27:37 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: emacs-orgmode@gnu.org From: Max Nikulin Subject: Re: [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3mpjk70si-emacs-org-9.6.7/share/emacs/site-lisp/org-9.6.7/)]) Date: Wed, 6 Sep 2023 21:27:25 +0700 Message-ID: References: <87il8v2q00.fsf@riseup.net> <89434f4f-8aea-23f2-bbfc-3961c18f2154@gmail.com> <87a5u6tgb3.fsf@localhost> <87fs3ydv17.fsf@web.de> <871qfirwbx.fsf@localhost> <875y4udqim.fsf@web.de> <871qfhhw7h.fsf@localhost> <87fs3svq5f.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.0 Content-Language: en-US, ru-RU In-Reply-To: <87fs3svq5f.fsf@localhost> Received-SPF: pass client-ip=116.202.254.214; envelope-from=geo-emacs-orgmode@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: 13 X-Spam_score: 1.3 X-Spam_bar: + X-Spam_report: (1.3 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-1.473, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no 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: -1.52 X-Migadu-Queue-Id: C9E215F143 X-Migadu-Spam-Score: -1.52 X-TUID: Y5d029Rr0JyM On 05/09/2023 18:02, Ihor Radchenko wrote: > > What I had in mind is a bit elaborate: > 1. We get actual link type > 2. If link type is not registered, we try "fuzzy" > 3. If "fuzzy" target is not found, instead of broken link, we export a > link with unknown type. It makes sense as an additional variant for `org-export-with-broken-links'. Currently no option allows to export description of broken links and sometimes it is inconvenient. > Max Nikulin writes: >> I am unsure if any "PREFIX:" should be recognized as a link type, but >> there is another possibility on this way: allow users to mark some >> prefixes as search links, not link types. > > May you elaborate? I am considering another behavior. If any PREFIX: is recognized then the link exported literally as PREFIX:PATH unless the PREFIX is registered as (org-link-register-search-link-prefix "sec") So if the document does not contain PREFIX:NAME target then it is an export error (or another prescription controlled by `org-export-with-broken-links') and it may be reported so by `org-lint'. Different users expect different degree of strictness during link export. I am unsure which variant is better.