From: "Drew Adams" <drew.adams@oracle.com>
To: <117@emacsbugs.donarmstrong.com>, "'Jason Rumney'" <jasonr@gnu.org>
Subject: bug#117: bug 117: messed up frame parameters
Date: Sat, 30 Aug 2008 07:38:21 -0700 [thread overview]
Message-ID: <003a01c90aae$0d61cbb0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <002401c9091f$55038520$c2b22382@us.oracle.com>
> Sorry, I was confused. I was thinking this was an Emacs 23
> pretest. These problems still exist in Emacs 23. :-(
FYI - I just checked with a new build of 8-29, and the problems still exist.
* Duplicate and contradictory frame params.
* Fringe (left and right) on first frame, even though default-frame-alist
specifies no fringe. No fringe problem with subsequent frames.
* Bizarre, unreadable symbols, intead of normal alphabetic characters, in tabbar
tabs and Info headings.
* Frames not getting redisplayed, so uncovering a frame that was overlapped by
another (or by a non-Emacs window-mgr window) shows the overlapped part as blank
(until you select the frame and do C-l).
* Tool bar showing in new frames even though tool-bar mode is turned off. Oddly
enough, if I do C-x 5 f foo.el, even in the same file foo.el, the tool bar shows
up, but if I instead do C-x 5 2, the tool bar does not show up.
HTH.
next prev parent reply other threads:[~2008-08-30 14:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 15:02 bug#117: bug 117: messed up frame parameters Drew Adams
2008-07-08 20:54 ` Jason Rumney
2008-07-09 15:27 ` Drew Adams
2008-08-02 20:36 ` Drew Adams
2008-08-02 21:07 ` Jason Rumney
2008-08-02 22:08 ` Drew Adams
2008-08-27 16:41 ` Drew Adams
2008-08-28 15:04 ` Drew Adams
2008-08-30 14:38 ` Drew Adams [this message]
2008-10-31 21:05 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2008-12-28 1:32 Chong Yidong
2008-12-28 8:02 ` Drew Adams
2008-12-28 9:00 ` Chong Yidong
2008-12-28 18:15 ` Drew Adams
2008-12-28 19:22 grischka
2008-12-28 19:27 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003a01c90aae$0d61cbb0$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=117@emacsbugs.donarmstrong.com \
--cc=jasonr@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.