[FR]: Fix mis-identification of similarly named buffers as "current buffer" in consult-buffer

[prosoitos]

I often switch back and forth between the most recent buffers. For this, I have a macro that uses consult-buffer. It works well, except in a situation that is actually very common in my workflow: things break down when using 2 files with the same name but different paths.

In that case, consult considers the buffers created from those files as being the same buffer, while they are obviously not.

Example:

Let's say that I am working on 2 files called theme.scss from different projects. They appear in the modeline as theme.scss<project1> and theme.scss<project2>.

Switching back and forth between them is a nightmare because consult will send both of them at the end of the consult-buffer queue, no matter which one I am visiting (because consult will wrongly consider both of them as "the current buffer").

It would be great if the full name displayed in the minibuffer (including the <some-project> part) were used instead of simply the file name.

This has been bothering me for a long time (and it actually took me a while to identify where things were breaking down in the reordering of consult-buffer).

Thank you!

[minad]

Hello!

Thanks for the report. I cannot reproduce this problem. consult--buffer-sort-alpha-current does not rely on the buffer name for reordering, but on identity of the buffer object, see:

consult/consult.el

Lines 4694 to 4700 in 45fdad7

	(defun consult--buffer-sort-alpha-current (buffers)
	"Sort BUFFERS alphabetically, put current at the beginning."
	(let ((buffers (consult--buffer-sort-alpha buffers))
	(current (current-buffer)))
	(if (memq current buffers)
	(cons current (delq current buffers))
	buffers)))

Can you create a minimal recipe which demonstrates the problem? Maybe something else in your configuration interferes?

[prosoitos]

Mmmm... interesting...

Thank you for your reply and sorry for getting back to you with a delay (I was away).

I will try to investigate and report here with what I find or a minimal recipe.

[prosoitos]

Sometimes I can reproduce my problem and sometimes I can't. So there indeed appears to be something going on locally, but because it is not consistent, it is hard to diagnose. I will look more into it, but it seems that indeed, there is nothing wrong with consult itself.

I am having the same problem when I use polymode. Sometimes things work as expected and sometimes consult-buffer is out of order. I am confused as to what is going on...

I will report here in the unlikely event that I find something on consult's side, but otherwise, I apologize for the noise.