From: martin rudalics <rudalics@gmx.at>
To: rms@gnu.org
Cc: 931@emacsbugs.donarmstrong.com, michael_heerdegen@web.de
Subject: bug#931: 23.0.60; Bug in bytecomp.el: displaying warnings
Date: Wed, 10 Sep 2008 11:23:12 +0200 [thread overview]
Message-ID: <48C79200.2000708@gmx.at> (raw)
In-Reply-To: <E1KcyJx-0002xV-VV@fencepost.gnu.org>
> I suppose the byte-compiler should either refrain from using
> `display-warning'
>
> That would be very drastic and cause a lot of inconvenience
> in the normal situation where there is no bug!
I obviously meant use something different instead of `display-warning'.
> or, if `pop-up-windows' and `pop-up-frames' are nil,
> not display a warning until compilation is complete.
>
> The solution that occurs to me is that `display-warning' should
> bind `pop-up-windows' to t in that case.
This would (1) ignore a user preference and (2) not work when the window
can't be split for some reason.
martin
next prev parent reply other threads:[~2008-09-10 9:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwvljxxgn4j.fsf-monnier+emacsbugreports@gnu.org>
2008-09-08 19:35 ` bug#931: 23.0.60; Bug in bytecomp.el: displaying warnings Michael Heerdegen
2008-09-08 21:12 ` martin rudalics
2008-09-09 8:11 ` Richard M. Stallman
2008-09-10 9:23 ` martin rudalics [this message]
2008-09-10 20:46 ` Richard M. Stallman
2008-09-11 8:53 ` martin rudalics
2008-09-09 14:33 ` Stefan Monnier
2008-09-10 9:23 ` martin rudalics
2008-09-10 16:24 ` Stefan Monnier
2008-09-10 17:37 ` martin rudalics
2008-09-11 1:52 ` Stefan Monnier
2008-09-11 8:53 ` martin rudalics
2008-09-12 16:30 ` Stefan Monnier
2008-09-12 18:04 ` martin rudalics
2008-09-12 20:00 ` bug#931: marked as done (23.0.60; Bug in bytecomp.el: displaying warnings) 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=48C79200.2000708@gmx.at \
--to=rudalics@gmx.at \
--cc=931@emacsbugs.donarmstrong.com \
--cc=michael_heerdegen@web.de \
--cc=rms@gnu.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 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.