unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mike Kupfer <kupfer@rawbw.com>
To: Eli Zaretskii <eliz@gnu.org>,
	Chris Siebenmann <cks.emacsbugs-01@cs.toronto.edu>
Cc: Bill Wohler <wohler@newt.com>, 67359@debbugs.gnu.org
Subject: bug#67359: 29.1; 29.1: MH-E limited display malfunctions if nothing is matched
Date: Wed, 22 Nov 2023 08:08:48 -0800	[thread overview]
Message-ID: <9058.1700669328@alto> (raw)
In-Reply-To: Your message of "Wed, 22 Nov 2023 16:43:09 +0200." <83h6ldhmrm.fsf@gnu.org>

Eli Zaretskii wrote:

> I'm not sure if it is better to report MH-E-related bugs here or
> submit the reports to https://sourceforge.net/p/mh-e/bugs/.

We (MH-E developers) have talked about dropping the SourceForge bug
tracker and just using the Emacs debbugs, but I don't think we ever
reached a definite decision.  In the meantime, either should work, since
at least one of us (me) is subscribed to Emacs bugs.

> > From: Chris Siebenmann <cks.emacsbugs-01@cs.toronto.edu>
> > Date: Tue, 21 Nov 2023 19:28:45 -0500
[...]
> > When you do this, MH-E will first show an error message in a buffer
> > below the folder window and then narrow the main folder window to a
> > single line showing 'scan: no messages match specification'. ('/ w' will
> > then fix the situation.)

Yes, I can reproduce this.  

Chris, I'm not sure what you're expecting instead.  I'm guessing you'd
like to have the original message list in the folder buffer (no need to
type "/ w"), with the error text displayed like a normal error, rather
than in the folder buffer.  Do I understand correctly?

thanks,
mike





  reply	other threads:[~2023-11-22 16:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22  0:28 bug#67359: 29.1; 29.1: MH-E limited display malfunctions if nothing is matched Chris Siebenmann
2023-11-22 14:43 ` Eli Zaretskii
2023-11-22 16:08   ` Mike Kupfer [this message]
2023-11-22 16:21     ` Chris Siebenmann
2023-11-23  1:56   ` Bill Wohler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-23  6:53     ` Eli Zaretskii
2023-11-23 19:59       ` Mike Kupfer

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=9058.1700669328@alto \
    --to=kupfer@rawbw.com \
    --cc=67359@debbugs.gnu.org \
    --cc=cks.emacsbugs-01@cs.toronto.edu \
    --cc=eliz@gnu.org \
    --cc=wohler@newt.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 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).