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
> (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
>> 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
>> 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
>> 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
>> 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
__
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,
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
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
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
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
>> 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
>> 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
>> 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
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
>
>> 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
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
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
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
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?
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
>> 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
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
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,
>
24 matches
Mail list logo