unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime <heimeborgia@protonmail.com>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: Heime via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Subject: Calling require with hyphened features
Date: Tue, 06 Aug 2024 14:44:17 +0000	[thread overview]
Message-ID: <2mg7n5OF-SY5GTfb7daVo6TEQo8ozbyU1IKy99FvyhjjRg3X_i_0DsAn8D1kzYgmpBM3kZ8Gl_9OLunywzDshv0LcEGrgidUJtwntiy8Ce0=@protonmail.com> (raw)
In-Reply-To: <86jzgtlo1w.fsf@fastmail.fm>






Sent with Proton Mail secure email.

On Wednesday, August 7th, 2024 at 2:32 AM, Joost Kremers <joostkremers@fastmail.fm> wrote:

> On Tue, Aug 06 2024, Heime wrote:
> 
> > Does emacs allow calling "require" for features that are hyphened,
> > such as with
> > 
> > (require 'lumi-prevo)
> 
> 
> Not sure what your question is about, really, but a hyphen is a valid character
> of a symbol (name), so you can have feature names with a hyphen. In which case
> it's valid to require them.
> 
> Tip: why not just try for yourself and see what happens? Or if you have, post
> the actual problem you're dealing with.

I do have a problem with the require.  So it must be something else, I just 
wanted to be sure.   The likely failure is not finding the correct path for 
the feature I require.  I am quite sure of this now.



      reply	other threads:[~2024-08-06 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 12:56 Calling require with hyphened features Heime
2024-08-06 14:32 ` Joost Kremers
2024-08-06 14:44   ` Heime [this message]

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='2mg7n5OF-SY5GTfb7daVo6TEQo8ozbyU1IKy99FvyhjjRg3X_i_0DsAn8D1kzYgmpBM3kZ8Gl_9OLunywzDshv0LcEGrgidUJtwntiy8Ce0=@protonmail.com' \
    --to=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=joostkremers@fastmail.fm \
    /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).