all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: tomas@tuxteam.de
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs segfaults when handling wrong_type_argument backtrace
Date: Sat, 1 Apr 2023 10:06:56 +0200	[thread overview]
Message-ID: <ZCfmIPUzxcf56v0f@tuxteam.de> (raw)
In-Reply-To: <83zg7syvwn.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

On Sat, Apr 01, 2023 at 09:11:04AM +0300, Eli Zaretskii wrote:
> > Date: Sat, 1 Apr 2023 07:51:29 +0200
> > From: <tomas@tuxteam.de>
> > 
> > On Fri, Mar 31, 2023 at 09:01:04PM +0200, Jonas Jelten wrote:
> > > On 2023-03-30 20:51, Andrea Corallo wrote:
> > > > Jonas Jelten <jj@sft.lol> writes:
> > > > > After clearing the cache it seems to work, thanks, that was easy.
> > > > > I assumed that changes in the abi would result in a version bump :)
> > > > 
> > > > It results in Emacs changing the directory name of the eln under
> > > > eln-cache, this way Emacs would discard all the other elns and produce
> > > > new ones.
> > 
> > Just curious: what happens with the old directories?
> 
> Nothing: they stay as they were.

Thanks
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2023-04-01  8:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 21:54 Emacs segfaults when handling wrong_type_argument backtrace Jonas Jelten
2023-03-30  5:14 ` Eli Zaretskii
2023-03-30  9:36   ` Andrea Corallo
2023-03-30 10:30     ` Eli Zaretskii
2023-03-30 16:41       ` Jonas Jelten
2023-03-30 18:51         ` Andrea Corallo
2023-03-31 19:01           ` Jonas Jelten
2023-04-01  5:51             ` tomas
2023-04-01  6:11               ` Eli Zaretskii
2023-04-01  8:06                 ` tomas [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZCfmIPUzxcf56v0f@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.