From: Kenichi Handa <handa@m17n.org>
To: emacs-devel@gnu.org
Subject: How to show *Warnings* buffer at startup time?
Date: Wed, 18 Mar 2009 22:22:21 +0900 [thread overview]
Message-ID: <E1Ljviv-0002mh-Jc@etlken> (raw)
I'm going to change create-fontset-from-x-resource
(fontset.el) as this:
@@ -1049,8 +1058,11 @@
(while (setq fontset-spec (x-get-resource (format "fontset-%d" idx)
(format "Fontset-%d" idx)))
(condition-case nil
- (create-fontset-from-fontset-spec fontset-spec t 'noerror)
- (error (message "Fontset-%d: invalid specification in X resource" idx)))
+ (create-fontset-from-fontset-spec fontset-spec t)
+ (error (display-warning
+ 'initialization
+ (format "Fontset-%d: invalid specification in X resource" idx)
+ :warning)))
(setq idx (1+ idx)))))
;;
But the *Warnings* buffer doesn't show up at startup time
even if create-fontset-from-fontset-spec causes an error.
Could someone tell me what is wrong with the above change?
If it is because the X frame is not yet created at that
time, don't we need something like the attached patch?
---
Kenichi Handa
handa@m17n.org
--- startup.el.~1.527.~ 2009-02-23 09:51:02.000000000 +0900
+++ startup.el 2009-03-18 22:16:35.000000000 +0900
@@ -1235,7 +1235,13 @@
(if (and (boundp 'x-session-previous-id)
(stringp x-session-previous-id))
(with-no-warnings
- (emacs-session-restore x-session-previous-id))))
+ (emacs-session-restore x-session-previous-id)))
+
+ (let ((warning-buf (get-buffer "*Warnings*")))
+ (if (and warning-buf
+ (not (get-buffer-window warning-buf))
+ (> (buffer-size warning-buf) 0))
+ (display-buffer warning-buf))))
(defcustom initial-scratch-message (purecopy "\
;; This buffer is for notes you don't want to save, and for Lisp evaluation.
next reply other threads:[~2009-03-18 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 13:22 Kenichi Handa [this message]
2009-03-18 13:28 ` How to show *Warnings* buffer at startup time? Lennart Borgman
2009-03-19 0:39 ` Kenichi Handa
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=E1Ljviv-0002mh-Jc@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@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 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).