From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 16661@debbugs.gnu.org
Subject: bug#16661: 24.3.50; standalone minibuffer frame gets renamed with name of aother frame
Date: Sat, 26 Dec 2015 14:27:57 +0100 [thread overview]
Message-ID: <87a8ox49wi.fsf@gnus.org> (raw)
In-Reply-To: <ba7e3611-56ac-440c-8495-49c190a8e119@default> (Drew Adams's message of "Sat, 22 Feb 2014 08:41:56 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
> The buffer displayed in the minibuffer window is typically named
> ` *Minibuf-N*', N=0,1,2... It is still named this way with my
> setup. The only thing I change is the `name' parameter of the
> frame.
>
> I will try removing the `window-setup-hook' renaming, to see whether
> that makes a difference.
Are you still seeing problems in this area? If so, please try to create
a recipe starting from -Q.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2015-12-26 13:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<97c44b41-de36-472b-833d-3b0d1ac4c912@default>
[not found] ` <<e1f6b83f-5c4c-4b4b-93c0-cec70e8f4198@default>
[not found] ` <<831tzgypbp.fsf@gnu.org>
2014-02-06 21:06 ` bug#16661: 24.3.50; standalone minibuffer frame gets renamed with name of aother frame Drew Adams
2014-02-07 7:09 ` Eli Zaretskii
[not found] ` <<ea23c21d-4e2d-4a93-865f-763ae2f9df19@default>
[not found] ` <<83zjm3xuu8.fsf@gnu.org>
2014-02-07 17:25 ` Drew Adams
2014-02-14 15:51 ` Drew Adams
2014-02-14 18:23 ` Eli Zaretskii
[not found] ` <<f103a66c-04d7-45f2-92a4-25687523ec8b@default>
[not found] ` <<e5b84d2d-38c3-49ec-be38-e91738da7c66@default>
[not found] ` <<83vbwhblkp.fsf@gnu.org>
2014-02-16 17:14 ` Drew Adams
2014-02-19 21:06 ` Drew Adams
2014-02-20 16:29 ` Eli Zaretskii
[not found] ` <<3febc9ab-b7b2-443c-8ec8-eaaf28ace468@default>
[not found] ` <<dde01fb4-f798-45d3-9ec6-3f4f1e7d16f5@default>
[not found] ` <<8338jd693l.fsf@gnu.org>
2014-02-22 4:23 ` Drew Adams
2014-02-22 8:55 ` Eli Zaretskii
2014-02-24 20:14 ` Stefan Monnier
2014-02-24 21:34 ` Drew Adams
[not found] ` <<16fff663-6320-4d96-a575-e3c368472a0a@default>
[not found] ` <<83a9dj4jc3.fsf@gnu.org>
2014-02-22 16:41 ` Drew Adams
2015-12-26 13:27 ` Lars Ingebrigtsen [this message]
2015-12-26 16:22 ` Drew Adams
[not found] <<6a126f7a-27e5-4ada-a6b3-1f3c1c19aca0@default>
[not found] ` <<831tzg22wn.fsf@gnu.org>
2014-02-06 6:15 ` Drew Adams
2014-02-06 18:42 ` Drew Adams
2014-02-06 20:10 ` Eli Zaretskii
2014-02-07 1:04 ` Juanma Barranquero
2014-02-07 2:36 ` Drew Adams
2014-02-07 2:49 ` Juanma Barranquero
2014-02-07 3:08 ` Drew Adams
2014-02-07 3:21 ` Juanma Barranquero
2014-02-05 23:33 Drew Adams
2014-02-06 6:03 ` Eli Zaretskii
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=87a8ox49wi.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=16661@debbugs.gnu.org \
--cc=drew.adams@oracle.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).