From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id cEPOFNRT1l6xGAAA0tVLHw (envelope-from ) for ; Tue, 02 Jun 2020 13:27:48 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id YMu0ENRT1l6eQQAAB5/wlQ (envelope-from ) for ; Tue, 02 Jun 2020 13:27:48 +0000 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 D6A93940607 for ; Tue, 2 Jun 2020 13:27:47 +0000 (UTC) Received: from localhost ([::1]:39804 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jg6xG-00049t-Hi for larch@yhetil.org; Tue, 02 Jun 2020 09:27:46 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:57252) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jg6wv-00049f-8M for emacs-orgmode@gnu.org; Tue, 02 Jun 2020 09:27:25 -0400 Received: from mail-wr1-x432.google.com ([2a00:1450:4864:20::432]:40790) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jg6wa-0003fX-9V; Tue, 02 Jun 2020 09:27:24 -0400 Received: by mail-wr1-x432.google.com with SMTP id h5so3413313wrc.7; Tue, 02 Jun 2020 06:27:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=F2KiI3OSBYHNH9RlOX+crW3LfoGf+VRG1VANfvxTrw4=; b=s4NFOckAnXoca5OG+QIrYvI0PJfV2ypmdvvzKcQU9QYY8093S+Dy7rzfVN6qTdR2+r L5P1ha3IsuTezWXLNwoK//mhJ1mKt5CCxj1notDBQFD6zW8VZgugf09GwyTIsSXTaDoY s0IY2BNB3Dk9yXwshfEGCjC3VajRavFpRtxLcKstiAbpU/mbnGy8ShGVBpfMzNtusjI5 pT0PaAOJiK3rRM0CBOkX4Oso/bc7wAsicgKXtdn2VlYrJ1t3OwQCEd64Uy8Nzk97cuGV JX3SdTYz/UytLSI07PpXYW4Hyj+YEm9OVZdfOEbpDl5aqlEN2RQzjSQxkEEaOafxSm8k kH4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=F2KiI3OSBYHNH9RlOX+crW3LfoGf+VRG1VANfvxTrw4=; b=hEokUARPH+MNuMYhVFE04ydLJW/F9he3srbeMAo85ddLT8VV071GIn8m5ytUv/bqYn J/cH7+kqqFmnSjY5DUOZNvM248FoubcVUCFrhU8MDiopaIGOptDky1WUpruXuulU9FdK Nu/CYFhNCxtkOt6kdzuuqtPhhxFt3mbCR0RYztid6AQkCZhHfnPl4vabAY+kqaH6VxG9 s0g3nwVRl8Qkhbi/+7GVDJzwFzMzqFyF8nSX/kC7EqxegOqle/FbYLqOOzZwUb84DWmt ET5ubFFDek/iFi8nF9yqoXm2jvKdg1yZrqYdNhXDiCFmi03IQN4rfxoAksCcHn78exv/ XbHQ== X-Gm-Message-State: AOAM530TCb1z8LkXAS0n0WtUvOAnWbdJOdYK5/u0L2sW6OKNwoUD5ejm LUCiOMo00YPVG4itT+mQ5bAR5HLlj0jICs3A X-Google-Smtp-Source: ABdhPJy46BBy8bynMONbw9416nbdL88klrOT1OGcj1BTaHb8Jc9T8iOgj4Xixdwe4tyP9DpP/CoNKA== X-Received: by 2002:adf:dccc:: with SMTP id x12mr25898307wrm.72.1591104421866; Tue, 02 Jun 2020 06:27:01 -0700 (PDT) Received: from localhost ([5.226.137.4]) by smtp.gmail.com with ESMTPSA id k64sm3918755wmf.34.2020.06.02.06.26.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 02 Jun 2020 06:27:01 -0700 (PDT) From: Ihor Radchenko To: Bastien Subject: Re: [QUESTION] What's the ":desk" link parameter? In-Reply-To: <871rmxy7jy.fsf@bzg.fr> References: <877dx27sc6.fsf@gmail.com> <871rna5hvp.fsf@gmail.com> <87pnauvxht.fsf@localhost> <871rn9wqat.fsf@gnu.org> <87wo51o9bg.fsf@localhost> <871rmxy7jy.fsf@bzg.fr> Date: Tue, 02 Jun 2020 21:22:12 +0800 Message-ID: <87pnah38mz.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2a00:1450:4864:20::432; envelope-from=yantar92@gmail.com; helo=mail-wr1-x432.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Org Mode , John Kitchin Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=s4NFOckA; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -0.21 X-TUID: 0QKop7sJe9fJ > I'm not sure `org-link-make-description-function' is used a lot out > there, but the change may break existing configurations/hacks. It should not break anything. I did not remove `org-link-make-description-function' functionality. Just marked it as deprecated. > Also, is it something we could use in the current export backends > or just for the users? If the latter, then I'm in favor of making > this move, probably for 9.5. I am not very familiar with the export code, but the function provided in :description property should follow the same conventions with `org-link-make-description-function'. The only place it is used is org-insert-link. I do not see how it can influence export code. As I understand, org-insert-link is mostly for users. Best, Ihor Bastien writes: > Hi Ihor, > > Ihor Radchenko writes: > >>> thanks for the patch. I assume you are submitting it against master, >>> am I right? >> >> The patch is against commit 2e96dc639. > > I see, thanks. > >>> From reading this, I don't see what bug it fixes, what problem it >>> solves or what real user need it responds to, but maybe I lost part >>> of the context. Can you explain why this should be applied? >> >> It does not fix any bug. Rather adds a new feature [1]. Currently, org >> provides org-link-make-description-function as user customisation to >> compute default link description. The patch provides a way to set such >> description functions on per link type basis (via :description link >> parameter). Using link parameters looks natural for me since similar >> customisation is already done in :follow and :store link parameters. > > Okay, I understand. It feels natural to me too. > > I'm not sure `org-link-make-description-function' is used a lot out > there, but the change may break existing configurations/hacks. > > Also, is it something we could use in the current export backends > or just for the users? If the latter, then I'm in favor of making > this move, probably for 9.5. > > Nicolas, what do you think? > > -- > Bastien -- Ihor Radchenko, PhD, Center for Advancing Materials Performance from the Nanoscale (CAMP-nano) State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg