From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: I continue to get error ob-ref: unescaped character literals
Date: Mon, 23 Nov 2020 14:14:55 +0100 [thread overview]
Message-ID: <trinity-5c393b54-fb96-4094-8843-e3ea9b2af69d-1606137295162@3c-app-mailcom-bs01> (raw)
In-Reply-To: <875z5wz1kz.fsf@web.de>
> Sent: Monday, November 23, 2020 at 1:42 PM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: I continue to get error ob-ref: unescaped character literals
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > The problem only crops up when I call (require 'org)
>
> If this doesn't happen with emacs -Q it is possible that the problem is
> in your config. Some `with-eval-after-load' or `add-hook' call maybe?
No, it does nat happen with emacs -Q
Must be something with my config file, but what! Seems to me that I cannot put
(require 'org) just anywhere.
Currently I have a file org.el
And even when I commentall the commands in the file, the message still appears
----- org.el -----
(require 'org)
;;-----------------------------------------------------------------------
;; Orgbabel - For executing programming language source code
(setq orgbabel
"~/GAdmSw/orgbabel.el")
;;(load orgbabel)
;;-----------------------------------------------------------------------
;; Orghist - For logging history about jobs
(setq orghist
"~/GAdmSw/orghist.el")
;;(load orghist)
;;-----------------------------------------------------------------------
;; Orghutf - Uses Utf-8 Geometric Pictograms for headings
(setq gungadin-orghutf
"~/GAdmSw/orghutf.el")
(load orghutf)
(require 'orghutf)
(add-hook 'org-mode-hook
(lambda ()
(orghutf-mode 1) ))
----- org.el -----
> Regards,
>
> Michael.
>
>
>
next prev parent reply other threads:[~2020-11-23 13:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 3:37 I continue to get error ob-ref: unescaped character literals Christopher Dimech
2020-11-23 8:28 ` Stephen Berman
2020-11-23 12:23 ` Michael Heerdegen
2020-11-23 12:30 ` Christopher Dimech
2020-11-23 12:42 ` Michael Heerdegen
2020-11-23 13:14 ` Christopher Dimech [this message]
2020-11-23 13:26 ` Michael Heerdegen
2020-11-23 13:32 ` Christopher Dimech
2020-11-23 13:54 ` Michael Heerdegen
2020-11-23 14:26 ` Christopher Dimech
2020-11-23 14:34 ` Michael Heerdegen
2020-11-23 14:45 ` Christopher Dimech
2020-11-23 15:40 ` Nick Dokos
2020-11-23 19:16 ` Stephen Berman
2020-11-23 19:28 ` Christopher Dimech
2020-11-23 19:54 ` Stephen Berman
2020-11-23 20:58 ` Christopher Dimech
2020-11-23 21:41 ` Stephen Berman
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=trinity-5c393b54-fb96-4094-8843-e3ea9b2af69d-1606137295162@3c-app-mailcom-bs01 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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).