19:07 <x9f83kjdos9pksdf> I can't seem to get past this error: "raco setup: WARNING: undefined tag in <pkgs>/…my package name"

19:07 <x9f83kjdos9pksdf> Where should I start looking for the problem?

19:08 <x9f83kjdos9pksdf> AFAICT each of the functions listed is being exported exactly once.

20:53 <x9f83kjdos9pksdf> Sorry, my village just called. They want their idiot back.

20:54 <x9f83kjdos9pksdf> The undefined tags that it's complaining about… I hadn't actually got around to defining those in the .scrbl file yet! 🤦

21:39 <winny> x9f83kjdos9pksdf: that error is kind of cryptic, might be constructive to mention in the issue tracker

21:39 <winny> like what is a tag tbh, i didn't know scribble uses that lingo, i thought they were just procedures :)

23:58 <x9f83kjdos9pksdf> winny: AFAIU "tag" basically means "link" or "anchor". It's when something comes out with a red underline in the documentation. Yes, the error message could probably be made clearer, but at the end of the day the issue was that I simply had not defined the corresponding entries via @defproc, @defstruct*, etc., so the message was spot on.

23:58 <winny> Gotcha til :-) thx

23:58 <winny> Glad you figured it out

23:59 <x9f83kjdos9pksdf> In my defence, I was conditioned by an earlier attempt in a different

23:59 <x9f83kjdos9pksdf> package, which took me ages to figure out how to stop it complaining

23:59 <x9f83kjdos9pksdf> about "undefined tags". I think in the end the issue was that I was importing some of the functions twice, or using one path (like collection/module) in one place and a different one in another ("module.rkt"). They pointed to the same file but via a different route and that seemed to get scribble confused.