From sfalcon at fhcrc.org  Sat Mar 25 00:37:20 2006
From: sfalcon at fhcrc.org (Seth Falcon)
Date: Fri, 24 Mar 2006 15:37:20 -0800
Subject: [Rd] Undocumented features of 'browser' (and possible changes)
In-Reply-To: <adf71a630603241441u26d7f577ta1a4b9448bf0253b@mail.gmail.com>
	(Kevin Wright's message of "Fri, 24 Mar 2006 16:41:36 -0600")
References: <adf71a630603241332g4e592112icc2944d969207924@mail.gmail.com>
	<x2lkuz7asy.fsf@turmalin.kubism.ku.dk>
	<adf71a630603241441u26d7f577ta1a4b9448bf0253b@mail.gmail.com>
Message-ID: <m2acbfmn2n.fsf@ziti.local>

"Kevin Wright" <kwright68 at gmail.com> writes:

> Thanks for the clarification about ENTER and for explaining that
> browser and debug use the same parser.  I'll crawl back into my
> cubicle and keep using my hack.  Maybe I'll look into  re-writing
> ess-eval-region to not send blank lines and comment lines.

Well, modifying ess to get what you want seems reasonable.  I have
used the ENTER as repeat feature so I wouldn't want that to go away.
But it does suggest a couple of alternative solutions:

1. Add one more command that the debug mode knows about that is a
   no-op.  Then copy/paste commands can send that first.

2. Add an option to browser that turns of the ENTER is repeat.

+ seth



[Rd] Undocumented features of 'browser' (and possible changes)
Seth Falcon