And here's all the code from my init.el related to development in Julia
;; auto-complete
(ac-
config-default)
;; ido
(ido-
mode)
;; Julia
(load "~/.emacs.d/ESS/lisp/ess-site")
(setq inferior-julia-program-name "julia")
(add-hook 'julia-mode-hook
'(lambda ()
(local-set-key (kbd "C-d")
'ess-eval-line-and-step)
(local-set-key (kbd "C-c C-c") 'ess-load-file)))
(setq ess-use-auto-complete t)
(setq ess-tab-complete-in-script t)
On Tuesday, September 22, 2015 at 4:16:33 PM UTC+3, Andrei Zh wrote:
>
>
>
>> I'd be grateful to hear from other emacs users regarding your workflows
>> for Julia development, e.g. if you want to write a Julia package what emacs
>> packages, setup and workflow help you to be the most productive?
>>
>>
> I use ESS + autocomplete + few keybindings (I'll post exact .init.el later
> when I get home), but there's one important thing about code organization
> that I worked out with time and now find very convenient.
>
> When developing a module, I put all the code in a file called "core.jl"
> (or other files included into "core.jl"), and then in "MyModule.jl" simply
> write:
>
> module MyModule
> export ...
>
>
> include("core.jl")
>
>
> end
>
>
>
> This allows to open "core.jl" in Emacs, load the file (C-c C-c) and work
> like "from inside" the module, i.e. reload any function, keep variables,
> types, etc. without the need to reload the whole module and thus reset all
> variables.
>
