From: Drew Adams <drew.adams@oracle.com>
To: Gottfried <gottfried@posteo.de>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
Jean Louis <bugs@gnu.support>
Subject: RE: [External] : Re: text formating
Date: Thu, 9 Feb 2023 19:11:54 +0000 [thread overview]
Message-ID: <SJ0PR10MB54884276236D9CF2F414D529F3D99@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <d285ca18-9c34-fc72-10d6-73350964c544@posteo.de>
> I put this in my init.el file
>
> ;;(define-key KEYMAP KEY DEF &optional REMOVE)
> (require "markdown-mode)
> (define-key markdown-mode-map (kbd "C-c a") #'rcd-markdown-preview)
> ........................................................................
> .
> when starting emacs
> the message came up:
>
> Warning (initialization): An error occurred while loading
> ‘/home/gfp/.config/emacs/init.el’:
>
> End of file during parsing: /home/gfp/.config/emacs/init.el
^^^^^^^^^^^^^^^^^^^^^^^^^^
> To ensure normal operation, you should investigate and remove the
> cause of the error in your initialization file. Start Emacs with
> the ‘--debug-init’ option to view a complete error backtrace. Disable
^^^^^^^^^^^^
> showing Disable logging
>
........................................................................
> Did I put it in the right order?
> Or any other mistake?
Yes, right order: load the library, then use it.
Something in your init file doesn't _parse_. Most likely you're missing a right paren or something. Use `M-x check-parens' in your init file.
You can put (setq debug-on-error t) at the start of your init file, or customize it to t.
You can start Emacs using the switch --debug-init, as the error msg suggested.
See also https://www.gnu.org/software/emacs/manual/html_node/elisp/Error-Debugging.html
___
In general, when your init file has a problem, consider _bisecting_ it, to find the culprit. Bisecting is a binary search - it's fast. You can use `M-x comment-region` to comment out 1/2, then 1/4, 1/8, 1/16,... of your init file. With C-u it UNcomments one level of commenting.
next prev parent reply other threads:[~2023-02-09 19:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 12:06 text formating Gottfried
2023-01-30 20:28 ` H. Dieter Wilhelm
2023-01-31 7:34 ` Jean Louis
2023-01-31 11:23 ` Ulrich Deiters
2023-01-31 12:43 ` Jean Louis
2023-02-02 13:52 ` Gottfried
2023-02-02 14:30 ` Eli Zaretskii
2023-02-02 15:40 ` [External] : " Drew Adams
2023-02-02 20:12 ` Jean Louis
2023-02-03 7:30 ` Eli Zaretskii
2023-02-03 9:08 ` Jean Louis
2023-02-03 17:24 ` Emanuel Berg
2023-02-04 15:24 ` Jean Louis
2023-02-04 21:44 ` Emanuel Berg
2023-02-07 17:25 ` Gottfried
2023-02-07 22:28 ` Jean Louis
2023-02-08 16:49 ` Gottfried
2023-02-08 19:37 ` Jean Louis
2023-02-08 20:18 ` [External] : " Drew Adams
2023-02-09 14:59 ` Gottfried
2023-02-09 15:27 ` [External] : " Drew Adams
2023-02-09 16:59 ` Gottfried
2023-02-09 17:13 ` Drew Adams
2023-02-09 18:10 ` Gottfried
2023-02-09 18:26 ` Jean Louis
2023-02-09 19:12 ` Drew Adams
2023-02-10 4:18 ` Jean Louis
2023-02-09 19:11 ` Drew Adams [this message]
2023-02-11 15:25 ` Gottfried
2023-02-11 16:10 ` tomas
2023-02-11 19:17 ` Jean Louis
2023-02-11 16:56 ` 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
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=SJ0PR10MB54884276236D9CF2F414D529F3D99@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=bugs@gnu.support \
--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).