Karl Fogel <kfo...@red-bean.com> writes: > In Org Mode buffers, `bounds-of-thing-at-point-provider-alist' > names a Org-Mode-specific URL provider: > ... > I think this is causing URL boundaries to be calculated > incorrectly. > > REPRODUCTION: > > Assume we have this line in an Org Mode buffer (note there are > three trailing spaces after the final "m" -- hopefully the MTAs > and MUAs will leave those spaces there): > > https://example.com > > Let's say the initial "h" is at position 22205, the position right > after the final "m" is 22224, and the final position on the line > (after the three spaces) is 22227. > > With point anywhere inside the URL, if I run > (bounds-of-thing-at-point 'url), I currently get this result: > > (22205 . 22227) > > But I expected this result instead: > > (22205 . 22224) > > Is (22205 . 22227) correct, and I'm just misunderstanding how URL > boundaries are supposed to work in Org Mode?
This is correct. Trailing whitespace belongs to the preceding node in Org syntax. This is not a bug. Moreover, if you have something like [[https//orgmode.org][description]] the whole thing will be considered a URL. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
