all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jay Adams <jka@google.com>
To: Wolfgang Jenkner <wjenkner@inode.at>
Cc: 21830@debbugs.gnu.org
Subject: bug#21830: Useless messages from comint-previous-matching-input
Date: Wed, 4 Nov 2015 19:49:49 -0800	[thread overview]
Message-ID: <CAPrNdr-a9NR4B+5zVK8aPFNVPYENo_z8WNWyLjyBKEfP90qJAQ@mail.gmail.com> (raw)
In-Reply-To: <85a8qtdwll.fsf@iznogoud.viz>

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

Thanks to all who replied.

It looks like this is fixed in 24.5 (I was running 24.3).  That message
call now appears inside of (let ((message-log-max nil)) ...).

I verified that this fixes the problem on the Mac.


On Wed, Nov 4, 2015 at 6:11 PM, Wolfgang Jenkner <wjenkner@inode.at> wrote:

> On Wed, Nov 04 2015, Jay Adams wrote:
>
> > 1. They go by so fast as to be unnoticeable (this happens on my Ubuntu
> > desktop).
> > 2. They go by slowly and make the search excruciatingly slow (this
> happens
> > on my Mac).
>
> I guess the message is meant to remain visible until you use the
> minibuffer (again) or some other message pops up from somewhere.
>
> At least, this is what happens for me when I call
> comint-previous-matching-input-from-input or
> comint-previous-matching-input repeatedly (via some key binding).
>
> Can you reproduce your problem with emacs -Q?
>

[-- Attachment #2: Type: text/html, Size: 1290 bytes --]

  reply	other threads:[~2015-11-05  3:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 17:50 bug#21830: Useless messages from comint-previous-matching-input Jay Adams
2015-11-04 18:04 ` John Wiegley
2015-11-04 18:13   ` Eli Zaretskii
2015-11-04 18:24     ` John Wiegley
2015-11-04 20:42       ` Eli Zaretskii
2015-11-04 21:26         ` John Wiegley
2015-11-05  2:11 ` Wolfgang Jenkner
2015-11-05  3:49   ` Jay Adams [this message]
2015-11-05  5:14     ` John Wiegley
2015-11-05  5:35       ` Jay Adams

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=CAPrNdr-a9NR4B+5zVK8aPFNVPYENo_z8WNWyLjyBKEfP90qJAQ@mail.gmail.com \
    --to=jka@google.com \
    --cc=21830@debbugs.gnu.org \
    --cc=wjenkner@inode.at \
    /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.