From: Matthew Fidler <matthew.fidler@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "João Távora" <joaotavora@gmail.com>, emacs-devel@gnu.org
Subject: Re: Getting rid of low-level assumptions in yasnippet
Date: Mon, 30 Mar 2015 10:15:43 -0500 [thread overview]
Message-ID: <CAOmN8O6k2yoGaGFS0jS5wR0RjaVRX2P_Kb-hyoUK4CqQVsoqbw@mail.gmail.com> (raw)
In-Reply-To: <jwvpp7rgvos.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
Ok,
I believe the problem is with named components. In the old eieio, it
allowed nil names, but in the current implementation it requires a name for
named components.
A work-around in ergoemacs-mode shows the possible issue
https://github.com/ergoemacs/ergoemacs-mode/commit/71319c2cc1874248c885cd6b6e7f826fb24c49a7
Matt.
On Sun, Mar 29, 2015 at 7:47 PM, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> > Since I'm here I would also like to add that eieio doesn't work the same
> in
> > emacs 25.
>
> There's been many changes to EIEIO's internals, indeed. I've tried to
> preserve compatibility so far both for source files and for
> byte-compiled files (tho not for files byte-compiled with non-released
> Emacs versions).
> So if you experience incompatibilities because of the new code, please
> report them,
>
>
> Stefan
>
[-- Attachment #2: Type: text/html, Size: 1441 bytes --]
next prev parent reply other threads:[~2015-03-30 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 19:49 Getting rid of low-level assumptions in yasnippet Stefan Monnier
2015-03-20 11:03 ` João Távora
2015-03-20 14:18 ` Stefan Monnier
2015-03-28 15:59 ` João Távora
2015-03-28 20:32 ` Stefan Monnier
2015-03-28 21:23 ` João Távora
2015-03-29 19:36 ` Matthew Fidler
2015-03-30 0:47 ` Stefan Monnier
2015-03-30 15:15 ` Matthew Fidler [this message]
2015-03-30 18:53 ` Stefan Monnier
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=CAOmN8O6k2yoGaGFS0jS5wR0RjaVRX2P_Kb-hyoUK4CqQVsoqbw@mail.gmail.com \
--to=matthew.fidler@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).