From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: #<EMACS BUG: INVALID DATATYPE (0x01) Save your buffers immediately and please report this bug>
Date: Sun, 28 Apr 2019 05:29:10 +0300 [thread overview]
Message-ID: <834l6ivp55.fsf@gnu.org> (raw)
In-Reply-To: <20190427201342.GF16260@protected.rcdrun.com> (message from Jean Louis on Sat, 27 Apr 2019 22:13:42 +0200)
> Date: Sat, 27 Apr 2019 22:13:42 +0200
> From: Jean Louis <bugs@gnu.support>
>
> I was using the module emacs-libpq for months
> without problem. Reference:
> https://github.com/anse1/emacs-libpq/issues/9
>
> Now I have upgraded to the latest development
> version of Emacs and am getting this bug below.
>
> (["tlds_id" "integer" "nextval('tlds_tlds_id_seq'::regclass)" "" 1 #<EMACS BUG: INVALID DATATYPE (0x01) Save your buffers immediately and please report this bug> "" #<EMACS BUG: INVALID DATATYPE (0x01) Save your buffers immediately and please report this bug> #<EMACS BUG: INVALID DATATYPE (0x01) Save your buffers immediately and please report this bug> "p" #<EMACS BUG: INVALID DATATYPE (0x01) Save your buffers immediately and please report this bug> "ID"] ["tlds_tld" "text" #<EMACS BUG: INVALID DATATYPE (0x01) Save your buffers immediately and please report this bug> "" 2 #<EMACS BUG: INVALID DATATYPE (0x01) Save your buffers immediately and please report this bug> "" #<EMACS BUG: INVALID DATATYPE (0x01) Save your buffers immediately and please report this bug> #<EMACS BUG: INVALID DATAT
YPE (0x01) Save your buffers immediately and please report this bug> "x
>
> Not even "SELECT 1" I can do without this bug
> appearing.
>
> If somebody have a clue, let me know.
Did you try recompiling the module against the new emacs-module.h?
next prev parent reply other threads:[~2019-04-28 2:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 20:13 #<EMACS BUG: INVALID DATATYPE (0x01) Save your buffers immediately and please report this bug> Jean Louis
2019-04-28 2:29 ` Eli Zaretskii [this message]
2019-04-28 5:14 ` Jean Louis
2019-04-28 8:44 ` Jean Louis
2019-04-28 9:34 ` Philipp Stephani
2019-04-28 9:46 ` Jean Louis
2019-04-29 5:45 ` Solved - was " Jean Louis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834l6ivp55.fsf@gnu.org \
--to=eliz@gnu.org \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.