Hi Sébastien,
Sebastien Vauban
writes:
>> But it may be OK to allow a user to override.
>
> But I really find we should be able to override it, yes!
Can you provide a patch for this?
--
Bastien
Charles Berry wrote:
> Sebastien Vauban writes:
>> Aaron Ecay wrote:
>>> 2014ko abuztuak 29an, Sebastien Vauban-ek idatzi zuen:
>>>
Does it have something to do with `ess-eval-visibly' not being respected
(whose default is `t')?
>>>
>>> Indeed, babel’s R support let-binds this variable t
Sebastien Vauban writes:
>
> Hi Aaron,
>
> Aaron Ecay wrote:
> > 2014ko abuztuak 29an, Sebastien Vauban-ek idatzi zuen:
> >
> >> Does it have something to do with `ess-eval-visibly' not being respected
> >> (whose default is `t')?
> >
> > Indeed, babel’s R support let-binds this variable to nil
Hi Aaron,
Aaron Ecay wrote:
> 2014ko abuztuak 29an, Sebastien Vauban-ek idatzi zuen:
>
>> Does it have something to do with `ess-eval-visibly' not being respected
>> (whose default is `t')?
>
> Indeed, babel’s R support let-binds this variable to nil when evaluating
> value-type results in a sessi
Hi Seb,
2014ko abuztuak 29an, Sebastien Vauban-ek idatzi zuen:
[...]
> Does it have something to do with `ess-eval-visibly' not being respected
> (whose default is `t')?
Indeed, babel’s R support let-binds this variable to nil when evaluating
value-type results in a session.
--
Aaron Ecay
Hi Seb,
I'm not quite sure why the commands are not echoed and someone else
can probably explain this.
But for what it's worth, using a header argument ":results output"
shows the command plus their output in the *R* buffer.
Cheers,
Andreas
Hello,
I execute the following block of R code by going in the temporary buffer (via
`C-c '') and by sending the lines to the =*R*= buffer (via `C-c C-b').
#+begin_src R :eval yes
id.etp <- as.data.frame(c(111:113, 444, 555, 666))
names(id.etp) <- "Id"
id.etp
#+end_src
The commands are out
