Rainer M Krug writes: >> What do you expect? >> >> Should the "::*SOMETHING"-part be discarded without warning? > > Well - the ideal solution would be a warning (or error message) with a > reference to the link. At the moment, a link to a non existing file is > exported, a link to a section in a non existing produces a cryptic > error message. > > At the moment, I have no clue how I can find the link. > > So I would hope for > > 1) consistent behavior for the two cases > 2) a meaningful warning which helps to find the culprit > 3) an html file, where the links do not work, but the export is fine. > > or, if 3) is not possible, meaningful error messages which actually help > me to track down the error (I only found out what was causing this error > accidentally) The issue with warnings is that I don't see them.... Though an error seems a bit drastic here. The attached patch inserts a link without the anchor and issues a warning if exporting such links without ox-publish. >> The internal link cannot be known without the file, as it is of the form >> orgheadlineN where N=n+1 and n is the number of headlines prior to >> "*Something"... > > Sure - this is obvious. Actually, the error you found is more interesting than what I first though, as any link with anchors will trigger the error, it seems. org-publish-cache must be non-nil, which seems to linger on publishing a project. —Rasmus -- Don't panic!!!