unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 10873@debbugs.gnu.org
Subject: bug#10873: 24.0.93; `report-emacs-bug' obscures bug-reporting buffer (!)
Date: Tue, 11 Feb 2014 06:33:08 -0800 (PST)	[thread overview]
Message-ID: <281e9d1f-0853-4498-bd4f-7510213c0cab@default> (raw)
In-Reply-To: <87sirsc1lg.fsf@building.gnus.org>

> > emacs -Q
> >
> > M-x customize-option RET abbrev-file-name RET
> >
> > Put point after the c:/ in the default value c:/.abbrev_defs, and
> > hit C-k.
> >
> > M-x widget-complete RET
> >
> > (See bug #6830 - the completion candidates are the files in the
> > current dir, not the files in c:/.)
> >
> > You now have two windows in the only frame: (1) Customize, (2)
> > *Completions*.
> >
> > Still with point in the edit field of the Customize buffer:
> >
> > M-x report-emacs-bug RET fffffffffff RET
> >
> > In the only existing frame, you now have two windows: (1) *Bug
> > Help*, (2) *Completions*, with the first of these selected.
> >
> > The only important buffer to show at this point is completely
> > hidden: *unsent mail to bug-gnu-emacs@gnu.org*.  No way for a
> > user to report the bug, unless s?he knows both (a) that there
> > is a buffer somewhere, waiting for user input to report the bug
> > and (b) how to show that buffer.
> 
> Is this still a problem in Emacs 24.3?  The code in this area has
> gotten a lot of churn...

Yes, apparently so (in a build from 2014-02-07, at least).

I just followed the fine recipe and saw exactly what was reported.
Perhaps it is platform-specific, if that is not what you see.





  reply	other threads:[~2014-02-11 14:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 23:21 bug#10873: 24.0.93; `report-emacs-bug' obscures bug-reporting buffer (!) Drew Adams
2012-09-17  0:10 ` Drew Adams
2014-02-09  5:11 ` Lars Ingebrigtsen
2014-02-11 14:33   ` Drew Adams [this message]
2015-12-25 23:34     ` Drew Adams
2015-12-26  9:36       ` Eli Zaretskii
2015-12-27 16:05         ` martin rudalics
2015-12-27 16:12           ` martin rudalics
2015-12-27 16:25           ` Eli Zaretskii
2015-12-27 16:57             ` Drew Adams
2015-12-27 17:16               ` Eli Zaretskii
2015-12-27 17:06             ` martin rudalics
2015-12-27 17:15               ` Eli Zaretskii
2015-12-27 18:00                 ` Drew Adams
2015-12-27 18:37                   ` martin rudalics
2015-12-27 19:14                     ` Drew Adams
2015-12-28 10:08                       ` martin rudalics
2015-12-27 18:36                 ` martin rudalics
2015-12-28 18:23                 ` martin rudalics
2015-12-28 18:35                   ` Eli Zaretskii
2016-04-28 13:47                     ` Lars Ingebrigtsen
2015-12-27 18:00               ` Drew Adams
2015-12-27 16:51           ` Drew Adams
2015-12-27 17:06             ` martin rudalics
2015-12-27 18:00               ` Drew Adams
2015-12-27 18:37                 ` martin rudalics
2015-12-27 19:14                   ` Drew Adams
2015-12-28 10:08                     ` martin rudalics
2015-12-28 10:44                       ` Drew Adams
2015-12-28 18:23                         ` martin rudalics
2015-12-28 18:41                           ` Drew Adams
     [not found]     ` <<43f2b0b2-fafc-43a9-b56a-120b90878cbc@default>
     [not found]       ` <<838u4hk0um.fsf@gnu.org>
     [not found]         ` <<56800C2E.80300@gmx.at>
     [not found]           ` <<83bn9bhna2.fsf@gnu.org>
     [not found]             ` <<1cf60229-6b8c-4c53-96f2-1b8f5d74b80b@default>
     [not found]               ` <<8337unhkwt.fsf@gnu.org>
2015-12-27 18:00                 ` Drew 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

  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=281e9d1f-0853-4498-bd4f-7510213c0cab@default \
    --to=drew.adams@oracle.com \
    --cc=10873@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).