Add option to record Embark targets in minibuffer history

[ultronozm]

Addresses #712.

• embark.el (embark-record-minibuffer-history): New user option to
  control when acted-on minibuffer candidates are recorded in the
  minibuffer history. Defaults to skipping certain actions, such as
  export, collect, and become.
  (embark--record-history-p, embark--record-target-in-history): New
  helper functions.
  (embark--act): Use them to record target in history.

[minad]

Thanks, this looks like a good addition - not unexpected that I would say that given that I opened the issue. Let's hope that @oantolin agrees. ;)

Did you use this for a few days, and tested various completion commands/packages with it, e.g., Consult, just to see that it works as expected?

[ultronozm]

Did you use this for a few days, and tested various completion commands/packages with it, e.g., Consult, just to see that it works as expected?

I have (with Consult and other popular packages), although any specific suggestions for what might be worth testing would be very welcome.

[minad]

This should be generated from the Org file.

[ultronozm]

Thanks, I see.

When I attempt to export the texinfo myself (via org-texinfo-export-to-texinfo), the resulting embark.texi differs in many places from what's in the repo. Is there some other way to do this? Or should I just update README.org in the PR, and leave it to @oantolin to export to texinfo?

[minad]

I usually do it manually and just keep the relevant changes in the texinfo. But in my setup the difference is not that large.

[ultronozm]

Thanks, updated