`edit:histlist:start` takes current command as initial filter

[brunoroque06]

If I begin typing a command, and then trigger edit:histlist:start, the filter will start empty. I think there should be an option for the filter to be equal to the current command.

I think I understand the motivation for the current behavior; it is great to compose commands, one after the other with ;. But the problem is when we realize we want to search the history while typing the command, which then requires us to delete what we have typed so far, trigger edit:histlist:start, and type again the command. What do you think?