unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sanel Zukan <sanelz@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 47318@debbugs.gnu.org
Subject: bug#47318: 26.3; Modules on Emacs 26.3 broken?
Date: Tue, 23 Mar 2021 22:41:32 +0100	[thread overview]
Message-ID: <87h7l15z03.fsf@example.com> (raw)
In-Reply-To: <CAArVCkQ8C7y39miTBVtjeebgpR9mFxHryetbX+8cgNw+b=8e9A@mail.gmail.com>

Hi Philipp,

Thanks for your fast reply. I tried that; it will return 't,' but no
symbols are visible in Emacs. Tried with modules-tut [3] example and
emacs-libvterm.

Any idea what could go wrong?

Best regards,
Sanel

Philipp Stephani <p.stephani2@gmail.com> writes:
> Am Mo., 22. März 2021 um 14:14 Uhr schrieb Sanel Zukan <sanelz@gmail.com>:
>>
>> Hi guys,
>>
>> I'm getting this [1] error from freshly compiled Emacs 26.3 and
>> vterm-module.
>>
>> Also, emacs-eject [2] and very simple module [3] fails on 26.3 with the
>> similar error. However, they are working fine on 27.1.
>>
>> Any idea what could go wrong? I also tried to run bare Emacs with
>> 'emacs -Q'. In the all cases, Emacs is compiled with modules support.
>>
>> [1] https://github.com/akermu/emacs-libvterm/issues/181
>> [2] https://github.com/syohex/emacs-eject
>> [3] http://diobla.info/blog-archive/modules-tut.html
>>
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30164 is probably at
> least part of the answer.
> However, loading modules in general should still work, even in Emacs
> 26. Do you also get errors when loading the module file directly with
> `load' instead of `require'?





  reply	other threads:[~2021-03-23 21:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 13:13 bug#47318: 26.3; Modules on Emacs 26.3 broken? Sanel Zukan
2021-03-22 13:39 ` Philipp Stephani
2021-03-23 21:41   ` Sanel Zukan [this message]
2021-03-27 15:39     ` Philipp
2021-03-27 17:53       ` Sanel Zukan
2021-03-28 16:36         ` Philipp Stephani
2021-03-29  9:16           ` Sanel Zukan
2022-06-26 18:25 ` Lars Ingebrigtsen

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=87h7l15z03.fsf@example.com \
    --to=sanelz@gmail.com \
    --cc=47318@debbugs.gnu.org \
    --cc=p.stephani2@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).