Daniel Mendler

@veronikazaglotova @hmelman I also thought about having some all in one solution. Type "r" to access register r "wr" to store window config in r, "pr" to store position etc....

@hmelman I agree it would be quite different and the keysequence would be longer. I am also not using registers much probably because I don't find them very accessible. @veronikazaglotova...

@veronikazaglotova @hmelman I think it is better to not reinvent such a thing. What we could do however is improving the consult-register view and maybe add preview support for locations...

@hmelman what's the purpose of viewing the register content when you want to write? In order to not overwrite something and find a free register? Or did I misunderstand you?

@hmelman @oantolin @veronikazaglotova I added `consult-global-mark` to browse the global mark ring. Please test! :partying_face:

@hmelman No, nothing significant, I decided to keep it separate from `consult-mark` since I think it is conceptually different and it displays the candidates differently. Furthermore it requires buffer switching...

But I should add - I have quite a few more general purpose helper functions around which are used by both `consult-mark` and `consult-global-mark` and the other consult functions, so...

@hmelman Indeed, this looks indeed better. See https://github.com/minad/consult/commit/d29ee8d86d4ee5fe6e5851128d0adc0ff8ea7b48.

@hmelman The current proposed keybinding is not good, I agree. But I am also not so sure about `M-g M-m` since I think `consult-mark` and `consult-global-mark` serve different purposes and...

@hmelman > I do view them as related, particularly since the global mark is set by setting local marks. Many (even experienced) users don't know about these two rings, so...