all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Emacs bug Tracking System'" <don@donarmstrong.com>,
	"'Chong Yidong'" <cyd@stupidchicken.com>,
	<994@emacsbugs.donarmstrong.com>
Cc: 'Emacs Bugs' <bug-gnu-emacs@gnu.org>
Subject: bug#1055: Processed: severity 994 wishlist
Date: Mon, 29 Sep 2008 16:38:16 -0700	[thread overview]
Message-ID: <001101c9228c$728367b0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <handler.s.C.12227280491935.transcript@emacsbugs.donarmstrong.com>

> From: Emacs bug Tracking System Sent: Monday, September 29, 2008 3:50 PM
> Processing commands for control@emacsbugs.donarmstrong.com:
> 
> > severity 994 wishlist
> bug#994: 23.0.60; minibuffer completion should act on all 
> minibuffer input
> Severity set to `wishlist' from `normal'

Why is this fodder for the wishlist? This bug is a regression!

Stefan asked for a recipe to reproduce it, so no doubt this behavior is not
intentional (not a design change). It is bad, bugged behavior, and it is new. 

Why on earth would such a bug report be classified as "wish list"? Perhaps you
are simply wishing bugs away? ;-)








  reply	other threads:[~2008-09-29 23:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87k5culgm2.fsf@cyd.mit.edu>
2008-09-29 22:50 ` Processed: severity 994 wishlist Emacs bug Tracking System
2008-09-29 23:38   ` Drew Adams [this message]
2008-09-30  1:59     ` bug#994: " Chong Yidong
2008-09-30  3:09       ` Drew Adams
2008-09-30 14:09         ` Stefan Monnier
2008-09-30 14:15           ` Drew Adams
2008-09-30 15:59             ` Stefan Monnier
2008-09-30 16:10               ` Drew Adams
2008-09-30  2:05     ` bug#1055: marked as done (Processed: severity 994 wishlist) Emacs bug Tracking System

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='001101c9228c$728367b0$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=1055@emacsbugs.donarmstrong.com \
    --cc=994@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=don@donarmstrong.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.