From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel,gmane.emacs.orgmode Subject: Re: Adding custom providers for thingatpt.el (was: [PATCH] Add support for 'thing-at-point' to get URL at point) Date: Mon, 05 Feb 2024 15:07:18 +0000 Message-ID: <875xz39cgp.fsf@localhost> References: <87leba3ame.fsf@localhost> <88435424-afa3-d7a3-56ff-df9f0a2ca6ba@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20441"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, emacs-orgmode@gnu.org To: Jim Porter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 05 16:04:58 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rX0Wo-0004zY-5t for ged-emacs-devel@m.gmane-mx.org; Mon, 05 Feb 2024 16:04:58 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rX0WB-0005pu-97; Mon, 05 Feb 2024 10:04:21 -0500 Original-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 1rX0Vq-0005oV-9t for emacs-devel@gnu.org; Mon, 05 Feb 2024 10:03:58 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rX0Vk-0005g9-9E for emacs-devel@gnu.org; Mon, 05 Feb 2024 10:03:57 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 1E16B240028 for ; Mon, 5 Feb 2024 16:03:49 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1707145429; bh=21+jHIdzxFpNplADqmzTnio7hRmzYYEvqZDK9xAiGbY=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=Y5DzcNtSktQ0gnIgotUsS1S/l8FMgLZPvjMI05ogv2p7uMEgGzEPeC4dV6AaXTNRP HPpM2Bc0azByrEzbSVAROxDUnnjBiWqdy3Krxtr5YCEJ9d/llRw5CqkHRw9BmZwFlU MntJihZQe8UzKfby3kgpFXoN2d8oF//esgZd0Kz32e9Jq/WIl215W4taEmHrjZTSP2 RUU1T7wLddV139EG1XlkX02QTr8yabv+4QjxflvEj68hg41BUr8npPoBrb2S9EuC/X 9CHG3gh7nUAw73dpfixy+DkEyLc3eQEyxvVgT4TYZw4hpxpfsUkogeDQ+9SYu/PBFx Jye33ZW/WV9xA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TT8lm2tBmz6tvl; Mon, 5 Feb 2024 16:03:48 +0100 (CET) In-Reply-To: <88435424-afa3-d7a3-56ff-df9f0a2ca6ba@gmail.com> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.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_H4=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=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:315893 gmane.emacs.orgmode:159622 Archived-At: Jim Porter writes: >> Looking into the source code of `bounds-of-thing-at-point', I see that >> for standard "things" (like url), >> `thing-at-point-bounds-of-url-at-point' is used unconditionally. In the >> case of Org links, we may have something like [[https://orgmode.org]] >> that will not match default URL regexp as is. AFAIU, there is no >> documented way to customize the behaviour of `bounds-of-thing-at-point' >> and `forward-thing'. > > I think it would make sense to add some sort of > 'bounds-of-thing-at-point-provider-alist' (that's a mouthful!) that > would let modes override the behavior of 'botap', but I don't think > that's necessary for the narrower purpose of asking, "I want the value > of THING at point, if any." It would make sense to add a number of alists: - bounds-of-thing-at-point-provider-alist - same for 'forward-op, 'beginning-op, 'end-op. After Emacs have those, we can add Org mode support. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at