R devel - Mar 2013 - ess completion

The thread is strange to me as well, since completion is logically impossible
for my
Sweave files.
     - an emacs buffer is open working on an .Rnw file
     - there is no copy of R running anywhere on the machine
     - the code chunk in the .Rnw file refers to a R data object saved somewhere
else
Of course it cannot do "name completion" on a bit of code I'm
writing, lacking omniscient
powers.  Emacs is good but not that good :-)

The ESS manual section 12.1 states that for .R files it has "completion of
object names
and file names".  I'm puzzled by exactly what this means, since it is
logically impossible
(without a running R session) to do this in general.
Linking an .Rnw file to an inferior R process doesn't make sense to me.

However, I think it's time to move this sub-thread off of R-devel.  Respond
to me
privately about the answer or the proper list for this discussion.

Terry T

On 03/22/2013 06:00 AM, r-devel-request at r-project.org
wrote:
> This thread is strange for me to read as I've been getting completion
of
> object names, function arguments names, and whatnot in ESS buffers for as
> long as I can have been using it. And I'm only on ESS 12.09.
>
> Perhaps you need to set `ess-use-R-completion` to non-nil. Or check the
> value of `completion-at-point-functions`. Mine is
'(ess-roxy-tag-completion
> ess-filename-completion ess-object-completion t)
>
> Peter

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 22/03/13 13:30, Terry Therneau wrote:
> The thread is strange to me as well, since completion is logically
impossible for my Sweave
> files. - an emacs buffer is open working on an .Rnw file - there is no copy
of R running
> anywhere on the machine - the code chunk in the .Rnw file refers to a R
data object saved
> somewhere else Of course it cannot do "name completion" on a bit
of code I'm writing, lacking
> omniscient powers. Emacs is good but not that good :-)
> 
> The ESS manual section 12.1 states that for .R files it has
"completion of object names and
> file names".  I'm puzzled by exactly what this means, since it is
logically impossible (without
> a running R session) to do this in general. Linking an .Rnw file to an
inferior R process
> doesn't make sense to me.
> 
> However, I think it's time to move this sub-thread off of R-devel. 
Respond to me privately
> about the answer or the proper list for this discussion.
If anybody wants to continue this ESS discussion:

The proper list is the ESS mailing list:
https://stat.ethz.ch/mailman/listinfo/ess-help

See you there,

Rainer
> 
> Terry T
> 
> On 03/22/2013 06:00 AM, r-devel-request at r-project.org wrote:
>> This thread is strange for me to read as I've been getting
completion of object names,
>> function arguments names, and whatnot in ESS buffers for as long as I
can have been using it.
>> And I'm only on ESS 12.09.
>> 
>> Perhaps you need to set `ess-use-R-completion` to non-nil. Or check the
value of
>> `completion-at-point-functions`. Mine is '(ess-roxy-tag-completion
ess-filename-completion
>> ess-object-completion t)
>> 
>> Peter
> 
> ______________________________________________ R-devel at r-project.org
mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys.
(Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer at krugs.de

Skype:      RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRTF8CAAoJENvXNx4PUvmCrSQH/inP6c5JT+YEJYDEGOkLQOiA
8GLGzgCdO+iekF1EMrKVvcPjim14gRu+y2HcryxMO44w1gIutcY2wpq6m7OYvCXI
BV40TjKut6nLzopx0IWVr0vX+mA5IybKiziup+lSS86gb5E8QNRVlBFIw3Xp2TXP
rMlS6kkNiQR6y94lwdnUJTy/FerqsV9sQNnNUNipTPt9coL4qISyl1TDoDImrtgM
kCG/kSoUnazzldH39qHgfEJb4rhgCLISNFKbPmtCuCbKh+iF0bHJF4rlEXrSkiRu
GsmfV1Ln3hWmYijtOygHUlmeSiiVTZVVtfXA5oXrW/GXVvDCYEkSTDuu3JbIj7o=DJwz
-----END PGP SIGNATURE-----