Re: [ESS] ess-dump-object-into-edit-buffer
> Vitalie Spinu> on Wed, 25 Apr 2018 11:16:57 +0200 writes: > I don't see this in 3.4.4 nor in Devel. >>> On Wed, Apr 25 2018 10:55, Lionel Henry wrote: >> Doesn't setting `options(deparse.max.lines = NA)` do the trick? >> Martin fixed this for R 3.5 btw. > Fixed in what sense? `dump` should not be abiding that option. It has it's own > control with .deparseOpts. Well, did you try? .. That's why it was a bug .. which was never reported at all, till Lionel mentioned it here (or the github issue). Martin Maechler ETH Zurich and R Core __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ess-dump-object-into-edit-buffer
On Tue, 24-Apr-2018 at 08:20AM -0400, Ista Zahn wrote: |> On Tue, Apr 24, 2018 at 4:13 AM, Patrick Connolly |>wrote: |> > On Mon, 16-Apr-2018 at 09:02AM -0400, Ista Zahn wrote: |> > |> > [...] |> > |> > |> This suggests to me that you did _not_ start with emacs -q, so indeed |> > |> you should start looking at your configuration to see where the |> > |> problem is. Did you try commenting out the 'ess-source-directory' |> > |> setting to see if that is the problem? |> > |> > I tried that, half-expecting it to make the difference. But it didn't |> > -- which was only half-unexpected. However, I *still* get the problem |> > even starting with emacs -q. That was completely unexpected since it |> > would indicate that the problem is not with my .emacs file. |> > |> > Where else is there to investigate? It's getting curiouser and |> > curiouser. |> |> Hi Patrick, |> |> What I've been trying to tell you is that we need explicit |> step-by-step instructions for reproducing the problem, as well as the |> details of your set up such as operating system and emacs and ess |> versions. Basically, please provide a standard, reproducible, and |> complete bugreport. Well, I thought I did that with what I posted on 16/4/18, though I did neglect to give the system information: GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.10.8) of 2017-09-20 on lcy01-35, modified by Debian ess-17.11 > sessionInfo() R version 3.4.4 (2018-03-15) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Ubuntu 14.04.5 LTS Matrix products: default BLAS: /home/pat/local/R-3.4.4/lib/libRblas.so LAPACK: /home/pat/local/R-3.4.4/lib/libRlapack.so locale: [1] LC_CTYPE=en_NZ.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_NZ.UTF-8LC_COLLATE=en_NZ.UTF-8 [5] LC_MONETARY=en_NZ.UTF-8LC_MESSAGES=en_NZ.UTF-8 [7] LC_PAPER=en_NZ.UTF-8 LC_NAME=C [9] LC_ADDRESS=C LC_TELEPHONE=C [11] LC_MEASUREMENT=en_NZ.UTF-8 LC_IDENTIFICATION=C attached base packages: [1] utils stats grDevices graphics methods base other attached packages: [1] lattice_0.20-35 loaded via a namespace (and not attached): [1] compiler_3.4.4 magrittr_1.5 https://www.antiaging-systems.com/articles/31-bec-5-the-treatment-of-choice-for-non-melanoma-skin-cancers assertthat_0.2.0 R6_2.2.1 [5] tools_3.4.4 pillar_1.2.1 bindrcpp_0.2.2 glue_1.2.0 [9] dplyr_0.7.4 tibble_1.4.2 Rcpp_0.12.16 grid_3.4.4 [13] pkgconfig_2.0.1 rlang_0.2.0 bindr_0.1.1 > best Patrick -- ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. ___Patrick Connolly {~._.~} Great minds discuss ideas _( Y )_ Average minds discuss events (:_~*~_:) Small minds discuss people (_)-(_) . Eleanor Roosevelt ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ess-dump-object-into-edit-buffer
On Tue, Apr 24, 2018 at 4:13 AM, Patrick Connollywrote: > On Mon, 16-Apr-2018 at 09:02AM -0400, Ista Zahn wrote: > > [...] > > |> This suggests to me that you did _not_ start with emacs -q, so indeed > |> you should start looking at your configuration to see where the > |> problem is. Did you try commenting out the 'ess-source-directory' > |> setting to see if that is the problem? > > I tried that, half-expecting it to make the difference. But it didn't > -- which was only half-unexpected. However, I *still* get the problem > even starting with emacs -q. That was completely unexpected since it > would indicate that the problem is not with my .emacs file. > > Where else is there to investigate? It's getting curiouser and > curiouser. Hi Patrick, What I've been trying to tell you is that we need explicit step-by-step instructions for reproducing the problem, as well as the details of your set up such as operating system and emacs and ess versions. Basically, please provide a standard, reproducible, and complete bugreport. Best, Ista > > Thanks for looking into it. > > -- > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. >___Patrick Connolly > {~._.~} Great minds discuss ideas > _( Y )_ Average minds discuss events > (:_~*~_:) Small minds discuss people > (_)-(_) . Eleanor Roosevelt > > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ess-dump-object-into-edit-buffer
On Mon, 16-Apr-2018 at 09:02AM -0400, Ista Zahn wrote: [...] |> This suggests to me that you did _not_ start with emacs -q, so indeed |> you should start looking at your configuration to see where the |> problem is. Did you try commenting out the 'ess-source-directory' |> setting to see if that is the problem? I tried that, half-expecting it to make the difference. But it didn't -- which was only half-unexpected. However, I *still* get the problem even starting with emacs -q. That was completely unexpected since it would indicate that the problem is not with my .emacs file. Where else is there to investigate? It's getting curiouser and curiouser. Thanks for looking into it. -- ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. ___Patrick Connolly {~._.~} Great minds discuss ideas _( Y )_ Average minds discuss events (:_~*~_:) Small minds discuss people (_)-(_) . Eleanor Roosevelt ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ess-dump-object-into-edit-buffer
Hi Patrick, On Mon, Apr 16, 2018 at 5:10 AM, Patrick Connollywrote: > This is about the shortest I can get that shows what happens: Just > what the example function does is not material to my question. Can you reproduce this following only these instructions starting from 'emacs -q'? I cannot, i.e., it works as expected for me. > (custom-set-variables > ;; custom-set-variables was added by Custom -- don't edit or cut/paste it! > ;; Your init file should contain only one such instance. > '(inferior-ess-dump-command "dump(\"%s\",file=\"%s\", control=\"useSource\") > ") > '(ess-source-directory "./.tmp") > '(load-home-init-file t t)) This suggests to me that you did _not_ start with emacs -q, so indeed you should start looking at your configuration to see where the problem is. Did you try commenting out the 'ess-source-directory' setting to see if that is the problem? Best, Ista > > Ideas as to where I should look are welcome. > > best > Patrick > > On Thu, 12-Apr-2018 at 11:08PM -0400, Ista Zahn wrote: > > |> Hi Patrick, > |> > |> I don't use ess-dump-object-into-edit-buffer, so I'm not sure what > |> exactly you expect it to do. A specific example would help, i.e., a > |> description of exactly what you did, exactly what happened, and how > |> what happened differed from you expectation. > |> > |> For example, if I start R with 'M-x R ' and do 'M-x > |> ess-dump-object-into-edit-buffer getwd ' I see a new buffer > |> is created containing > |> > |> getwd <- > |> function () > |> .Internal(getwd()) > |> > |> Is that what you see? If so, how does it differ from what you expect? > |> If you see something different, how does your setup differ from mine? > |> I'm running Emacs 25.3 and ESS 17.11 [elpa: 20180412.315] > |> > |> Best, > |> Ista > |> > |> On Thu, Apr 12, 2018 at 7:19 PM, Patrick Connolly > |> wrote: > |> > Thanks Ista. > |> > > |> > The result is not the same, but it's equally useless. It produces almost > |> > the same as typing the name of the function and pressing . That > is to > |> > say, unless the function has been edited in the working directory, it > lists > |> > all the code without any of the comments almost in the form of a list > |> > element labelled "structure" and a second element labelled "source" which > |> > contains all the source in the form of a character vector. Quite a lot > of > |> > text wrangling is required to get that text into the form of an editable > |> > function. > |> > > |> > There is a slight difference from what results from typing the function > name > |> > and pressing in that the word "structure" is not in the latter > and > |> > the source is an attr. > |> > > |> > (I say "almost" because neither form is exactly the same as how a list is > |> > displayed.) > |> > > |> > Is that intended behaviour? > |> > > |> > TIA > |> > Patrick > |> > > |> > On 04/13/2018 01:48 AM, Ista Zahn wrote: > |> > > |> > On Thu, Apr 12, 2018 at 3:56 AM, Patrick Connolly > |> > wrote: > |> > > |> > Thanks for the response, however, if I start Emacs with a '-q' none of > |> > my ~/.emacs file is read, so Emacs doesn't know how to start R. More > |> > to the point, I'm unable to run R within Emacs any other way. > |> > > |> > The usual recipe is to start with emacs -q and then evaluate > |> > > |> > (package-initialize) > |> > (require 'ess-site) > |> > > |> > in the scratch buffer, then check to see if you can reproduce the bug. > |> > If you have ESS installed in a way that it is not in your load-path by > |> > default you may have to do something along the lines of > |> > > |> > (add-to-list 'load-path "/path/to/ESS/lisp/") > |> > (load "ess-site") > |> > > |> > Best, > |> > Ista > |> > > |> > > |> > > |> > I gather there is a way of applying individual lines of the .emacs > |> > files but a bear with a small brain doesn't know how to do that (or > |> > where to look in the manual how to do it), > |> > > |> > It would appear, if it doesn't reproduce, that the problem is > |> > somewhere in my .emacs file. That's a hodge-podge of various things > |> > I've picked up over the decades so it wouldn't be surprising to find > |> > some incompatibilities. > |> > > |> > Ideas appreciated. > |> > > |> > > |> > On Wed, 11-Apr-2018 at 07:44AM -0400, Ista Zahn wrote: > |> > > |> > |> I can't reproduce it with the latest ESS from melpa. Can you give > |> > |> reproduction steps starting with > |> > |> > |> > |> emacs -q > |> > |> > |> > |> ? > |> > |> > |> > |> --Ista > |> > |> > |> > |> On Wed, Apr 11, 2018 at 4:58 AM, Patrick Connolly > |> > |> wrote: > |> > |> > For a long time I used to be able to use > |> > |> > > |> > |> > ess-dump-object-into-edit-buffer > |> > |> > > |> > |> > to create a buffer that could be used to edit the designated > function > |> > |> > from anywhere on the search path to make a local version. > |> > |> > > |>
Re: [ESS] ess-dump-object-into-edit-buffer
This is about the shortest I can get that shows what happens: Just what the example function does is not material to my question. ## from the bash prompt mkdir ~/Temp/First cd ~/Temp/First emacs & # start R using M-x R ## within the *R* buffer make a short function bringLibrary <- function(lastR = "3.0.2", latestR = "3.1.0", Rloc = "~/local/"){ ### Purpose:- Bring library from older R version to newer one. ### (Idea is to then update the packages that need to be) ### -- ### Modified from:- ### -- ### Arguments:- lastR: version of R that has the packages desired ### latestR: latest version of R of interest ### Rloc: where R versions are located (probably not the default) ###Make sure there's a trailing "/" ### -- ### Author:- Patrick Connolly, Date:- 29 May 2014, 11:08 ### -- ### Revisions:- 22/08/14 fixed mistaken swap of lastR & latestR ### 15/10/15 location of R installions made adjustable ### 7//2017 Rloc changed back to ~/local now <- system(paste0("ls ", Rloc, "R-", latestR, "/library"), TRUE) was <- system(paste0("ls ", Rloc, "R-", lastR, "/library"), TRUE) need <- was[!is.element(was, now)] ### Check if it's already been done if(length(need) < 1) stop("Nothing in R-", lastR, " that isn't already in R-", latestR, ".\n") for(i in need) # reason for running this function system(paste0("cp -prv ", Rloc, "R-", lastR, "/library/", i, " ", Rloc, "R-", latestR, "/library/")) ### Notify it's finished and give pastable text to update copied packages cat(length(need), " packages copied into R-", latestR, " directory.\nProbably a good idea to start R-", latestR, " and run\n update.packages(checkBuilt = TRUE, ask = FALSE)\n", sep = "") } ## now save and exit then start in another directory: > q() Save workspace image? [y/n/c]: y ## from the bash prompt mkdir ~/Temp/Second cd ~/Temp/Second emacs & # start R using M-x R ## Within the *R* buffer > attach("../First/.RData") > ls(pos = 2) [1] "bringLibrary" "repos" ## Then 'M-x ess-dump-object-into-edit-buffer bringLibrary ' bringLibrary <- function(lastR = "3.0.2", latestR = "3.1.0", Rloc = "~/local/") { ### Purpose:- Bring library from older R version to newer one. ### (Idea is to then update the packages that need to be) ... ## but in the *R* buffer all code and comment are there. > bringLibrary function(lastR = "3.0.2", latestR = "3.1.0", Rloc = "~/local/") { ### Purpose:- Bring library from older R version to newer one. ### (Idea is to then update the packages that need to be) ### -- ### Modified from:- ### -- ### Arguments:- lastR: version of R that has the packages desired ### latestR: latest version of R of interest ### Rloc: where R versions are located (probably not the default) ###Make sure there's a trailing "/" ### -- ### Author:- Patrick Connolly, Date:- 29 May 2014, 11:08 ### -- ### Revisions:- 22/08/14 fixed mistaken swap of lastR & latestR ### 15/10/15 location of R installions made adjustable ### 7//2017 Rloc cchanged back to ~/local now <- system(paste0("ls ", Rloc, "R-", latestR, "/library"), TRUE) was <- system(paste0("ls ", Rloc, "R-", lastR, "/library"), TRUE) need <- was[!is.element(was, now)] ### Check if it's already been done if(length(need) < 1) stop("Nothing in R-", lastR, " that isn't already in R-", latestR, ".\n") for(i in need) # reason for running this function system(paste0("cp -prv ", Rloc, "R-", lastR, "/library/", i, " ", Rloc, "R-", latestR, "/library/")) ### Notify it's finished and give pastable text to update copied packages cat(length(need), " packages copied into R-", latestR, " directory.\nProbably a good idea to start R-", latestR, " and run\n update.packages(checkBuilt = TRUE, ask = FALSE)\n", sep = "") } ## Initially this example function was made by 'M-x ess-dump-object-into-edit-buffer bringLibrary ' That produced a blank file into which the skeleton function was dumped using 'C-c f' which I find very handy. In this case it's not very tedious to paste the requisite code into the edit function buffer, but for longer functions (often found in packages) if I want to make a local copy to edit, it is very tedious -- particularly when the comments are all stripped and placed in a
Re: [ESS] ess-dump-object-into-edit-buffer
G'day Ista, I'm having trouble getting an example small enough to show. Some work properly and others (usually longer ones) don't. Can't imagine what makes the difference. I'll be at the machine where I normally work and there I'll find a small example. Thanks for looking at my problem. best Patrick On Thu, 12-Apr-2018 at 11:08PM -0400, Ista Zahn wrote: |> Hi Patrick, |> |> I don't use ess-dump-object-into-edit-buffer, so I'm not sure what |> exactly you expect it to do. A specific example would help, i.e., a |> description of exactly what you did, exactly what happened, and how |> what happened differed from you expectation. |> |> For example, if I start R with 'M-x R ' and do 'M-x |> ess-dump-object-into-edit-buffer getwd ' I see a new buffer |> is created containing |> |> getwd <- |> function () |> .Internal(getwd()) |> |> Is that what you see? If so, how does it differ from what you expect? |> If you see something different, how does your setup differ from mine? |> I'm running Emacs 25.3 and ESS 17.11 [elpa: 20180412.315] |> |> Best, |> Ista |> |> On Thu, Apr 12, 2018 at 7:19 PM, Patrick Connolly |>wrote: |> > Thanks Ista. |> > |> > The result is not the same, but it's equally useless. It produces almost |> > the same as typing the name of the function and pressing . That is to |> > say, unless the function has been edited in the working directory, it lists |> > all the code without any of the comments almost in the form of a list |> > element labelled "structure" and a second element labelled "source" which |> > contains all the source in the form of a character vector. Quite a lot of |> > text wrangling is required to get that text into the form of an editable |> > function. |> > |> > There is a slight difference from what results from typing the function name |> > and pressing in that the word "structure" is not in the latter and |> > the source is an attr. |> > |> > (I say "almost" because neither form is exactly the same as how a list is |> > displayed.) |> > |> > Is that intended behaviour? |> > |> > TIA |> > Patrick |> > |> > On 04/13/2018 01:48 AM, Ista Zahn wrote: |> > |> > On Thu, Apr 12, 2018 at 3:56 AM, Patrick Connolly |> > wrote: |> > |> > Thanks for the response, however, if I start Emacs with a '-q' none of |> > my ~/.emacs file is read, so Emacs doesn't know how to start R. More |> > to the point, I'm unable to run R within Emacs any other way. |> > |> > The usual recipe is to start with emacs -q and then evaluate |> > |> > (package-initialize) |> > (require 'ess-site) |> > |> > in the scratch buffer, then check to see if you can reproduce the bug. |> > If you have ESS installed in a way that it is not in your load-path by |> > default you may have to do something along the lines of |> > |> > (add-to-list 'load-path "/path/to/ESS/lisp/") |> > (load "ess-site") |> > |> > Best, |> > Ista |> > |> > |> > |> > I gather there is a way of applying individual lines of the .emacs |> > files but a bear with a small brain doesn't know how to do that (or |> > where to look in the manual how to do it), |> > |> > It would appear, if it doesn't reproduce, that the problem is |> > somewhere in my .emacs file. That's a hodge-podge of various things |> > I've picked up over the decades so it wouldn't be surprising to find |> > some incompatibilities. |> > |> > Ideas appreciated. |> > |> > |> > On Wed, 11-Apr-2018 at 07:44AM -0400, Ista Zahn wrote: |> > |> > |> I can't reproduce it with the latest ESS from melpa. Can you give |> > |> reproduction steps starting with |> > |> |> > |> emacs -q |> > |> |> > |> ? |> > |> |> > |> --Ista |> > |> |> > |> On Wed, Apr 11, 2018 at 4:58 AM, Patrick Connolly |> > |> wrote: |> > |> > For a long time I used to be able to use |> > |> > |> > |> > ess-dump-object-into-edit-buffer |> > |> > |> > |> > to create a buffer that could be used to edit the designated function |> > |> > from anywhere on the search path to make a local version. |> > |> > |> > |> > Starting at about ess-15.x, only the first 5 or so lines of code is |> > |> > made available which I took to be a bug that would be fixed. However, |> > |> > I was mistaken. I installed ess-17.11 and it's still the same. Being |> > |> > a bear with only a small brain, I can't imagine what use that would be |> > |> > if it's what is intended. |> > |> > |> > |> > Could it be that there is an additional setting that allows all of the |> > |> > function (including comments) to be dumped into that buffer? Perhaps, |> > |> > more difficult to track down, I have something else in my ~/.emacs |> > |> > file that is incompatible. |> > |> > |> > |> > TIA for suggestions. |> > |> > |> > |> > -- |> > |> > |> > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. |> > |> >___Patrick Connolly |> > |> > {~._.~} Great minds discuss ideas |> > |> > _( Y )_
Re: [ESS] ess-dump-object-into-edit-buffer
On Thu, Apr 12, 2018 at 3:56 AM, Patrick Connollywrote: > Thanks for the response, however, if I start Emacs with a '-q' none of > my ~/.emacs file is read, so Emacs doesn't know how to start R. More > to the point, I'm unable to run R within Emacs any other way. The usual recipe is to start with emacs -q and then evaluate (package-initialize) (require 'ess-site) in the scratch buffer, then check to see if you can reproduce the bug. If you have ESS installed in a way that it is not in your load-path by default you may have to do something along the lines of (add-to-list 'load-path "/path/to/ESS/lisp/") (load "ess-site") Best, Ista > > I gather there is a way of applying individual lines of the .emacs > files but a bear with a small brain doesn't know how to do that (or > where to look in the manual how to do it), > > It would appear, if it doesn't reproduce, that the problem is > somewhere in my .emacs file. That's a hodge-podge of various things > I've picked up over the decades so it wouldn't be surprising to find > some incompatibilities. > > Ideas appreciated. > > > On Wed, 11-Apr-2018 at 07:44AM -0400, Ista Zahn wrote: > > |> I can't reproduce it with the latest ESS from melpa. Can you give > |> reproduction steps starting with > |> > |> emacs -q > |> > |> ? > |> > |> --Ista > |> > |> On Wed, Apr 11, 2018 at 4:58 AM, Patrick Connolly > |> wrote: > |> > For a long time I used to be able to use > |> > > |> > ess-dump-object-into-edit-buffer > |> > > |> > to create a buffer that could be used to edit the designated function > |> > from anywhere on the search path to make a local version. > |> > > |> > Starting at about ess-15.x, only the first 5 or so lines of code is > |> > made available which I took to be a bug that would be fixed. However, > |> > I was mistaken. I installed ess-17.11 and it's still the same. Being > |> > a bear with only a small brain, I can't imagine what use that would be > |> > if it's what is intended. > |> > > |> > Could it be that there is an additional setting that allows all of the > |> > function (including comments) to be dumped into that buffer? Perhaps, > |> > more difficult to track down, I have something else in my ~/.emacs > |> > file that is incompatible. > |> > > |> > TIA for suggestions. > |> > > |> > -- > |> > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. > |> >___Patrick Connolly > |> > {~._.~} Great minds discuss ideas > |> > _( Y )_ Average minds discuss events > |> > (:_~*~_:) Small minds discuss people > |> > (_)-(_) . Eleanor Roosevelt > |> > > |> > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. > |> > > |> > __ > |> > ESS-help@r-project.org mailing list > |> > https://stat.ethz.ch/mailman/listinfo/ess-help > > -- > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. >___Patrick Connolly > {~._.~} Great minds discuss ideas > _( Y )_ Average minds discuss events > (:_~*~_:) Small minds discuss people > (_)-(_) . Eleanor Roosevelt > > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ess-dump-object-into-edit-buffer
I think we should adjust the max lines before calling dump(). In the mean time you can do it manually: options(deparse.max.lines = NA) The reason for the change of behaviour is this change in R: https://github.com/wch/r-source/commit/201ddbd16e8f410c469dcd4695471c0bedd65dd5 dput() and dump() should probably set this option to NA themselves. Lionel > On 12 avr. 2018, at 09:56, Patrick Connolly> wrote: > > Thanks for the response, however, if I start Emacs with a '-q' none of > my ~/.emacs file is read, so Emacs doesn't know how to start R. More > to the point, I'm unable to run R within Emacs any other way. > > I gather there is a way of applying individual lines of the .emacs > files but a bear with a small brain doesn't know how to do that (or > where to look in the manual how to do it), > > It would appear, if it doesn't reproduce, that the problem is > somewhere in my .emacs file. That's a hodge-podge of various things > I've picked up over the decades so it wouldn't be surprising to find > some incompatibilities. > > Ideas appreciated. > > > On Wed, 11-Apr-2018 at 07:44AM -0400, Ista Zahn wrote: > > |> I can't reproduce it with the latest ESS from melpa. Can you give > |> reproduction steps starting with > |> > |> emacs -q > |> > |> ? > |> > |> --Ista > |> > |> On Wed, Apr 11, 2018 at 4:58 AM, Patrick Connolly > |> wrote: > |> > For a long time I used to be able to use > |> > > |> > ess-dump-object-into-edit-buffer > |> > > |> > to create a buffer that could be used to edit the designated function > |> > from anywhere on the search path to make a local version. > |> > > |> > Starting at about ess-15.x, only the first 5 or so lines of code is > |> > made available which I took to be a bug that would be fixed. However, > |> > I was mistaken. I installed ess-17.11 and it's still the same. Being > |> > a bear with only a small brain, I can't imagine what use that would be > |> > if it's what is intended. > |> > > |> > Could it be that there is an additional setting that allows all of the > |> > function (including comments) to be dumped into that buffer? Perhaps, > |> > more difficult to track down, I have something else in my ~/.emacs > |> > file that is incompatible. > |> > > |> > TIA for suggestions. > |> > > |> > -- > |> > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. > |> >___Patrick Connolly > |> > {~._.~} Great minds discuss ideas > |> > _( Y )_ Average minds discuss events > |> > (:_~*~_:) Small minds discuss people > |> > (_)-(_) . Eleanor Roosevelt > |> > > |> > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. > |> > > |> > __ > |> > ESS-help@r-project.org mailing list > |> > https://stat.ethz.ch/mailman/listinfo/ess-help > > -- > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. > ___Patrick Connolly > {~._.~} Great minds discuss ideas > _( Y )_Average minds discuss events > (:_~*~_:) Small minds discuss people > (_)-(_) . Eleanor Roosevelt > > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. > > __ > ESS-help@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/ess-help __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ess-dump-object-into-edit-buffer
Thanks for the response, however, if I start Emacs with a '-q' none of my ~/.emacs file is read, so Emacs doesn't know how to start R. More to the point, I'm unable to run R within Emacs any other way. I gather there is a way of applying individual lines of the .emacs files but a bear with a small brain doesn't know how to do that (or where to look in the manual how to do it), It would appear, if it doesn't reproduce, that the problem is somewhere in my .emacs file. That's a hodge-podge of various things I've picked up over the decades so it wouldn't be surprising to find some incompatibilities. Ideas appreciated. On Wed, 11-Apr-2018 at 07:44AM -0400, Ista Zahn wrote: |> I can't reproduce it with the latest ESS from melpa. Can you give |> reproduction steps starting with |> |> emacs -q |> |> ? |> |> --Ista |> |> On Wed, Apr 11, 2018 at 4:58 AM, Patrick Connolly |>wrote: |> > For a long time I used to be able to use |> > |> > ess-dump-object-into-edit-buffer |> > |> > to create a buffer that could be used to edit the designated function |> > from anywhere on the search path to make a local version. |> > |> > Starting at about ess-15.x, only the first 5 or so lines of code is |> > made available which I took to be a bug that would be fixed. However, |> > I was mistaken. I installed ess-17.11 and it's still the same. Being |> > a bear with only a small brain, I can't imagine what use that would be |> > if it's what is intended. |> > |> > Could it be that there is an additional setting that allows all of the |> > function (including comments) to be dumped into that buffer? Perhaps, |> > more difficult to track down, I have something else in my ~/.emacs |> > file that is incompatible. |> > |> > TIA for suggestions. |> > |> > -- |> > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. |> >___Patrick Connolly |> > {~._.~} Great minds discuss ideas |> > _( Y )_ Average minds discuss events |> > (:_~*~_:) Small minds discuss people |> > (_)-(_) . Eleanor Roosevelt |> > |> > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. |> > |> > __ |> > ESS-help@r-project.org mailing list |> > https://stat.ethz.ch/mailman/listinfo/ess-help -- ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. ___Patrick Connolly {~._.~} Great minds discuss ideas _( Y )_ Average minds discuss events (:_~*~_:) Small minds discuss people (_)-(_) . Eleanor Roosevelt ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ess-dump-object-into-edit-buffer
I can't reproduce it with the latest ESS from melpa. Can you give reproduction steps starting with emacs -q ? --Ista On Wed, Apr 11, 2018 at 4:58 AM, Patrick Connollywrote: > For a long time I used to be able to use > > ess-dump-object-into-edit-buffer > > to create a buffer that could be used to edit the designated function > from anywhere on the search path to make a local version. > > Starting at about ess-15.x, only the first 5 or so lines of code is > made available which I took to be a bug that would be fixed. However, > I was mistaken. I installed ess-17.11 and it's still the same. Being > a bear with only a small brain, I can't imagine what use that would be > if it's what is intended. > > Could it be that there is an additional setting that allows all of the > function (including comments) to be dumped into that buffer? Perhaps, > more difficult to track down, I have something else in my ~/.emacs > file that is incompatible. > > TIA for suggestions. > > -- > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. >___Patrick Connolly > {~._.~} Great minds discuss ideas > _( Y )_ Average minds discuss events > (:_~*~_:) Small minds discuss people > (_)-(_) . Eleanor Roosevelt > > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. > > __ > ESS-help@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/ess-help __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help