From: Stephen Berman <stephen.berman@gmx.net>
To: Gottfried <gottfried@posteo.de>
Cc: David Masterson <dsmasterson@gmail.com>,
Jean Louis <bugs@gnu.support>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: pandoc-mode /Asciidoc
Date: Sun, 26 Feb 2023 11:53:02 +0100 [thread overview]
Message-ID: <877cw4r94h.fsf@gmx.net> (raw)
In-Reply-To: <291efab1-2d10-5d42-8439-41cea8acd3cb@posteo.de> (gottfried@posteo.de's message of "Sun, 26 Feb 2023 10:31:47 +0000")
On Sun, 26 Feb 2023 10:31:47 +0000 Gottfried <gottfried@posteo.de> wrote:
> Hi,
>
> Yes you were right
>
>> This error means emacs cannot find the "add-to-path" function. Maybe
>> you want "add-to-list"?
>
> Now I get an other error message and I don’t know why.
>
>> Debugger entered--Lisp error: (file-missing "Cannot open load file" "Datei
>> oder Verzeichnis nicht gefunden" "asciidoc.el")
>> load("asciidoc.el")
>> load-with-code-conversion("/home/gfp/.config/emacs/init.el"
>> "/home/gfp/.config/emacs/init.el" t t)
>> load("/home/gfp/.config/emacs/init" noerror nomessage)
>> startup--load-user-init-file(#f(compiled-function () #<bytecode
>> 0x1bd9a952b2a41bee>) #f(compiled-function () #<bytecode 0x4d12c0e0e44348b>)
>> t)
>> command-line()
>> normal-top-level()
>
> I put the file: "asciidoc.el" in my direcory:
>
> /home/gfp/.config/emacs/Zusatzpakete/selbstinstalliert/Asciidoc/
>
>
> and in my init.el file it looks like this:
>
>
> (load "asciidoc.el")
> (add-to-list 'load-path
> "/home/gfp/.config/emacs/Zusatzpakete/selbstinstalliert/Asciidoc/")
>
> So, where is my mistake?
> Why emacs can’t find my file?
Lisp expresssions in a buffer are evaluated sequentially, and load-path
has to include the directory before you try to load a file in in it, so
the order must be this:
(add-to-list 'load-path
"/home/gfp/.config/emacs/Zusatzpakete/selbstinstalliert/Asciidoc/")
(load "asciidoc.el")
> Second question
> If there is already an error showing up in the backtrace buffer
> can I test an other expression in the scratch buffer with hitting C-j?
That should be possible.
> It seems to me that the first backtrace blocks everything
> and I have to get right this one.
The backtrace shouldn't block executing unrelated code.
> How can I get rid of the first backtrace to check other expressions?
Type `q' in the backtrace buffer.
Steve Berman
next prev parent reply other threads:[~2023-02-26 10:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 14:26 pandoc-mode Gottfried
2023-02-13 14:40 ` pandoc-mode Jean Louis
2023-02-22 14:26 ` pandoc-mode /Asciidoc Gottfried
2023-02-23 11:33 ` Jean Louis
2023-02-23 11:34 ` Jean Louis
2023-02-23 14:13 ` Gottfried
2023-02-23 17:48 ` Jean Louis
2023-02-23 20:17 ` Jean Louis
2023-02-25 12:24 ` Gottfried
2023-02-26 1:36 ` David Masterson
2023-02-26 10:31 ` Gottfried
2023-02-26 10:53 ` Stephen Berman [this message]
2023-02-26 16:06 ` Gottfried
2023-02-26 16:50 ` Jean Louis
2023-02-27 8:41 ` Gottfried
2023-03-01 3:24 ` David Masterson
2023-03-02 18:06 ` Gottfried
2023-03-02 18:51 ` Gottfried
2023-03-13 4:17 ` Jean Louis
2023-03-15 15:42 ` Gottfried
2023-03-15 16:37 ` Emanuel Berg
2023-02-14 18:35 ` pandoc-mode Bruno Barbier
2023-02-14 19:52 ` pandoc-mode Joost Kremers
2023-02-22 14:13 ` pandoc-mode Gottfried
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=877cw4r94h.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=bugs@gnu.support \
--cc=dsmasterson@gmail.com \
--cc=gottfried@posteo.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.
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).