all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Skip Montanaro <skip.montanaro@gmail.com>
To: Narendra Joshi <narendraj9@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Requiring elisp that comes with Emacs
Date: Mon, 30 Jan 2017 12:50:58 -0600	[thread overview]
Message-ID: <CANc-5Uy9XTb2Ry7UARcHuU=9x4MX=o8D7yJaSiuCGDdMwpo5kQ@mail.gmail.com> (raw)
In-Reply-To: <874m0gv6ba.fsf@gmail.com>

On Mon, Jan 30, 2017 at 10:52 AM, Narendra Joshi <narendraj9@gmail.com>
wrote:

> What happens when we do `require'?


It guarantees the relevant feature is available, generally as a side effect
of loading the named package. I believe the package much "provide" its
name. If not found, an error is raised. Full details can be found here:

https://www.gnu.org/software/emacs/manual/html_node/elisp/Named-Features.html

While under the covers I imagine the implementation is much different, I my
mental model is similar to Python's import statement or C++'s namespace
statement. All three make a series of names available to you, though
require is a global operation, not local to a particular module or
translation unit.

Skip Montanaro


  reply	other threads:[~2017-01-30 18:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 16:52 Requiring elisp that comes with Emacs Narendra Joshi
2017-01-30 18:50 ` Skip Montanaro [this message]
2017-01-31 13:46   ` Narendra Joshi
2017-01-31 14:39     ` Óscar Fuentes
2017-01-31 18:06       ` Skip Montanaro
2017-01-31 20:03         ` Óscar Fuentes
2017-01-31 14:50     ` Skip Montanaro
2017-01-31 20:01       ` Narendra Joshi
2017-01-31 20:40         ` Skip Montanaro
2017-02-01 10:07           ` hector
2017-02-01 15:10           ` Narendra Joshi
2017-02-01 15:53     ` Eric Abrahamsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANc-5Uy9XTb2Ry7UARcHuU=9x4MX=o8D7yJaSiuCGDdMwpo5kQ@mail.gmail.com' \
    --to=skip.montanaro@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=narendraj9@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.