From: martin rudalics <rudalics@gmx.at>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: niwtrx@icloud.com, 38912@debbugs.gnu.org, eggert@cs.ucla.edu,
pipcet@gmail.com, emacs-devel@gnu.org
Subject: Re: bug#38912: 27.0.60; PDumper meets segmentation fault when evil is loaded
Date: Tue, 7 Jan 2020 19:29:14 +0100 [thread overview]
Message-ID: <1e33c53e-f6ae-a3bf-6ce0-5c1894cb9b35@gmx.at> (raw)
In-Reply-To: <jwvwoa3w3lb.fsf-monnier+emacs@gnu.org>
> I actually *expected* that `equal` on window configs would behave like
> `eq`. It would have never occurred to me (before I looked at the code)
> that it could be different (although in retrospect, I can see reasons
> why it could make sense).
`eq' wouldn't make any sense at all. 'compare-window-configurations'
per se is a misconception. But I have no intention to dig into
strokes.el to find out why on earth it would need such a thing and how
to remove it.
martin
next prev parent reply other threads:[~2020-01-07 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <333553AC-68DE-4F1C-9586-5A13248AD6DD@icloud.com>
[not found] ` <83ftgvh96l.fsf@gnu.org>
[not found] ` <D1473DD8-48F8-4204-80B5-BE6396B8B668@icloud.com>
[not found] ` <83a771g2tc.fsf@gnu.org>
[not found] ` <CAOqdjBfjpSqhDcMiHGQfaOGZEodmjmvhQionRPO1OQ0sVsLDPg@mail.gmail.com>
[not found] ` <83o8vgee85.fsf@gnu.org>
[not found] ` <8b2e879676c6ecc1371d50e033164424.squirrel@dancol.org>
2020-01-06 17:13 ` bug#38912: 27.0.60; PDumper meets segmentation fault when evil is loaded Pip Cet
2020-01-07 2:38 ` Paul Eggert
2020-01-07 3:34 ` dancol
2020-01-07 14:16 ` Stefan Monnier
2020-01-07 19:32 ` Paul Eggert
2020-01-07 15:47 ` Eli Zaretskii
2020-01-07 17:37 ` Stefan Monnier
2020-01-07 17:43 ` Eli Zaretskii
2020-01-07 18:01 ` Stefan Monnier
2020-01-07 18:11 ` Eli Zaretskii
2020-01-07 18:47 ` Stefan Monnier
2020-01-07 18:29 ` martin rudalics [this message]
2020-01-07 18:43 ` Stefan Monnier
2020-01-07 18:58 ` martin rudalics
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=1e33c53e-f6ae-a3bf-6ce0-5c1894cb9b35@gmx.at \
--to=rudalics@gmx.at \
--cc=38912@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=niwtrx@icloud.com \
--cc=pipcet@gmail.com \
/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).