Re: [ESS] R 4.0
I think we could stick to capital `R-`. A few false positives, if any, are probably harmless. Vitalie On Fri, 17 Apr 2020 at 02:18, Tyler Smith via ESS-help wrote: > > I have some TeX-related stuff: > > r-mpost > r-pmpost > r-upmost > > I don't know what they do, I assume they were pulled in as part of > texlive. > > Best, > > Tyler > > > Alex Branham via ESS-help writes: > > > On Thu 16 Apr 2020 at 16:20, Kasper Daniel Hansen via ESS-help > > wrote: > > > >> I have just updated ESS using list-packages. R-4.0 is not found > >> due to the > >> value of ess-r-runners-prefixes. This can of course be > >> customized, but I > >> think it should be changed to include "R-4" > > > > Thanks. I wonder if we should just look for any R-* values. Can > > anyone > > think of instances of an executable named R-* on exec-path that > > *isn't* > > a version of R? > > > > Alex > > > > __ > > ESS-help@r-project.org mailing list > > https://stat.ethz.ch/mailman/listinfo/ess-help > > > -- > Tyler Smith > plantarum.ca > > __ > 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-help Digest, Vol 199, Issue 3
> (add-to-list 'load-path "~/Library/Preferences/Aquamacs Emacs/Packages/lisp/") > (require 'ess-site) > (load "ess-autoloads") ;; need to register Rnw files > (require ‘polymode) ;; version 2.0 now > (require 'poly-markdown) > (require 'poly-noweb) > (require 'poly-R) ;; Just to clarify that none of those requires is really needed unless you install polymode and poly-xyz from the source and want to load from special locations. If installed from melpa, everything (including file associations) should work out of the box. No configuration needed whatsoever. Dependencies will be resolved automatically because elpa packages are already in the path. Vitalie [[alternative HTML version deleted]] __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] Possible to interact with julia-repl?
>> On So, Aug 25 2019 11:07, HaiYing Wang wrote: > Similar to the above situation, I find if I am able to set the value of > "ess-local-process-name" to "julia", then the script file can interact with > julia-repl. However, I don't know how to do this. It seems these variables > cannot be changed by user. It should work. Do you mean that it doesn't work when set from the `ess-julia-mode-hook` or `julia-mode-hook`? Vitalie __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] font color in Sweave file and slowness in inferior mode issues
>> On Mon, Mar 04 2019 23:51, Samuele Carcagno via ESS-help wrote:
> (add-to-list 'auto-mode-alist '("\\.md" . poly-markdown-mode))
> (add-to-list 'auto-mode-alist '("\\.Snw" . poly-noweb+r-mode))
> (add-to-list 'auto-mode-alist '("\\.Rnw" . poly-noweb+r-mode))
> (add-to-list 'auto-mode-alist '("\\.Rmd" . poly-markdown+r-mode))
> I suppose that's all that was needed
None of the above is needed with the recent polymode. Just install poly-R from
MELPA and that's it; all of the above associations are auto-loaded.
Vitalie
__
ESS-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ESS+Polymode Questions
>> On Thu, Mar 07 2019 12:17, Marc Schwartz via ESS-help wrote: >>> >>> that defines the boundary of an R chunk is bolded in black instead of red. I >>> Googled for polymode colors but did not see anything obvious, so was >>> wondering if someone can point me to the fontlock settings for the above to >>> change it from black to red. Red stands out better for my aging eyes... >> >> Usually M-x describe-face defaults to the face under point, perhaps >> that's what you need? > It just shows the default 'bold', not a specific font-lock face. There is no global customization entry for this as yet. For now you can alter the default value of the class: (with-eval-after-load "polymode" (oset-default 'pm-inner-chunkmode :head-adjust-face font-lock-warning-face)) Or if you with to customize specific innermodes: (oset pm-inner/noweb :head-adjust-face font-lock-string-face) Vitalie __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] disable console help when "pausing"
>> On Wed, Feb 27 2019 11:29, clark richards via ESS-help wrote: > (setq ess-use-company t) This one is not needed as it's the default. There are a few recommendations on the Emacs Wiki: https://www.emacswiki.org/emacs/ESS-company Vitalie __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] Problem with R help buffers
Hi Henric, This is most surely related to our recent migration to emacs standard display-buffer mechanism. I opened a new issue https://github.com/emacs-ess/ESS/issues/826 Please follow there for a resolution. Vitalie >> On Wed, Jan 23 2019 14:20, Henric Winell via ESS-help wrote: > Hi, > There's something strange going on with the R help buffers. I'm using the > latest ess-20190122.2108 from melpa, but it's not particular to that version: > I want each help buffer to appear in its own separate frame, and have > '(ess-help-own-frame t) > '(ess-help-reuse-window nil) > in my .emacs. Now, pressing, say, '?lm' in an R buffer opens up the help page > in a separate frame as it should. However, using 'l' to execute the code in > the > 'Examples:' section results in the help frame being split up with the help > buffer on top and the R buffer below. Then, pressing 'q' or 'k' should bury or > remove the help frame, respectively, but it's still visible and has the help > buffer on top replaced by the R buffer. > Henric Winell > __ > 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] Emacs hangs when starting R via -x R
Do you customize your R prompt by any chance? Can you start without your ESS customization? If you do M-x toggle-debug-on-error and start R, what do you see on C-g? Vitalie >> On Mon, Jan 28 2019 12:10, Kjetil brinchmann Halvorsen via ESS-help wrote: > I have no way to know if this is a debian, emacs or ess problem. But I can > use R otherwise than via emacs and ess. > I open a buffer with a file "something.R". In the status line I have >U:--- (...) (ESS[R] [none] hl-p ElDoc) > When starting an R process with R > a new frame opens, R starts (I see the welcome message) and then emacs > hangs. > This have been the state now for at least a week. I am running Debian > testing updated. > Any ideas? (And would this rather belong on r-debian list?) > Kjetil > [[alternative HTML version deleted]] > __ > 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] R Error splits code frame
Could you please add an issue to github with your frame configuration? I also see some not-so nice dynamics with R buffers recently. We need to discuss this in a bit more detail on the issue tracker. Vitalie >> On Wed, Jan 16 2019 12:01, Johannes Aengenheyster via ESS-help wrote: > Dear all, > For some months now, I basically have the exact same problem as here: > https://grokbase.com/t/r/ess-help/1319gq8w1m/ess-error-message-in-r-now-splitting-frame. > I > have one frame with an R process, and one (or more) frames with R code. As > soon > as R produces an error, the code frame gets split in half and the R process is > shown in the new window. Since I already have a frame with a R process, I do > not > want this to happen. Anybody have an idea what to do? (I'm using emacs 26.1.50 > on ubuntu 16.04 with ESS 18.10.3) Thanks in advance! > __ > 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] Trouble evaluating in namespace
You cannot evaluate your input line by line inside a package. The entire function should be sent at once. Use C-c C-c instead. The current doc string of `ess-eval-region-or-line-visibly-and-step` says: Note that when inside a package and namespaced evaluation is in place (see ‘ess-r-set-evaluation-env’) evaluation of multiline input will fail. >> On Thu, Dec 06 2018 16:07, Kevin Wright via ESS-help wrote: > (ess-inject-source nil) Not the best idea. At least for functions you would like to have source references on errors. There is really no benefits at all for changing the default to nil. Vitalie __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] eldoc in Rmd files
You have an outdated polymode
polymode$ git show 0340f5e7e55235832e
commit 0340f5e7e55235832e59673f027cc79a23cbdcd6
Author: Vitalie Spinu
Date: Tue Mar 7 12:22:42 2017 +0100
Polymode has been rewritten and R functionality lives in a separate
package. Just install `poly-R` from melpa and remove *all* old polymode
configuration from your .emacs.
Vitalie
>> On Sat, Nov 10 2018 10:54, Leha, Andreas via ESS-help wrote:
> Hi all,
> I recently upgraded both emacs and ess. One of those broke eldoc
> functionality in Rmd files, which worked fine previously.
> I can reproduce with `emacs -Q`.
> To reproduce this, use this test.Rmd file:
> ---
> title: Test
> ---
> ```{r testblock, include = FALSE}
> rnorm
> ```
> - move the point to the source block
> - type C-c C-v to update the references
> - type the opening '(' after 'rnorm'
> Now, I would expect the eldoc message in the echo buffer, as it appears
> in ordinary R files.
> This is a major limitation for my workflow. Can I fix that somehow?
> Thanks in advance!
> Regards,
> Andreas
> PS:
> Here is my setup:
> - linux (debian buster)
> - Emacs 26.1.50
> - ess-version: 18.10.2
> - polymode (0340f5e7e55235832e59673f027cc79a23cbdcd6)
> - markdown-mode, version 2.4-dev
> PPS:
> And here is my minimal init.el:
> ;; ess
> (add-to-list 'load-path "~/local/emacs/ess/lisp")
> ;;(load "~/local/emacs/ess/lisp/ess-site.el")
> (require 'ess-site)
> ;; markdown mode
> (setq load-path
> (append '("~/local/emacs/markdown-mode/")
> load-path))
> (autoload 'markdown-mode "markdown-mode"
>"Major mode for editing Markdown files" t)
> ;;(add-to-list 'auto-mode-alist '("\\.text\\'" . markdown-mode))
> (add-to-list 'auto-mode-alist '("\\.markdown\\'" . markdown-mode))
> (add-to-list 'auto-mode-alist '("\\.md\\'" . markdown-mode))
> ;; polymode
> (setq load-path
> (append '("~/local/emacs/polymode/"
> "~/local/emacs/polymode/modes")
> load-path))
> (require 'poly-R)
> (require 'poly-markdown)
> ;;; R modes
> (add-to-list 'auto-mode-alist '("\\.Snw" . poly-noweb+r-mode))
> (add-to-list 'auto-mode-alist '("\\.Rnw" . poly-noweb+r-mode))
> (add-to-list 'auto-mode-alist '("\\.Rmd" . poly-markdown+r-mode))
> __
> 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 R code evaluation in package
>> On Fri, Nov 09 2018 09:38, Cyrus Harmon via ESS-help wrote: > I'm not sure if this is a polymode or an ESS problem It's on the ESS side. There are two things, package mode (devtools commands) is activated in specified sub-directories only (see ess-r-package-dirs), but name-space evaluation is activated only within ./R sub-directory. I think this is the right behavior and your use case is non-standard. It's very unlikely that from a Rmd file you would need to evaluate code in the namespace. > but is there someway to specify the pkg in which ESS should be evaluating > code? Yes, with C-c C-t C-s you can either disable or activate namespaced evaluation into any of the currently loaded packages. Vitalie __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ESS R code evaluation in package
>> On Thu, Nov 08 2018 15:15, Cyrus Harmon via ESS-help wrote: > I naively assumed that i could just C-c C-r the source for an installed > function and I would get the new version, at least for the current R > session. This is how it should work. I do devtools::load_all and devtools::install all the time and I haven't noticed unusual behavior. If an object is already in the package it should be replaced. The sealed issue applies only to *new* objects. If you have an example of when the existing object is not re-assigned, then please open a github issue for that. Vitalie __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ESS R code evaluation in package
>> On Tue, Nov 06 2018 16:53, Cyrus Harmon via ESS-help wrote:
> 1. How might I compile 'moose <- function () { “bar” }’ from Emacs/ESS and
> have moose show up in my package?
> 2. If it isn’t going into my package now, where is it going?
There are essentially 3 cases:
1. `moose` is public (exported) function in your package. This means it is
present in both namespace and package environments when the package is loaded.
In this case, when you eval moose <- function() ... it goes into both package
environment and namespace environment of the package.
2. `moose` is not exported. This means it is in your namespace but not in the
package environment. And ls("package:foo") wont show it .
In this case when you eval `moose` it replaces the old version of `moose` in
the namespace. You can see it with ls(asNamespace("foo"))
3. Final case which (seems to be of main interest to you) when `moose` is a
new function. Then, due to the fact that R namepsaces are sealed for new
objects ESS has to do some cheating. It basically inserts a new environment
between package namespace env and its parent and adds all new objects to that
environment. You should get NEW[moose] message in the minibuffer.
With this arrangement all your code will work as if that function exists in
the actual package environment, but you won't be able to see that object with
ls.
> 3. If I can’t do this is there some easy way to build an reinstall an
> existing R
> library without having to call me R process and restart every time I want to
> make a simple change to a library function (this is where I find myself now).
Namespaced evaluation should work for R code as described above. If not, it's a
bug.
Alternatively you can use devtools integration. See C-c C-w map for what is
available. Particularly load-package with [C-c C-w l] or run complete re-install
and reload with (C-c C-w i). Depending on your version of ESS you might need the
dev version of devtools and friends to take the full advantage of the system.
Vitalie
__
ESS-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] how to start debugging R with ess-tracebug
You can also just put a breakpoint (C-c C-t b) and re-evaluate the code. Those breakpoints are just browser() under the hood. Vitalie >> On Sun, Oct 28 2018 20:51, Jeremie Juste via ESS-help wrote: > Hello, > C-c C-t d runs the command ess-debug-flag-for-debugging, which is an > interactive compiled Lisp function in ‘ess-tracebug.el’. > It is bound to C-c C-t d, C-c C-t C-d, > . > (ess-debug-flag-for-debugging) > Set the debugging flag on a function. > Ask the user for a function and if it turns to be generic, ask > for signature and trace it with browser tracer. > HTH, > Jeremie > __ > 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 18.10-1 patch released
>> On Fri, Oct 26 2018 08:33, Alex Branham wrote: > I'd say stick with e.g. 18.10.1, 18.10.2. Ok. Let's do that. __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] flymake + lintr
Most of the linters are disabled by default because they are controversial,
buggy or interfere with how emacs users normally do things. See
ess-r-flymake-linters for how to change that.
I think project local lintr configuration should be taking effect with new
version of lintr, but I am not sure. Alex knows more about that.
Vitalie
>> On Thu, Oct 25 2018 12:24, Kevin Wright via ESS-help wrote:
> I'm not seeing any effects from flymake. I see "Flymake" in the modeline
> and I can click on Flymake, then Check now. Nothing seems to happen.
> I set ess-r-flymake-linters to be the string "lintr::default_linters".
> My setup is fairly current:
> Emacs 27.0.50
> lintr* 1.0.2.9000 2018-10-25 Github (jimhester/lintr@4ade1fc)
> ESS 18.10-1
> I CAN use lint() in an R session:
> R> lint("a=1+1\n")
> :1:2: style: Use <-, not =, for assignment.
> a=1+1
> ^
> :1:2: style: Put spaces around all infix operators.
> a=1+1
> ~^~
> :1:4: style: Put spaces around all infix operators.
> a=1+1
> ~^~
> Anybody have ideas for diagnosing what the problem is?
> Kevin Wright
__
ESS-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ESS 18.10-1 patch released
Our git tags are not signed right? At least I don't see that on GitHub interface. I have manually changed the tag to v18.10.1. Should propagate soon. >> On Thu, Oct 25 2018 17:53, Alex Branham wrote: > This is yet another consequence of ess not being package.el-friendly: There is a good reason of having dashes in our mini version number because it refers to non-calendar updates. I would say it's more of Emacs/package.el issue that they don't recognize such a possibility. What shall we do about it? Shall we stick with mini . from now on or have two version tags? Vitalie __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] re-mapping C-RET in 18.10, avoiding conflict with CUA mode
Hi Paul, Ess-mode.el changed to ess.el but we are still discussing the change. For now just replace "ess-mode" with "ess" and it should be fine. The change to *-visibility-* is needed. In the future release both ess-mode and ess will work. Vitalie >> On Wed, Oct 24 2018 14:58, Paul Johnson via ESS-help wrote: > I'm running Ubuntu-18.10 and the new packaging for elpa-ess provides > ESS 18.10. I still like CUA mode rectangles and so I want to remap > C-RET to S-RET. > 5 years ago Vitalie S told me how to do that. The stanza in init.el was: > ;; Change shortcut "run this line" to use Shift-Return > ;; Suggested by Vitalie Spinu 2013-09-30 to co-exist with Windows Emacs > (eval-after-load "ess-mode" > '(progn >(define-key ess-mode-map [(control return)] nil) >(define-key ess-mode-map [(shift return)] > 'ess-eval-region-or-line-and-step)) > ) > In Ess 18.10-1 this no longer works, I thought I'd fix by revising: > (eval-after-load "ess-mode" > '(progn >(define-key ess-mode-map [(control return)] nil) >(define-key ess-mode-map [(shift return)] > 'ess-eval-region-or-line-visibly-and-step)) > ) > But it does not help. > Can you advise me? __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] ESS 18.10-1 patch released
Do you mean MELPA stable? I do see a git tag 18.10-1 but it's probably not
recognized by MELPA. We need 18.10.1 instead.
Vitalie
>> On Wed, Oct 24 2018 12:26, William McCoy via ESS-help wrote:
> This newest release, ESS 18.10-1, does not yet appear on MELPA yet. Is it on
> its way there?
> On 10/23/18 3:37 PM, Martin Maechler via ESS-help wrote:
>> The ESS 18.10 release (of 3 days ago) had shown some small but
>> obnoxious problems which have been fixed now, and hence we have
>> created a patch release (to 18.10), 18.10-1 which should use
>> *instead* of 18.10.
>>
>> Download from "Downloads" on https://ess.r-project.org/ or also
>> directly at https://stat.ethz.ch/ESS/downloads/ess/?C=M;O=D>
>> -
>>
>> Relatedly, I'm happy to note explicitly that the ESS
>> core team has a new active and very competent member,
>> J. Alexander (Alex) Branham.
>>
>> He's been actively contributing already starting as early as
>> March 2017, and has been formally and successfully invited to
>> join the ESS core on Sep 6, 2018.
>>
>> We're all happy and grateful to be to have him on board!
>>
>> -
>>
>> The only new entry in the 'new features' list is
>>
>> Changes and New Features in 18.10-1:
>>
>> * New functions 'ess-eval-line-visibly-and-step' ('C-c C-n' and
>> 'ess-eval-region-or-line-visibly-and-step' ('C-RET') which behave
>> as the old versions of 'ess-eval-line-and-step' and
>> 'ess-eval-region-or-line-and-step'.
>>
>> In the name of the ESS core team,
>> Martin Maechler
>>
>>
>>> Martin Maechler via ESS-help
>>> on Sat, 20 Oct 2018 22:29:21 +0200 writes:
>>
>>> Dear ESS Users
>>> it's a pleasure to announce the release of
>>>
>>> ESS 18.10 (2018 October)
>>>
>>> of a few minutes ago in the name of the ESS core team.
>>>
>>> There have been many changes and improvements since the last
>>> official release 17.11 (in last November)
>>>
>>> For the complete list of (documented) new features and bug
>>> fixes, read the following (beginning of file 'ANNOUNCE') to the end.
>>>
>>> In the name of the ESS core team, with thanks to all helpers,
>>> notably by github pull requests,
>>>
>>> Martin Maechler, ETH Zurich
>>>
>>>
>>>
>>> 1 ANNOUNCING ESS
>>>
>>>
>>> The ESS Developers proudly announce the release of ESS 18.10
>>>
>>> Emacs Speaks Statistics (ESS) provides an intelligent, consistent
>>> interface between the user and the software. ESS interfaces with
>>> R/S-PLUS, SAS, BUGS/JAGS, Stata and other statistical analysis packages
>>> under the UNIX, GNU Linux, Microsoft Windows, macOS and other operating
>>> systems. ESS is a package for the GNU Emacs and XEmacs text editors
>>> whose features ESS uses to streamline the creation and use of
>>> statistical software. ESS knows the syntax and grammar of statistical
>>> analysis packages and provides consistent display and editing features
>>> based on that knowledge. ESS assists in interactive and batch execution
>>> of statements written in these statistical analysis languages.
>>>
>>> ESS is freely available under the GNU General Public License (GPL).
>>> Please read the file COPYING which comes with the distribution, for more
>>> information about the license. For more detailed information, please
>>> read the README files that come with ESS.
>>>
>>> 1.1 Getting the Latest Version
>>> ==
>>>
>>> ESS supports GNU Emacs versions 24.3 and newer.
>>>
>>> ESS is most likely to work with current/recent versions of the
>>> following statistical packages: R/S-PLUS, SAS, Stata, OpenBUGS and JAGS.
>>>
>>> To build the PDF documentation, you will need a version of TeX Live
>>> or texinfo that includes texi2dvi.
>>>
>>> There are two main methods used for installing ESS. You may install
>>> from a third-party repository or from source code. Once you install it,
>>> you must also activate or load ESS in each Emacs session, though
>>> installation from a third-party repository likely takes care of that for
>>> you. See *note Activating and Loading ESS:: for more details.
>>>
>>> 1.2 Installing from a third-party repository
>>>
>>>
>>> ESS is packaged by many third party repositories. Many GNU/Linux
>>> distributions package it, usually with the name "emacs-ess" or similar.
>>>
>>> ESS is also available through Milkypostman’s Emacs Lisp Package
>>> Archive (MELPA), a popular repository for Emacs packages. Instructions
>>> on how to do so are found on MELPA's website (https://melpa.org/).>> MELPA
>>> also hosts MELPA-stable with stable ESS builds. You may choose
>>> between MELPA with the latest and greatest features (and bugs) or
>>> MELPA-stable, which may lag a bit behind but should be more stable.
>>>
>>> After installing, users should make sure ESS is activated or loaded
>>> in each Emacs session. See *note Activating and Loading ESS::.
>>> Depending on install method, this
Re: [ESS] Hang when opening remote session
Do you have a proper ssh remote to test this on? Could this be docker specific? >> On ma, jul 23 2018 05:58, Gammel Holte via ESS-help wrote: >> >> Just a shot in the dark, but does /ssh:root@localhost#6000:/root/.Rhistory >> exist and you have read/write permission? >> > Apologies for the late reply. Yes, it does exist and I have rw permissions. > Anything else I can do to debug this issue? > Thanks. > [[alternative HTML version deleted]] > __ > 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] Indent for R's 'switch'
>> On Fri, Jun 22 2018 11:06, Marius Hofert via ESS-help wrote: > my_variable_value <- switch(...) You can always do: my_variable_value <- switch(...) Vitalie __ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
Re: [ESS] looking for definitions of R functions
In addition to xref and etags I use M-o for imenu-anywhere. It works within all buffers of the same mode and buffers within same project (if you have projectile installed). The benefit is that you don't need any fancy lockup functionality or TAGS. It will work straight away. The drawback is that you need to open the buffers first. Vitalie >> On Fri, Jun 22 2018 10:15, Stephen Eglen via ESS-help wrote: > Hello, > what are people using (if anything) to find declarations of R functions > within Emacs buffers? e.g. when point is on the name of a function, you > hit a keybinding to look up the definiton of that function. > I just had some success with using dumb-jump.el > https://github.com/jacktasia/dumb-jump -- it has a notion of a project > folder within which it will search for R function definitions > dynamically using a grep variant. (It doesn't always work -- e.g. I > can't yet get it to fund hidden functions that begin with a period, > since I think it does not recognise the . as beginning of a word.) > But I'm just wondering if others had success with other packages? We > mention TAGS files in our ESS documentation, and rtags. > Stephen > __ > 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 problem
Hi Rob,
Have you changed prompt on the R side (in opts)? Try running R without any
personal configuration. If it "just started happening" it's unlikely ESS
problem. Evaluation hasn't been touched in a while here.
Vitalie
>> On Tue, Jun 12 2018 12:00, Rob Dunne wrote:
> Hi Ess- help,
> when I highlight something like
> F <- 4 +5 +
> 6
> and send it to a running R process -- the process just hangs. But
> F <- 4 +5 +6
> caused no problems.
> This has just started happening. I don't think I have changed anything.
> I realize it is not much to go on. How can I get better information about
> the problem.
> The output from ess-submit-bug-report and sessionInfo() is attached.
> Bye
> R
> ]*function) (ess-font-lock-keywords quote ess-R-font-lock-keywords)
> (ess-font-lock-defaults ess--extract-default-fl-keywords
> ess-R-font-lock-keywords) (font-lock-defaults quote (ess-font-lock-defaults
> nil nil ((46 . w) (95 . w)
> (ess-setq-vars-LOCAL): language=S, dialect=R, buf=nil, comint..echoes=t,
> comint..sender=comint-simple-send
> Finished setting up ESS-mode.
> (n-i-m-l: 1)(ess-setq-vars-LOCAL): language=S, dialect=R, buf=nil,
> comint..echoes=t, comint..sender=comint-simple-send
> (ess-mode-1): ess-language=S, ess-dialect=R buf=script1.Rnw
> (ess-mode-1.5): alist=((inferior-ess-reload-function quote
> inferior-ess-reload:R) (ess-quit-function quote ess-quit:R)
> (ess-send-region-function quote ess-send-region:R) (ess-load-file-function
> quote ess-load-file:R) (ess-build-load-command-function quote
> ess-build-load-command:R) (ess-build-eval-command-function quote
> ess-build-eval-command:R) (ess-local-customize-alist quote
> ess-r-customize-alist) (ess-dialect . R) (ess-suffix . R) (ess-ac-sources .
> ess-r-ac-sources) (ess-company-backends . ess-r-company-backends)
> (ess-build-tags-command . ess-r-build-tags-command) (ess-traceback-command
> . ess-r-traceback-command) (ess-call-stack-command .
> ess-r-call-stack-command) (ess-mode-completion-syntax-table .
> ess-r-completion-syntax-table) (ess-build-eval-message-function function
> ess-r-build-eval-message) (ess-format-eval-command-function function
> ess-r-format-eval-command) (ess-format-load-command-function function
> ess-r-format-load-command) (ess-send-region-function function
> ess-r-send-region) (ess-load-file-function function ess-r-load-file)
> (ess-make-source-refd-command-function function
> ess-r-make-source-refd-command) (ess-format-eval-message-function function
> ess-r-format-eval-message) (ess-install-library-function function
> ess-r-install-library) (ess-eldoc-function function ess-r-eldoc-function)
> (ess-help-web-search-command function ess-r-sos)
> (ess-build-help-command-function function ess-r-build-help-command)
> (ess-dump-filename-template . ess-r-dump-filename-template)
> (ess-mode-editing-alist . ess-r-editing-alist) (ess-change-sp-regexp .
> ess-r-change-sp-regexp) (ess-help-sec-regex . ess-help-r-sec-regex)
> (ess-help-sec-keys-alist . ess-help-r-sec-keys-alist) (ess-loop-timeout .
> ess-r-loop-timeout) (ess-function-pattern . ess-r-function-pattern)
> (ess-object-name-db-file . ess-r-namedb.el) (ess-smart-operators .
> ess-r-smart-operators) (inferior-ess-program . inferior-ess-r-program-name)
> (inferior-ess-objects-command . inferior-ess-r-objects-command)
> (inferior-ess-font-lock-keywords quote inferior-ess-r-font-lock-keywords)
> (inferior-ess-search-list-command . search()
> ) (inferior-ess-help-command . inferior-ess-r-help-command)
> (inferior-ess-help-filetype) (inferior-ess-exit-command . q())
> (inferior-ess-exit-prompt . Save workspace image? [y/n/c]: )
> (inferior-ess-start-file) (inferior-ess-start-args . )
> (ess-error-regexp-alist . ess-r-error-regexp-alist)
> (ess-describe-object-at-point-commands quote
> ess-r-describe-object-at-point-commands) (ess-STERM . iESS) (ess-editor .
> ess-r-editor) (ess-pager . ess-r-pager) (ess-mode-syntax-table .
> ess-r-syntax-table) (font-lock-syntactic-face-function function
> ess-r-font-lock-syntactic-face-function) (prettify-symbols-alist quote ((<-
> . 8592) (<<- . 8606) (-> . 8594) (->> . 8608))) (ess-language . S)
> (inferior-ess-exit-command . q()
> ) (inferior-ess-language-start eval inferior-S-language-start)
> (comint-use-prompt-regexp . t) (comint-process-echoes . t)
> (inferior-ess-primary-prompt . > ) (inferior-ess-secondary-prompt . + )
> (comment-start . #) (ess-imenu-generic-expression .
> ess-imenu-S-generic-expression) (comment-add . 1) (comment-start-skip . #+
> *) (comment-use-syntax . t) (comment-column . 40) (ess-no-skip-regexp
> concat ^ *@\| (default-value 'ess-no-skip-regexp)) (inferior-ess-prompt .
> inferior-S-prompt) (ess-get-help-topics-function function
> ess-s-get-help-topics-function) (ess-getwd-command . getwd()
> ) (ess-setwd-command . setwd('%s')
> ) (ess-funargs-command . .ess_funargs("%s")
> ) (fill-nobreak-predicate quote ess-inside-string-p)
> (normal-auto-fill-function quote ess-do-auto-fill)
>
