Max Nikulin <maniku...@gmail.com> writes: >> What about updating your patch to only use `call-process' on gnu systems >> and fallback to the existing code otherwise? > > Emacs developers made `call-process' default with exception for other > systems like darwin and windows. > > 5e377f4fcc0 2024-09-06 09:47:33 +0200 Manuel Giraud: Make > `dired-do-open' work on more *nix systems > > I do not like adding conditions inside `org-open-file'. It is already > excessively complex. On the other hand I can not figure out how to make > it more flexible without overwhelming configuration options.
Rather than overcomplicating things, we can: 1. Introduce some helper function/macro to do the right call depending on the OS. 2. Use the macro in `org-open-file' 3. Hold on with adding configuration options. If users actually request such feature, we can think further. WDYT? > Ideally users and developers who define new link types should be able to > just use the strategy default to the current OS. But since it appeared > to be fragile, users should be able to override default policy. I can > not figure out a source of resistance against using `browse-url' for URL > schemes with external handlers. People prefer to use some function to > start a process explicitly. Sorry, I do not understand what you are referring to and what you want to suggest in the context of this discussion. -- 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>
