unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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 13:30:32 +0100	[thread overview]
Message-ID: <trinity-ed47f805-68f6-42c1-8231-9d1ffe95e725-1606134632052@3c-app-mailcom-bs01> (raw)
In-Reply-To: <87blfoz2gt.fsf@web.de>

The problem only crops up when I call (require 'org)


> Sent: Monday, November 23, 2020 at 1:23 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
>
> 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?
>
> Michael.
>
>
>



  reply	other threads:[~2020-11-23 12:30 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 [this message]
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
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-ed47f805-68f6-42c1-8231-9d1ffe95e725-1606134632052@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).