From: Richard Copley <rcopley@gmail.com>
To: 21131@debbugs.gnu.org, control@debbugs.gnu.org,
Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#21131: bug#23930: 25.0.95; "M-: 3072 RET" very slow to echo "3072
Date: Sat, 9 Jul 2016 23:13:04 +0100 [thread overview]
Message-ID: <CAPM58ohLNp=xq+fi=ofyjXc78u=OaUaZKZOoVE1EmFZnDKirNw@mail.gmail.com> (raw)
In-Reply-To: <FFF03935-2868-4BF8-8DCB-10A2E27BD620@dtpq.com>
merge 23930 21131
thanks
Noam Postavsky wrote:
> Maybe a dup of http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21131
Looks like it! Thanks, merging.
prev parent reply other threads:[~2016-07-09 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 1:40 bug#21131: minibuffer repl delay Chris Stacy
2015-07-25 6:44 ` Andreas Schwab
2015-07-25 8:20 ` Chris Stacy
2015-07-25 18:28 ` Glenn Morris
2015-07-25 18:48 ` Eli Zaretskii
2016-07-09 22:13 ` Richard Copley [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
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='CAPM58ohLNp=xq+fi=ofyjXc78u=OaUaZKZOoVE1EmFZnDKirNw@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=21131@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).