[ESS] How to stop highlighting after eval-region

Martin Maechler maechler at stat.math.ethz.ch
Mon Mar 22 12:17:47 CET 2010

>>>>> "JT" == Jason Thomas <jthomas at ssc.wisc.edu>
>>>>>     on Thu, 18 Mar 2010 08:25:36 -0500 (CDT) writes:

    JT> Hi all,

    JT> The suggested fix (M-x customize-variable
    JT> ess-eval-deactivate-mark) did the trick (Thanks, Leo!!).
    JT> And sorry for the delayed response (I tried responding
    JT> earlier, but had to update my email address to do this
    JT> -- long time user and fan of ESS :) and I think this is
    JT> holding up my first reply).

    JT> Best Wishes, Jason

    JT> On Thu, 18 Mar 2010, Martin Maechler wrote:

    >>>>>>> "RoSp" == Rodney Sparapani <rsparapa at mcw.edu> on
    >>>>>>> Wed, 17 Mar 2010 08:49:51 -0500 writes:
    RoSp> On 03/17/10 03:10 AM, Martin Maechler wrote:
    LA> Try customizing the variable ess-eval-deactivate-mark
    LA> and set it to t (M-x customize-variable
    LA> ess-eval-deactivate-mark).
    >> >>
    >> >> Thank you, Leo, for helping..
    >> >>
    LA> (IMO, it should be true by default).
    >> >>
    >> >> I'd tend to agree: It has been true for me "forever".
    >> >>
    >> >> OTOH, I tend to be very reluctant in changing
    >> *defaults* >> of functions I write (in R, or Emacs lisp,
    >> ...): >> In theory, all calls of such a function (which
    >> does not >> explicitly set the option explicitly) would
    >> have to be >> reconsidered...
    >> >>
    >> >> OTOH, I also do agree that a change seems sensible.
    >> >> Note that this is only visible for those of us who
    >> have >> activated "transient mark mode" aka >> "Active
    >> Region Highlighting" >> ( = first entry of Emacs menu
    >> 'Options' )
    >> >>
    >> >> What do others ESS-lovers (and particularly experts)
    >> >> think about such a proposed change?
    >> >>
    >> >> Martin Maechler
    RoSp> Perhaps I'm being dense, but does this actually fix
    RoSp> the problem?  I haven't seen a response from Jason.
    RoSp> And the circumstances of his problem would suggest not
    RoSp> (it worked before, but after an upgrade of ESS, it
    RoSp> doesn't).
    >> well, I guess he updated ESS and Emacs at the same time,
    >> or changed his emacs configurations slightly, possibly
    >> inadvertently...
    >> It's definitely true that the ess-eval-deactivate-mark
    >> variable controls the behavior we are talking about.
    >> Jason, can you please try the recommendation and publicly
    >> confirm (or deny) that it helps ?
    RoSp> As this seems to be an Emacs-only issue, I can see no
    RoSp> objection provided it is actually needed and
    RoSp> sufficiently tested.
    >> Thanks.  .. Of course "sufficiently tested" maybe too
    >> hard: We (ESS developers) have only a few incantations of
    >>     >> Emacs that we use regularly, and there are not too many
    >> ESS users volunteering to work with the devel-version of
    >> ESS on a regular basis.
    >> Martin.

I have now changed the default in the development (aka
"subversion") version of ESS such that
there and hence in the next released version of ESS,


is 't' by default.

Martin Maechler, ETH Zurich

More information about the ESS-help mailing list