unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: How to show *Warnings* buffer at startup time? [Re: Pretest next week]
Date: Fri, 15 May 2009 13:00:36 +0900	[thread overview]
Message-ID: <E1M4ob6-0007Ob-TA@etlken> (raw)
In-Reply-To: <8763g39jwd.fsf@cyd.mit.edu> (message from Chong Yidong on Thu, 14 May 2009 22:31:30 -0400)

In article <8763g39jwd.fsf@cyd.mit.edu>, Chong Yidong <cyd@stupidchicken.com> writes:

> Hi all,
> I'm planning to make the 23.0.94 pretest next Wednesday, the 20th.

> The release seems to be coming along nicely; the font code seems to have
> converged at last (with the exception of #2667), and most of the
> documentation work is now done.  I'm thinking of cutting the branch
> after the next pretest, so that some of the pent-up patches can start
> being applied.  I have not, however, discussed this in detail with
> Stefan yet.  If you like, please feel free to weigh in with opinions
> and/or concerns about the release process.

I've just noticed that the subject issure is not yet
settled.  I think this is not a serious one but the attached
patch to startup.el is simple and it helps people identify a
fontset problem earlier.

---
Kenichi Handa
handa@m17n.org


In article <E1Ljviv-0002mh-Jc@etlken>, Kenichi Handa <handa@m17n.org> writes:

> 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.







  reply	other threads:[~2009-05-15  4:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15  2:31 Pretest next week Chong Yidong
2009-05-15  4:00 ` Kenichi Handa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-15 15:02 How to show *Warnings* buffer at startup time? [Re: Pretest next week] Chong Yidong
2009-05-16  1:02 ` Kenichi Handa
2009-05-16 21:41 ` Richard M Stallman
2009-05-17  2:57   ` Chong Yidong
2009-05-17 17:23     ` Richard M Stallman
2009-05-17 18:47       ` Chong Yidong

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=E1M4ob6-0007Ob-TA@etlken \
    --to=handa@m17n.org \
    --cc=cyd@stupidchicken.com \
    --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).