# Resolving a module by its name?

**URL:** https://discourse.julialang.org/t/resolving-a-module-by-its-name/30569
**Category:** General Usage
**Tags:** question
**Created:** [November 1, 2019, 12:50am UTC](https://discourse.julialang.org/t/resolving-a-module-by-its-name/30569 "2019-11-01T00:50:21Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![gcv](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gcv/32/11086_2.png) [@gcv](https://discourse.julialang.org/u/gcv)
#### Post date: [November 1, 2019, 7:38pm UTC](https://discourse.julialang.org/t/resolving-a-module-by-its-name/30569/9 "2019-11-01T19:38:31Z")

</div>

> [@Tamas\_Papp](#):
>
> Can you give some context to your problem?

I’m hacking on a Julia interaction mode for Emacs in the spirit of Common Lisp’s SLIME and Clojure’s CIDER — both of which are superb, (pretty much) best-of-breed interactive programming environments, and which I miss when I use all other languages. Some features — like putting the current top-level form into the running REPL or system image — require evaluating Julia code in the context of the module where it is defined. These modules can be arbitrarily nested. Hence the need to resolve the module and `eval` things.

---

_[View the full topic](https://discourse.julialang.org/t/resolving-a-module-by-its-name/30569)._