Omar Antolín Camarena

Yeah, as I said I'm not convinced this is a good rule, but like @woolsweater, I don't really like that `class Foo` matches `Foo.py`. > There are many more such...

> But then I wonder why file is not prioritized lower than identifier. Because with point on the `foo` in `~/notes/foo.txt` you want the target `~/notes/foo.txt` before the target `foo`.

I like that suggestion, @minad! > Iirc we've avoided adding multiple finders until now We have _mostly_ avoided it, but not completely: there are `embark-target-library-file-at-point` (for elisp libraries) and `embark-target-file-at-point`....

> I thought libraries at point have some further special treatment, such that they do not really count as files. (EDIT: They have their own map!) Yes, a symbol naming...

I went with @minad's suggestion instead of hard-coding some `import`-like keywords. Thanks, @minad, it is much nicer this way.

> I see there was also a bug in the target deduplication :) That's debatable: in the default configuration I believe I was only generating adjacent duplicates so it didn't...

Oops, thanks for reporting. I can confirm the problem. I'll reopen this as a reminder.

I'm sorry, I don't think I understand what could cause this other than it seems like maybe it's some sort of installation problem? After installing Org 9.7, I reinstalled every...

Well, that just removes most of embark's org support, @rmathew8-gh. I'd suggest instead loading org and recompiling embark-org.

Well, I already suggested it but I can suggest the same thing again: find your copy of embark-org and recompile it. More specifically, first load org with `M-x load-library RET...