From: hector <hectorlahoz@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: (require 'filename) doesn't find the file
Date: Fri, 10 Mar 2017 10:17:37 +0100 [thread overview]
Message-ID: <20170310091737.GA3727@workstation> (raw)
The file called BASENAME.el that I want to (require) is in the load-path.
If I add to it the line
(provide 'basename)
it works.
But if I remove the line when I try to compile it says:
syntax.el:26:1:Error: Required feature `basename' was not provided
The part that I think isn't working:
If FEATURE is not a member of the list `features', then the feature
is not loaded; so load the file FILENAME.
Why doesn't it find the file even if it does not contain a (provide)?
I searched for an answer in the list but couldn't find it.
The topic "Requiring elisp that comes with Emacs" comes close
but not to the point.
next reply other threads:[~2017-03-10 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 9:17 hector [this message]
2017-03-10 9:37 ` (require 'filename) doesn't find the file tomas
2017-03-10 10:26 ` hector
2017-03-10 10:46 ` tomas
2017-03-10 9:38 ` hector
2017-03-10 9:55 ` tomas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170310091737.GA3727@workstation \
--to=hectorlahoz@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).