Janek F <xer...@pm.me> writes: > Considering the other messages, let's not get lost in details, the default > function does not need to consider all edge cases. It simply should not error > out on ids in a different format.
You are indeed right, but we may use multiple different approaches to achieve this. Some are more simplistic, some are less. We are trying to find a balance between less hassle for users and not overthinking things. The simplest approach would be wrapping the function calls into (ignore-errors ...), which would avoid errors when we just try to check the existence of the attachment dir. However, it may raise unexpected errors for non-standard/copy-pasted IDs for users who did not customize this area. The approach I am proposing is handling unexpected IDs inside the default functions and bringing errors in user-defined functions to the attention of user - I feel that it will be more useful than ignoring errors. We could use yet another approach and use a global fallback if no available function can generate an ID, but we may run into tricky cases because the first function in the list has a special meaning - it _must_ generate a path from ID or the user may run into unexpected breakage in some cases when custom IDs are being used. -- Ihor Radchenko, 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