From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.help Subject: Re: Requiring elisp that comes with Emacs Date: Tue, 31 Jan 2017 21:03:45 +0100 Message-ID: <878tpr9eu6.fsf@wanadoo.es> References: <874m0gv6ba.fsf@gmail.com> <87k29bl4v0.fsf@gmail.com> <87d1f39tv4.fsf@wanadoo.es> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1485895652 16750 195.159.176.226 (31 Jan 2017 20:47:32 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2017 20:47:32 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jan 31 21:47:28 2017 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cYfKp-00047S-ME for geh-help-gnu-emacs@m.gmane.org; Tue, 31 Jan 2017 21:47:27 +0100 Original-Received: from localhost ([::1]:41132 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYfKv-0004tM-3O for geh-help-gnu-emacs@m.gmane.org; Tue, 31 Jan 2017 15:47:33 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50217) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYeej-00059I-SX for help-gnu-emacs@gnu.org; Tue, 31 Jan 2017 15:03:58 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cYeeg-0000Bl-Qq for help-gnu-emacs@gnu.org; Tue, 31 Jan 2017 15:03:57 -0500 Original-Received: from [195.159.176.226] (port=43672 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cYeeg-0000Bf-L6 for help-gnu-emacs@gnu.org; Tue, 31 Jan 2017 15:03:54 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cYeeY-0000Zf-TE for help-gnu-emacs@gnu.org; Tue, 31 Jan 2017 21:03:46 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 25 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:i7JTaMBNguZDjkAcXy5pnFFuVP8= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-Mailman-Approved-At: Tue, 31 Jan 2017 15:46:31 -0500 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:112221 Archived-At: Skip Montanaro writes: > On Tue, Jan 31, 2017 at 8:39 AM, Óscar Fuentes wrote: > >> Type >> >> C-h f require [ENTER] >> >> A *Help* buffer will popup with the docstring for `require'. There it is >> explained that the file for the require-d package is inferred from the >> package name. >> > > Thanks. When I said "this is all speculation", I meant how it works under > the covers (how it compares semantically to Python's import statement or > C++'s namespace statement), not how it locates a file to load. I realize > that require uses the argument symbol name as the basename of the source > file. I don't know about Python, but Elisp `require' is totally unrelated to C++'s namespace statement. Semantically, it is loosely related to the #include preprocessor directive, although not quite the same. IMHO it is wrong to learn a language thinking on supposedly similar conceps on other languages. It just creates confusion.