[ESS] Error starting R

[Jeremie Juste]

Hello,

Be sure to CC ess-help using r-project.org in your reply as your mail can help
others as well. You might find better support in this way too.

I updated by ess to your version : ess-version: 18.10 and could load
R without difficulty.

I'm using GNU Emacs 25.3.3 (x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
of 2018-08-22 though. So updating emacs might help but it might be
costly depending on your operating system.

Another way around your problem could be trying to switch back to
previous versions of ESS.

If you use melpa and you didn't delete the previous versions of ess, deleting the most
recent ones in your directory and reloading emacs should do the job.


Another quick way to see if the problem comes from your .init file is to
start emacs without loading it.

> emacs -Q (from the terminal)

then in the scratch execute 

(add-to-list 'load-path "path to ess site.el ")
;; mine 
(add-to-list 'load-path "/home/djj/.emacs.d/elpa/ess-20181003.755/")
(require 'ess-site)

I got some errors from julia mode but R works fine.

Hope it helps

Jeremie





Neil Shephard <nshephard using gmail.com> writes:

> Hi,
>
> Thanks for taking the time to reply.
>
> On Wed, 3 Oct 2018 at 12:26, Jeremie Juste <jeremiejuste using gmail.com> wrote:
>
>>
>> Can you specify the ess version you are using?
>>
>
> Yep its...
>
>> I'm using Emacs 25.3.1 with ESS installed from ELPA (20181003.755).
>
> I started seeing the error last week when I updated packages from MELPA and
> before posting to ESS-ehlp updated ESS today to check the error still
> persisted which it does.  Looks like it was built against Git commit d94388.
>
>>
>> I would suggest disabling global-font-lock-mode (M-x
>> global-font-lock-mode) before launching R to see if it works.
>> It is not a fix but just a way to investingate where the problem might
>> be.
>>
>
> Gave this a try and neither *Messages* nor the *Backtrace* give any more
> information...
>
> *Messages*
>     Global Font-Lock mode disabled
>     autoload-do-load: Wrong type argument: consp, nil
>     Debug on Error enabled globally
>     Entering debugger...
>
> *Backtrace*
>     Debugger entered--Lisp error: (wrong-type-argument consp nil)
>
> byte-code("\301\30\"\303\241\210\301\30\"\305\241\210\306\307\300\"\207"
> [ess-r-customize-alist assoc ess-font-lock-keywords (quote
> ess-R-font-lock-keywords) inferior-ess-font-lock-keywords (quote
> inferior-ess-r-font-lock-keywords) defalias R-customize-alist] 3)
>       autoload-do-load((autoload "ess-r-mode" "Call 'R', the 'GNU S' system
> from the R Foundation.\nOptional prefix (\\[universal-argument]) allows to
> set command line arguments, such as\n--vsize.  This should be OS
> agnostic.\nIf you have certain command line arguments that should always be
> passed\nto R, put them in the variable `inferior-R-args'.\n\nSTART-ARGS can
> be a string representing an argument, a list of\nsuch strings, or any other
> non-nil value.  In the latter case, you\nwill be prompted to enter
> arguments interactively.\n\n(fn &optional START-ARGS)" t nil) R)
>       command-execute(R record)
>       execute-extended-command(nil "R" "R")
>       funcall-interactively(execute-extended-command nil "R" "R")
>       call-interactively(execute-extended-command nil nil)
>       command-execute(execute-extended-command)
>
> I read through the comments in issue 596 and followed the suggestion of
> deleting the MELPA installed ESS and disabling loading of any ESS then
> reinstalling (see comment at
> https://github.com/emacs-ess/ESS/issues/596#issuecomment-402053269) but
> that didn't work either.
>
> If there is anything else I can try or any more information please let me
> know.
>
> Thanks for your time,
>
> Neil
>
> --
> *Natural selection is a mechanism for generating an exceedingly high **degree
> of improbability.* - R.A. Fisher
>
> *Ignorance more frequently begets confidence than does knowledge* - Charles
> Darwin
>
> PGP Public : https://pgp.mit.edu/pks/lookup?op=get&search=0x0E7ECE9C10D7B4A0