Omar Antolín Camarena
Omar Antolín Camarena
Found a work around: if you make the menu appear for the next to last comment, and then try to produce the one for the last comment, it does appear.
Now that we use the new selection functionality instead, I think I don't want a marker character, for uniformity with regular buffers where I certainly don't want such a character.
I think writing a new component matching style is the best way to go here. If anyone wants to contribute one to the wiki that would be great. (I don't...
As things turned out, I wound up implementing a slightly different org target finder in the embark-org library. I still don't have key bindings for all the actions that @sheijk's...
I regard this as essentially unfixable in Embark, but at the same time the tools we have to mitigate the problem seem sufficient. Commands like `org-ql-find` are weird in that...
Maybe we can revisit this now that I finally added support for menu-items and their `:filter` properties.
My current opinion is that it is good to have support for menu-item and :filter just so embark can use existing keymaps that might happen to use that, such as...
I'm closing this issue: I don't think we really need it. People that feel strongly about it can already do it in their configuration: you can always define narrower target...
I followed @minad's suggestion to leave `revert-buffer-function` alone and added a new `embark--rerun-function` instead. I remapped `revert-buffer` to run `embark-rerun-collect-or-export` so `g` still works as before.
Whoops, forgot to update some docstrings. 😬