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

[Vitalie Spinu]

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

  MM> Mainly for Vitalie,
  MM> You have replaced ess-eval-visibly-p  by the version without  '-p'
  MM> 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 my emacs
  MM> startup scripts,
  MM> the effect is "dramatic":

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

  MM> I'm pretty sure that many other ESS users would be similarly
  MM> affected... So I think we need a different "trick" to move from
  MM> using the *-p version to the one that emacs standards recommend
  MM> (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.

    Thanks, 
    Vitalie