From: Charles Millar <millarc@verizon.net>
To: emacs-orgmode@gnu.org
Subject: Re: Please see attached debug-init
Date: Fri, 27 Apr 2018 20:53:00 -0400 [thread overview]
Message-ID: <9fe3f7ec-3b7e-21c8-35a9-137cbb674287@verizon.net> (raw)
In-Reply-To: <87fu3hmjdb.fsf@alphaville.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
Hello,
On 04/26/2018 11:13 PM, Nick Dokos wrote:
> Charles Millar <millarc@verizon.net> writes:
>
>> Hi Nicholas,
>>
>> On 04/26/2018 07:34 PM, Bastien wrote:
>>
>> Hi Charles,
>>
>> Charles Millar <millarc@verizon.net> writes:
>>
>> Attached --debug-init when starting -
>>
>> is this with emacs -Q? If not, can you bisect your configuration?
>>
>> Thanks,
>>
>> emacs -Q starts fine.
>>
>> The problem may be with
>>
>> require 'ox-XXXXXXX
>>
>> When I worked my way down to (require 'ox-texinfo) there was no problem. When I uncomment that line the startup error appeared.
>>
>> In the warnings buffer part of the message is
>>
>> error: Invalid byte opcode: op=183, ptr=31
> Byte compilation is not necessarily backwards compatible.
>
> If the file was compiled with emacs 27, then earlier versions of emacs
> will not necessarily be able to deal with it. If you recompile all
> *.el files with emacs 24, they should work with emacs 24 and *also*
> with emacs 27.
>
I update org using the https:// access to the git repo.
the Emacs 24 version is the debian package. Is this a factor?
Charlie
Charlie
[-- Attachment #2: Type: text/html, Size: 1862 bytes --]
next prev parent reply other threads:[~2018-04-28 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 16:34 Please see attached debug-init Charles Millar
2018-04-26 23:34 ` Bastien
2018-04-27 2:27 ` Charles Millar
2018-04-27 3:13 ` Nick Dokos
2018-04-28 0:53 ` Charles Millar [this message]
2018-04-28 6:23 ` Bastien
2018-04-28 12:54 ` Charles Millar
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9fe3f7ec-3b7e-21c8-35a9-137cbb674287@verizon.net \
--to=millarc@verizon.net \
--cc=emacs-orgmode@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/org-mode.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).