unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: emacs-devel@gnu.org
Subject: Some proposed backports from master to emacs-26
Date: Sun, 03 Jun 2018 08:03:02 -0400	[thread overview]
Message-ID: <871sdo9ix5.fsf@gmail.com> (raw)

I pushed some proposed backports to scrach/np/backport-26.2, listed here
by bug:

- #30931 abort() due to CHECK_ALLOCATED_AND_LIVE failure during GC
  Not a regression, but IMO nasty enough to be worth backporting.
  - Centralize Bug#30931 fix
  - Fix another case of freed markers in the undo-list (Bug#30931)
  - Fix CHECK_ALLOCATED_AND_LIVE abort during GC

- #30995 Slow window and frame popup on Emacs 26+ (e.g. with Helm)
  Regression.
  - Don't wait for visible frames to become visible

- bug#27656: 26.0.50; Fix "Make mail-extract-address-components return the user name more"
  Regression.
  - Revert "Make mail-extract-address-components return the user name more"

- bug#31146: 27.0.50; ielm via cl-prin1 infloops when printing circular object
  Bug in new feature.
  - Fix cl-print for circular sublists (Bug#31146)

- #30363 26.0.91; epa-decrypt-file not using epa-pinentry-mode
  Fix is trivial, and obviously safe.  Not a regression, but with
  removal of pinentry.el, epa-pinentry-mode becomes more important.
  - * lisp/epa.el (epa-decrypt-file): Apply epa-pinentry-mode (Bug#30363).

- part of Bug#28323 improper parsing of first argument
  Regression in Emacs 24.4
  - esh-opt.el: Fix improper parsing of first argument (Bug#28323)

- #30846 26.0.91; debug-watch of kill-all-local-variables triggers
      'assertion failed: found == !EQ (blv->defcell, blv->valcell)'
  Bug in new feature.
  - Fix bug#30846, along with misc cleanups found along the way



             reply	other threads:[~2018-06-03 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-03 12:03 Noam Postavsky [this message]
2018-06-03 16:26 ` Some proposed backports from master to emacs-26 Eli Zaretskii
2018-06-03 17:32   ` Noam Postavsky

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=871sdo9ix5.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --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 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).