I made the original FR. I use AstroJS in my blog. It requires using relative URLs to link between pages. Details here: https://docs.astro.build/en/basics/astro-pages/#link-between-pages.
I think, it would be too complicated to have such links as valid links Org buffers as you'd need to implement the routing logic of the web framework (in this case AstroJS) which varies across users. You'd need to find how a relative URL maps to user's content directory structure. For example, a user can have a URL in his site like https://a.b.com/articles/someawesomearticle, and that may be located in src/content/someawesomearticle under his site project root. Whereas another user can use a URL as simple as https://a.b.com/someawesomearticle, but have his content source in src/content/articles/someawesomearticle. The URL structure is decided by how the user implemented routing logic of his website under pages/ subdirectory. And, regarding the other issues you mentioned, I never used those Org mode features. So, I have no idea about them. Maybe with a bit more explanation, I can help. Thank you. Ihor Radchenko <[email protected]> writes: > Earl Chase <[email protected]> writes: > >> +*** New custom variable ~org-export-file-links-verbatim~ >> + >> +~org-export-file-links-verbatim~ controls whether Org >> +mode exports file links that start with "/" verbatim. >> +Set it to t to export said links without first appending >> +~file:~ to them. >> + >> +This variable has no effect on links that are already prefixed with >> +=file:= or links that start with a =~=. > > I have doubts about this approach. > First, it will not work for publishing, because publishing will turn > absolute links into relative. > Second, the links like you described will not be valid links in Org mode > buffers. > Third, we have a very similar functionality in :html-link-home. > Finally, it is not clear why this option is global. Yes, it can be > useful for markdown export as you described, but, say, in odt export, it > will break things. > > Could you please describe in more details about your use case, providing > some examples? I feel that we need to discuss the overall export > workflow first and possibly come up with something that does not involve > creating broken links that do not work in Org buffers. > > Meanwhile, I have reverted the patch. Let's discuss the general feature > request first, and how to design the suggested feature better. > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=2277d10ac > > -- > Ihor Radchenko // yantar92, > Org mode maintainer, > 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> > -- Khalid Rafi Sent with Emacs
