From: Stephen Berman <stephen.berman@gmx.net>
To: fatiparty--- via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Cc: fatiparty@tutanota.com
Subject: Re: File for minor mode not found
Date: Sun, 09 Jan 2022 17:01:28 +0100 [thread overview]
Message-ID: <874k6cgap3.fsf@gmx.net> (raw)
In-Reply-To: <MszWKRB--7-2@tutanota.com> (fatiparty's message of "Sun, 9 Jan 2022 16:46:51 +0100 (CET)")
On Sun, 9 Jan 2022 16:46:51 +0100 (CET) fatiparty--- via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> Jan 9, 2022, 15:12 by stephen.berman@gmx.net:
>
>> On Sun, 9 Jan 2022 15:43:42 +0100 (CET) fatiparty--- via Users list for the
>> GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
[...]
>>> It does not exist. The file is named daph-ideograms.el but I am using
>>> (provide 'daph) at the end of the file. And using (require 'daph) after
>>> setting the load-path in another file.
>>>
>>
>> That should be (require 'daph "daph-ideograms"), see `C-h f require':.
>>
>> require is a built-in function in ‘C source code’.
>>
>> (require FEATURE &optional FILENAME NOERROR)
>>
>> If feature FEATURE is not loaded, load it from FILENAME.
>> If FEATURE is not a member of the list ‘features’, then the feature is
>> not loaded; so load the file FILENAME.
>>
>> If FILENAME is omitted, the printname of FEATURE is used as the file
>> name, and ‘load’ will try to load this name appended with the suffix
>> ‘.elc’, ‘.el’, or the system-dependent suffix for dynamic module
>> files, in that order.
>>
>> Steve Berman
>>
>
> Thanks Steve. One thing that has been difficult to see, is the
> relationship between (provide 'daph) and (require 'daph). Following
> your suggestion, I need to have (require 'daph "daph-ideograms"). Are
> there any implications for the (provide 'daph) part?
No, that's fine. As its doc string says, `provide' just "[a]nnounce[s]
that FEATURE is a feature of the current Emacs." So there's no
requirement that FEATURE be the name of an existing file. But `require'
loads a feature from an existing file, so it has to find that file,
using the name of the feature as a default. But if the file providing
that feature has a different name, you have to pass that name (just the
base name without extension) to `require'.
Steve Berman
next prev parent reply other threads:[~2022-01-09 16:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 5:14 File for minor mode not found fatiparty--- via Users list for the GNU Emacs text editor
2022-01-09 6:47 ` tomas
2022-01-09 7:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-09 10:04 ` tomas
2022-01-09 15:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-09 14:43 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-09 15:12 ` Stephen Berman
2022-01-09 15:57 ` Tomas
[not found] ` <878rvpeyek.fsf@gmx.net-MszOZsb----2>
2022-01-09 15:46 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-09 16:01 ` Stephen Berman [this message]
[not found] ` <874k6cgap3.fsf@gmx.net-MszaWDg----2>
2022-01-09 16:37 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-09 16:50 ` tomas
2022-01-09 21:49 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-09 22:10 ` Tomas
[not found] ` <YdtdbjZlybD0X0rJ@tuxteam.de-Mt-tK84----2>
2022-01-10 12:19 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-10 18:09 ` Tomas
[not found] ` <Ydx2V/PAuIJAU8HR@tuxteam.de-Mt4B_wx----2>
2022-01-11 0:23 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-11 6:38 ` Tomas
2022-01-11 16:33 ` Michael Heerdegen
2022-01-11 16:41 ` tomas
[not found] ` <Yd0lz7vSTBzYeeJW@tuxteam.de-Mt6ynvW--7-2>
2022-01-11 16:25 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-11 16:36 ` Michael Heerdegen
2022-01-09 15:56 ` Tomas
[not found] ` <SJ0PR10MB5488E2D49393EC94EC06A41CF34F9@SJ0PR10MB5488.namprd10.prod.outlook.com>
[not found] ` <MsxIft1--B-2@tutanota.com>
2022-01-09 17:25 ` [External] : " Drew Adams
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=874k6cgap3.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=fatiparty@tutanota.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.
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.