bug#15231: 24.3.50; eshell: variable `name' treated different from other variables

[Stefan Monnier]

>>> Is this a bug?
>> Sounds like it, yes.  More specifically it sounds like changing Eshell
>> to use lexical-binding would fix this bug.
> But why is this happening with just `name'?

I don't know the precise cause of the bug, but my crystal ball says that
the Eshell code that interprets your command itself uses a variable
named "name".  There are probably a few other variables names used by
Eshell that suffer from the same kind of "capture".


        Stefan