[ESS-bugs] 12.09-1: ess-eval-visibly vs ess-eval-visibly-p

[Martin Maechler]

>>>>> Vitalie Spinu <spinuvit at gmail.com>
>>>>>     on Sat, 20 Oct 2012 14:35:17 +0200 writes:

    >>> Martin Maechler <maechler at stat.math.ethz.ch> on Sat, 20
    >>> Oct 2012 14:01:00 +0200 wrote:

    MM> Mainly for Vitalie, You have replaced ess-eval-visibly-p
    MM> by the version without '-p' keeping the old one as alias
    MM> ...  which at first looks ago.

    MM> But for me who sets ess-eval-visibly-p to nil in one of
    MM> my emacs startup scripts, the effect is "dramatic":

    MM> Inside ESS, ess-eval-visibly-p takes its value from
    MM> ess-eval-visibly and that is t by default.  ===> My
    MM> setting of ess-eval-visibly to nil has no effect
    MM> anymore.

    > I am also setting ess-eval-visibly-p to nil, and
    > everything is as expected.

    > My guess is that you set ess-eval-visibly-p before loading
    > ESS. I tried that, and indeed it has the effect that you
    > described.

Exactly  {in one of my startup scripts that ... believe it or
not ... predates the 'custom' at least in its current good form}.

    MM> I'm pretty sure that many other ESS users would be
    MM> similarly affected... So I think we need a different
    MM> "trick" to move from using the *-p version to the one
    MM> that emacs standards recommend (namely w/o "-p").

    > It's an easy trick - revert the order of defcustom and
    > defvaralias during the initialization. I have done it in
    > trunk, should be fine now.

Excellent... I'll let you know if I observe any more.
Martin

    >     Thanks, Vitalie