comint history for ess

Thomas Gerds gerds at
Fri Oct 12 10:05:01 CEST 2001

Jeff Mincy <jeff at> writes:

> I thought about it some, and I'm not really buying the idea.  lines
> that you type to a comint prompt, are likely to be needed again,
> but things that you ess-eval, are things that you are likely to ess-eval
> again, but not that you are going to explictly type want completion.

if a command was sent by ess-eval, the code shows up in the
inferior-ess-buffer as if it was typed behind the prompt. now, when i
evaluate a command with ess-eval-...-and-go then i can see it sitting
one prompt above the current cursor position but i can not retrieve it
from where i am (i know it is just idleness) ...

... on the other hand if very long code is evaluated through
ess-eval, most often it is not necessary to see a full copy in the
inferior-ess-buffer (since it is always visuable in a different
buffer). it would be easier to distinguish between code and output if
(for very long code) only an abrivated version like

                    foo <- function() ... 

would appear in the inferior-ess-buffer! however, you may be right
that these ideas only apply to my way of using ess.

> But, hey, if you really want it....

thanks a lot for your help! the defadvice is almost working correctly,
only that comint-input-ring is nil since ess-eval-linewise is not
called from the inferior-ess-buffer:

>(defadvice ess-eval-linewise (after add-history first activate)
>  (comint-add-to-input-history text-withtabs))

do you have a fix for that? i will also try and error myself ... :)

thanks again,

Signature for mail groups
ess-help mailing list -- To (un)subscribe, send
subscribe	or	unsubscribe
(in the "body", not the subject !)  To: ess-help-request at

More information about the ESS-help mailing list