Target :type is 'file when switching to a project with projectile

[rmolinari]

Embark version: 1.1
Consult version: 3.4
Marginalia version: 2.1

I have defined a simple action that I'd like to have for projects when selecting one via projectile-switch-project. Based on the section "Defining actions for new categories of targets" in the manual I have this in my init code:

(defvar-keymap my/embark-projectile-actions
  :doc "Keymap for actions for project(ile) names"
  :parent embark-general-map
  "k" #'projectile-remove-known-project)

(add-to-list 'embark-keymap-alist '(project-file . my/embark-projectile-actions))

This used to work, but doesn't any more. When I act on a project target with embark-act I don't see the binding to k in the map. The behavior is the same if I add this:

(add-to-list 'marginalia-prompt-categories '("Switch to project" . project-file))

(My comments say that I noticed it was no longer working on 2025-07-16.)

I spent some time with the code and noticed that when I'm in the minibuffer on a project name, this is the value returned by embark--targets:

((:orig-type project-file :orig-target "~/org/" :bounds nil :type file :target "/Users/rory/org/"))

Notice that :orig-type is correct, but :type is just plain old 'file. This value for :type is determined in embark--targets by a call to embark--project-fill-file-path.

It looks like :orig-type is not used to determine the keymap to pick. embark-act does this (though it is deep in some let/let* code so I may be misunderstanding the call):

(embark--action-keymap (plist-get target :type) (cdr targets))

What am I doing wrong?

[oantolin]

This behavior is on purpose. There is a transformer added for the project-file type that converts the file name to a full path and changes the type to file. This way, you can use arbitrary file actions with project-file targets. Now, if you don't mind loosing those file actions, you could remove the transformer:

(setf (alist-get 'project-file embark-transformer-alist) nil)

Another thing you could do, is to add an action to remove a project to the general file actions, that way you can use it on a project directory no matter where you got it from. That would just mean adding your action key binding to embark-file-map instead of this new my/embark-projectile-actions.

(But I have to ask, not being a projectile user myself, does projectile-remove-known-project really take a file path? Is that how projects are identified in projectile? If so, I assume it removes the project containing the file. Oh, or does it only work on the path to the project root?)