Daniel Mendler

In don't think this is a good rule. There are many more such "include" keywords. Furthermore I'd also like to act in file names appearing at other places. I have...

> The rule is only for file names which are identifiers, where else would you want them? Okay then it is probably alright. But then I wonder why file is...

@oantolin > Because with point on the foo in ~/notes/foo.txt you want the target ~/notes/foo.txt before the target foo. One could add two file finders with different priorities (`embark-target-file-path-at-point`, `embark-target-guess-file-name-at-point`),...

Okay, I see. 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!) For more...

I've also just checked `embark--targets`. It removes duplicate targets, such that Embark is already prepared for a setup with multiple finders of the same type. One should probably not overdo...

Great, thanks! It is indeed nicer now with the clean separation of file name detection with high confidence and less reliable guessing via ffap. I see there was also a...

> That's debatable: in the default configuration I believe I was only generating adjacent duplicates so it didn't matter whether I took the first or last among duplicates. But now...

@Kaspazza I believe so. I haven't tested the feature though. Did you try it, if it works for your use case?

Can you give an example please? Patches welcome.

I am one of the Compat co-maintainers. compat-macs.el is an internal feature of Compat and must not be used by other packages. See this warning: https://github.com/emacs-compat/compat/blob/cccd41f549fa88031a32deb26253b462021d7e12/compat-macs.el#L20-L26 Instead of `compat-defun` use...