[ESS] disabling C-c h bound to ess-handy-commands
alix.tofigh at gmail.com
Mon Oct 8 04:27:56 CEST 2012
On Sun, Oct 7, 2012 at 4:32 PM, Vitalie Spinu <spinuvit at gmail.com> wrote:
> I propose to redefine/remove some less used key. For instance
> C-c C-d ess-dump-object-into-edit-buffer
> Would be good to have this for documentation (index, apropos etc) like
> slime does. And put ess-dump-object-into-edit-buffer on C-c C-e or
> something else.
> C-c C-f ess-eval-function
> This one is redundant with C-c C-c and C-M-x, may be remove altogether
> and put something useful on it.
> C-c C-k ess-force-buffer-current
> Is this one equivalent to C-c C-s?
> C-c C-n ess-eval-line-and-step
> We have C-RET for this. C-c C-n is too lengthy for such a task. Can be
> C-c C-r ess-eval-region
> If transient-mark is active. This one is redundant with C-c C-c,
> C-M-x, C-RET. Roxygen would be good on it.
> C-c C-t ess-execute-in-tb
> Who is using this one? Would be good to have it for dev-map.
> C-c C-y ess-switch-to-ESS
> Who is using this one? C-c C-z should be pretty enough.
I actually didn't know about the versatility of C-c C-c until now that
you mentioned it, so I have become used to using many of the shortcuts
in your list. But I can easily relearn to use only C-c C-c and C-c
RET, which seem to be the only ones I would need. You didn't mention
C-c C-p which evaluates a paragraph. But I actually think that C-c C-p
should be kept, becuase I often wind up evaluation paragraphs inside
functions when debugging. So in summary, I would personally agree that
all the shortcuts you mentioned could be replaced, except for C-c C-p,
which you actually didn't mention. :-)
More information about the ESS-help