Identifying the cause of "Warning: Ignored unaccessible loci"

Trying to expand a master file with several subdocuments containing <hlink||> instructions to pages on the Internet, I often get this warning message:

Does anyone know if there’s a way to computationally locate

  • the file(s)

  • and the <hlink||>(s)

that cause the issue?

Doing this by hand on several files and numerous hlinks is excruciatingly painful and time-consuming. After having identified the roots of all evil, I clicked on these links to find that the loci are perfectly accessible. Why then these misleading warning messages?

Any ideas/suggestions appreciated.

Cheers, Tilda

I took a brief look, I did not understand what happens but here is some information. I think the messages are caused by typesetting code that calls the C++ function build_locus, which in turn calls the macro is accessible.

The macro is accessible is defined as

#define is_accessible(p) ((is_nil (p)) || ((p)->item >= 0))

I stopped here. Maybe someone else can take over. At first sight it refers to the accessibility of the locus for typing, not the accessibility of the link.

Giovanni

Dear Giovanni,

thanks for looking into this. I’m not quite sure what

… the accessibility of the locus for typing

really means. I get that warning message when I open the master document–but no messages when opening the subdocument that contains the hlink that causes the master file to complain. The accessibility of locus is indeed not referred to by the warning.

What’s the point then of the macro? Would it be able to identify obsolete hlink s?

Cheers, Tilda

It is a guess: I guess that it means that you can type over the link text. It works for a link I tested. Maybe you can try it for the “unaccessible loci”: if you can’t change the link text, then I think the guess is correct.

I don’t know as I do not know how C++ TeXmacs trees work. I found the information I posted by looking for "Ignored unaccessible loci"in the source code at GitHub and I followed the code calls. Also I do not have a clue for why you get

Maybe someone else does understand and can explain.