all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Ranjan Maitra <maitra@gmx.com>
Cc: 26531-done@debbugs.gnu.org
Subject: bug#26531: Emacs crashes with adding space character
Date: Sun, 16 Apr 2017 12:24:59 -0700	[thread overview]
Message-ID: <1bbd8ab9-0ea1-68f9-27c8-c7809ac6d91a@cs.ucla.edu> (raw)
In-Reply-To: <20170416084348.09ebb0625a0ddb8b4997bcc1@gmx.com>

Ranjan Maitra wrote:
> PS: I was able to compile the git version and at least now, I could not replicate the bug on this little file using the newly-compiled emacs.

Thanks for checking. Closing the bug report.

> Is there a date for the release of a new version?

Not that I know of. I don't know what's holding things up. For some time I've 
thought that users are suffering significantly more by not having the new 
release than they would suffer by getting it "prematurely".





  reply	other threads:[~2017-04-16 19:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-16  3:18 bug#26531: Emacs crashes with adding space character Ranjan Maitra
2017-04-16  4:38 ` bug#26531: Further information (Emacs crashes with adding space character) Ranjan Maitra
2017-04-16  5:43 ` bug#26531: Emacs crashes with adding space character Paul Eggert
2017-04-16  6:41   ` Eli Zaretskii
2017-04-16 19:21     ` Paul Eggert
2017-04-16 13:43   ` Ranjan Maitra
2017-04-16 19:24     ` Paul Eggert [this message]
2017-04-16 20:08       ` Eli Zaretskii
2017-04-17  0:06         ` Ranjan Maitra
2017-04-17  5:43           ` Eli Zaretskii
2017-04-17 13:54             ` Ranjan Maitra
2017-04-17 12:34           ` npostavs
2017-04-16 13:44   ` Ranjan Maitra
2017-04-16 16:57     ` Eli Zaretskii
2017-04-16 18:29       ` Ranjan Maitra
2017-04-16 18:32       ` Ranjan Maitra
2017-04-16  6:37 ` Eli Zaretskii

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=1bbd8ab9-0ea1-68f9-27c8-c7809ac6d91a@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=26531-done@debbugs.gnu.org \
    --cc=maitra@gmx.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 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.