unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: Re: I continue to get error ob-ref: unescaped character literals
Date: Mon, 23 Nov 2020 21:58:59 +0100	[thread overview]
Message-ID: <trinity-2d7f530d-a23a-4c0a-9a54-02c6dcc1cd85-1606165139218@3c-app-mailcom-bs16> (raw)
In-Reply-To: <87pn43j1c9.fsf@rub.de>

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
>



  reply	other threads:[~2020-11-23 20:58 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
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 [this message]
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-2d7f530d-a23a-4c0a-9a54-02c6dcc1cd85-1606165139218@3c-app-mailcom-bs16 \
    --to=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=stephen.berman@gmx.net \
    /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).