Re: dabbrev-expand in minibuffer: well, would I be posting if it were OK?

[Eli Zaretskii]

On 18 Jun 2001, Dan Jacobson wrote:

> type this: M-x compile ./oneside 153.80 237000;./oneside 153.40
> 
> Ok before you type RET, add a 2:
> Compile command: ./oneside 153.80 237000;./oneside 153.40 2
> and start pounding on M-/ M-/ M-/
> One would think that we could quickly arrive at
> Compile command: ./oneside 153.80 237000;./oneside 153.40 237000
> but no, one has to go thru all the expansions of the 2 stuff lying
> around in other buffers before we see the 237000 from a mere couple
> words back show up as an expansion.

This is a feature: dabbrev-expand favors the buffer from which M-x was
invoked, and it does so by starting its search from that buffer.

> So this means the minibuffer shouldn't have some special default
> avoidance... just treat it like a normal buffer...

That would be not what users expect in most cases.

> Yeah I know I can customize this and that

So, given your ability to customize this, where is the problem?