From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: File for minor mode not found
Date: Sun, 9 Jan 2022 17:50:19 +0100 [thread overview]
Message-ID: <YdsSSzXe5tyw1mba@tuxteam.de> (raw)
In-Reply-To: <Mszh-61--3-2@tutanota.com>
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
On Sun, Jan 09, 2022 at 05:37:49PM +0100, fatiparty--- via Users list for the GNU Emacs text editor wrote:
[...]
> I have difficulty about the utility of 'provide'. You have pointed out that (provide 'daph)
> simply announces that daph is a feature of the current emacs. Can it be any name? The
> manual states that "calling 'provide' adds 'feature' tothe front of 'features' if it is not already
> in that list". This suggests that provide should also use (provide 'daph-ideograms).
That depends on how you want to call your feature. Note that once a
feature is `provide'd, a `require' of that feature does nothing. Quoting
from the docs:
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.
> I guess that one could define the feature as 'daph' when using 'provide'. And use the feature 'daph'
> when calling 'require'. In this way, the 'daph' will be recognise the 'daph' feature in the features variable,
> but use the optional filename "daph-ideograms"
Yes, that'd be a way to do it (in theory you could have one file
providing several features, for example).
> Thus
>
> daph-ideograms.el
> **********************
> (provide 'daph)
>
> test.el
> *******
> (add-to-list
> 'load-path "~/Admin/bin/gadi-1.0/typex/ziggurat-protowrit/daph-ideograms")
> ;; Load the Daph Package if it has not already been loaded.
> (require 'daph "daph-ideograms")
>
> --------
>
> My load path is quite long, and wonder how this can be shortened by storing in some other variable
> before passing to 'add-to-list'.
I don't quite understand your last sentence. What is it you are trying
to shorten -- and how?
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-01-09 16:50 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
[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 [this message]
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=YdsSSzXe5tyw1mba@tuxteam.de \
--to=tomas@tuxteam.de \
--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.