[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: I continue to get error ob-ref: unescaped character literals
From: |
Christopher Dimech |
Subject: |
Re: I continue to get error ob-ref: unescaped character literals |
Date: |
Mon, 23 Nov 2020 21:58:59 +0100 |
I fixed it now. Was related to org-babel.
Am now trying to install the latest version of Org as a package by invoking
M-x package-install RET org RET after having configured Emacs to include
Org ELPA as a package repository.
Have done like below, however I am not finding org when I try to
enter the command "M-x package-install RET org RET".
(require 'package)
(add-to-list 'package-archives '("org" . "https://orgmode.org/elpa/"))
(add-to-list 'package-archives
'("melpa-stable" . "https://melpa.org/packages/"))
> Sent: Monday, November 23, 2020 at 8:54 PM
> From: "Stephen Berman" <stephen.berman@gmx.net>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Michael Heerdegen" <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
> Subject: Re: I continue to get error ob-ref: unescaped character literals
>
> On Mon, 23 Nov 2020 20:28:33 +0100 Christopher Dimech <dimech@gmx.com> wrote:
>
> >> Sent: Monday, November 23, 2020 at 8:16 PM
> >> From: "Stephen Berman" <stephen.berman@gmx.net>
> >> 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
> >>
> >> On Mon, 23 Nov 2020 13:23:30 +0100 Michael Heerdegen
> >> <michael_heerdegen@web.de> wrote:
> >>
> >> > Stephen Berman <stephen.berman@gmx.net> writes:
> >> >
> >> >> It's a warning from the byte compiler that it found `?(' and `?)' in
> >> >> elisp code, which should be written as `?\(' and `?\)'. See (info
> >> >> "(elisp) Basic Char Syntax"):
> >> >
> >> > I'm not sure if it is from compiling. Can this warning also be raised
> >> > by the reader?
> >>
> >> You're right, it's also raised on loading uncompiled elisp. Thanks for
> >> the correction.
> >
> > What's one to do about it?
>
> The backtrace you posted had this:
>
> Debugger entered--Lisp error: "Loading ‘ob-ref’: unescaped character literals
> `?(..."
> require(ob-ref)
> eval-buffer(#<buffer *load*-6358> nil
> "/usr/share/emacs/site-lisp/org-mode/ob.el" nil t) ; Reading at buffer
>
> So it looks like there are unescaped character literals in the version
> of ob-ref.el you have in site-lisp. Maybe it's an old version. So you
> should check if that's the case, and if so, escape them with a
> backslash.
>
> Steve Berman
>
- Re: I continue to get error ob-ref: unescaped character literals, (continued)
- Re: I continue to get error ob-ref: unescaped character literals, Michael Heerdegen, 2020/11/23
- Re: I continue to get error ob-ref: unescaped character literals, Christopher Dimech, 2020/11/23
- Re: I continue to get error ob-ref: unescaped character literals, Michael Heerdegen, 2020/11/23
- Re: I continue to get error ob-ref: unescaped character literals, Christopher Dimech, 2020/11/23
- Re: I continue to get error ob-ref: unescaped character literals, Michael Heerdegen, 2020/11/23
- Re: I continue to get error ob-ref: unescaped character literals, Christopher Dimech, 2020/11/23
- Re: I continue to get error ob-ref: unescaped character literals, Nick Dokos, 2020/11/23
- Re: I continue to get error ob-ref: unescaped character literals, Stephen Berman, 2020/11/23
- Re: I continue to get error ob-ref: unescaped character literals, Christopher Dimech, 2020/11/23
- Re: I continue to get error ob-ref: unescaped character literals, Stephen Berman, 2020/11/23
- Re: I continue to get error ob-ref: unescaped character literals,
Christopher Dimech <=
- Re: I continue to get error ob-ref: unescaped character literals, Stephen Berman, 2020/11/23