Re: Please fix history-search-backward/forward

[Felipe Contreras <felipe.contreras@xxxxxxxxx>]

On Sun, Aug 29, 2010 at 1:33 AM, Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
> On 29 August 2010 00:23, Felipe Contreras <felipe.contreras@xxxxxxxxx> wrote:
>> On Sat, Aug 28, 2010 at 11:55 PM, Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
>>> On 28 August 2010 20:54, Felipe Contreras <felipe.contreras@xxxxxxxxx> wrote:
>>>> zle says:
>>>> Search backward in the history for a line beginning with the first
>>>> word in the buffer.
>>>>
>>>> GNU readline says:
>>>> Search backward through the history for the string of characters
>>>> between the start of the current line and the point.
>>
>>>> [1] http://zsh.sourceforge.net/Doc/Release/User-Contributions.html
>>>
>>> I think you want history-beginning-search-backward/forward ? Changing
>>> the effects of a widget is (and I think I can say this quite safely)
>>> is not really an option.
>>
>> I already mentioned history-beginning-search-backward/forward
>> (history-search-end), the point is not how to do that.
>
> history-beginning-search-backward and
> history-beginning-search-backward-end are not the same. The one I
> mentioned is builtin and doesn't need any autoloads.

Ah!

But this is misleading:

---
history-beginning-search-backward
Search backward in the history for a line beginning with the current
line up to the cursor.

history-search-backward
Search backward in the history for a line beginning with the first
word in the buffer.
---

So both start from the beginning, so what's the 'beginning' in the
former supposed to differentiate? Wouldn't history-cur-search-backward
make more sense? Or even better:

---
history-search-backward
Search backward in the history for a line beginning with the current
line up to the cursor.

history-word-search-backward
Search backward in the history for a line beginning with the first
word in the buffer.
---

Note: I'm only objecting to the misleading names.

-- 
Felipe Contreras