I've had quite some troubles with this too... I found that renaming the
DESCRIPTION file will do the trick. I choose to rename it to
"locked_DESCRIPTION" and then I can just go and rename it back whenever
I want the features of package mode. Thought it might help someone else
in the future.
>> On Wed, Aug 24 2016 15:49, Tyler Smith wrote:
> The `ess-r-package-auto-activate` toggle isn't working for me. From
> `emacs -Q`, I'm setting up with this script:
> (require 'package)
> (setq package-load-list
> '((ess t)
> (julia-mode t))
> (package-initialize)
> (require
The `ess-r-package-auto-activate` toggle isn't working for me. From
`emacs -Q`, I'm setting up with this script:
(require 'package)
(setq package-load-list
'((ess t)
(julia-mode t))
(package-initialize)
(require 'ess-site)
(setq ess-r-package-auto-activate nil)
And I'm still getting
Hi,
I am working on a package that is currently unloadable (conflicts
between NAMESPACE and current R/ code). Working on this is very
difficult, because I can't convince ESS to treat my code files as
regular files, rather than as part of the package. For example, I can
pass a class definition to
