Re: Recently emacs hangs on startup due to ESS

["Cook, Malcolm" <MEC@stowers.org>]

> On Thu, May 28, 2015 at 5:07 PM, Cook, Malcolm <MEC@stowers.org>
> wrote:
> > I would install latest ess fresh.
> 
> I wondered about that as well, so I tried that prior to posting here.
> Sorry, I should have listed my version, which is now 15.03-1.
> 
> > What version of emacs?  The package manager is a moving target these
> days.
> 
> GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.2)
> (installed via Arch Linux standard package)
> 
> > Try to use the package manager to interactively install the latest
> >
> >> - emacs -Q
> >> following:
> >> http://melpa.org/?utm_source=dlvr.it&utm_medium=twitter#/getting-
> star
> >> ted
> >> - putting this in the buffer
> >
> > (require 'package) ;; You might already have this line (add-to-list
> > 'package-archives
> >              '("melpa" . "http://melpa.org/packages/") t) (when (<
> > emacs-major-version 24)
> >   ;; For important compatibility libraries like cl-lib
> >   (add-to-list 'package-archives '("gnu" .
> > "http://elpa.gnu.org/packages/")))
> > (package-initialize) ;; You might already have this line
> >
> 
> I could do this, though I've sort of decided to steer away from packages and
> just manage things manually via my ~/.elisp/site-lisp folder. Would this have
> an affect? My process was to simply download the .zip of ESS, and unpack to
> ~/.elisp/site-lisp/ess (after deleting the old version). This way, my .emacs can
> continue to point to ~/.elisp/site-lisp/ess/lisp regardless of what version I
> have.
> 
> If manual vs. [m]elpa would make a difference, I suppose I could give the
> above a whirl.
> 

Well, you'll get everything compiled if you use the package manager.  Worth it just for that!  There are other ways to get those files byte-compiled, but the package manager is probably the best.

Also, the package manager can help you discover when updates exist to ALL your eamcs packages.  Worth learning for that.

OTOH, as I said, it has been in flux lately and is still a moving target.

BTW, when did you last update emacs?

And, does (require 'ess-site) ALL BY ITSELF generate your error?

~Malcolm


> 
> Best regards,
> John
> 
> >
> >>
> >> - M-x eval-region on the above lines
> >>
> >
> > Then, M-x list-packages and install it by positioning the cursor on the line
> mentioning the ess package from melpa and typing "I".
> >
> > The type "x" to execute your decision, and confirm with "yes".
> >
> > Now, delete or move/hide your old ess bits and restart emacs.
> >
> > Did it work?
> >
> >> -----Original Message-----
> >> From: emacs-orgmode-bounces+mec=stowers.org@gnu.org
> [mailto:emacs-
> >> orgmode-bounces+mec=stowers.org@gnu.org] On Behalf Of John Hendy
> >> Sent: Thursday, May 28, 2015 2:51 PM
> >> To: emacs-orgmode
> >> Subject: [O] Recently emacs hangs on startup due to ESS
> >>
> >> Over the past couple of weeks, I've been having some issues with
> >> emacs hanging on startup. I usually kill the process, but
> >> inadvertently left it in the background today, noting much later that
> >> it ended up starting. I played with commenting out various parts of
> >> my config until I narrowed things down to the line:
> >>
> >> (require 'ess-site)
> >>
> >> the message buffer displays "enabling speedbar support" for a
> >> reeeaaally long time before it eventually starts up.
> >>
> >> I tried debug-on-signal and eval-expression-debug-on-error... I'm not
> >> sure what is supposed to happen with debug options, but no debug
> >> buffer pops up. The only lines that appear relevant in *Messages* are:
> >>
> >> ad-handle-definition: `ess-indent-command' got redefined
> >> ad-handle-definition: `ess-eval-line-and-step' got redefined
> >>
> >> How might I diagnose this further?. I'm not familiar with chasing
> >> down Emacs issues other than narrowing it down to a config file option.
> >>
> >> I can reproduce this with:
> >> - emacs -Q
> >> - putting this in the buffer
> >>
> >> (add-to-list 'load-path "/path/to/ess/lisp") (require 'ess-site)
> >>
> >> - M-x eval-region on the above two lines
> >>
> >>
> >> Thanks for any suggestions,
> >> John
> >