From: David Bremner <david@tethera.net>
To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH v2] emacs: add compatability functions for emacs 23
Date: Fri, 11 Nov 2016 09:38:53 -0400 [thread overview]
Message-ID: <87vavu5e6q.fsf@tethera.net> (raw)
In-Reply-To: <87zil65f8c.fsf@tethera.net>
David Bremner <david@tethera.net> writes:
> The plot thickens. With this patch applied, I can generate an emacs
> segfault with
>
> 1) EMACS=emacs23 ./devel/try-emacs-mua -q
>
> 2) M-x notmuch-search <return>
>
> 3) tag:inbox <return>
OK, I managed to figure out the problem. I had byte compiled the emacs
code with emacs24, and loading that in emacs23 caused all heck to break
loose. With the byte compilation done with a matching version of emacs,
the test suite passes.
So my conclusions from all this fun:
1) since Mark went to the trouble of doing the compatiblity functions,
we may as well get emacs23 working again.
2) It's getting hard to debug emacs23 problems, and developer time is
scarce, so at the same time, deprecate emacs23 support, so e.g. after
the next major release we can just drop it.
3) With the caveat that we plan to drop the compat functions, I leave it
to mark's judgement whether it's worth putting them in a seperate
file, or just adding the FSF copyright to the top of the file.
next prev parent reply other threads:[~2016-11-11 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 10:21 [PATCH v2] emacs: add compatability functions for emacs 23 Mark Walters
2016-11-02 23:57 ` Matt Armstrong
2016-11-11 12:11 ` David Bremner
2016-11-11 13:16 ` David Bremner
2016-11-11 13:38 ` David Bremner [this message]
2016-11-11 17:23 ` Tomi Ollila
2016-11-11 18:51 ` David Bremner
2016-11-12 12:27 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vavu5e6q.fsf@tethera.net \
--to=david@tethera.net \
--cc=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).