From: Mark Oteiza <mvoteiza@udel.edu>
To: 25716@debbugs.gnu.org
Subject: bug#25716: 26.0.50; Invalid byte opcode: op=0, ptr=30
Date: Mon, 13 Feb 2017 23:28:36 -0500 [thread overview]
Message-ID: <8760kdz98r.fsf@holos> (raw)
From -Q:
1. C-x C-f some/patch.diff RET
2. M-n
Error running timer: (error "Invalid byte opcode: op=0, ptr=30")
In GNU Emacs 26.0.50.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw scroll bars)
of 2017-02-13 built on logos
Repository revision: fffd4ffd747fe46bb7849a874e4ae265b6eda54e
next reply other threads:[~2017-02-14 4:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 4:28 Mark Oteiza [this message]
2017-02-14 6:50 ` bug#25716: 26.0.50; Invalid byte opcode: op=0, ptr=30 Tino Calancha
2017-02-14 13:01 ` Vibhav Pant
2017-02-14 15:18 ` Vibhav Pant
2017-02-14 15:47 ` Tino Calancha
2017-02-14 17:40 ` Vibhav Pant
2017-02-14 17:45 ` Mark Oteiza
2017-02-14 20:16 ` Eli Zaretskii
2017-02-15 15:45 ` Vibhav Pant
2017-02-15 16:52 ` Eli Zaretskii
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=8760kdz98r.fsf@holos \
--to=mvoteiza@udel.edu \
--cc=25716@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).