From: Keith David Bershatsky <esq@lawlist.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21301@debbugs.gnu.org
Subject: bug#21301: 25.0.50; Emacs Trunk: Fringe bitmaps confuse foreground/background colors.
Date: Sat, 29 Aug 2015 14:52:34 -0700 [thread overview]
Message-ID: <m27fodsqxp.wl%esq@lawlist.com> (raw)
In-Reply-To: <m2pp2j2f62.wl%esq@lawlist.com>
Here is the workaround until a fix is found:
Step number 1: Revert b00168e833ccca1b5c0eebe56688ec44e0efabe7
Step number 2: Revert 67a878f78f879ce534232408c34dd11f42dd802b
Using the above-steps, I am able to build Emacs to completion and bug#21301 is gone.
Thank you for all your help -- greatly appreciated! :)
Keith
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
At Sat, 29 Aug 2015 23:18:12 +0300,
Eli Zaretskii wrote:
>
> ***
>
> Great, thanks. So we now know for sure that 67a878f _was_ the
> culprit.
>
> I hope someone knowledgeable about NS and OS X will be able to tell
> what's wrong with that change, and how to fix it.
next prev parent reply other threads:[~2015-08-29 21:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 20:31 bug#21301: 25.0.50; Emacs Trunk: Fringe bitmaps confuse foreground/background colors Keith David Bershatsky
2015-08-21 13:47 ` Eli Zaretskii
2015-08-22 23:45 ` Keith David Bershatsky
2015-08-23 2:43 ` Eli Zaretskii
2015-08-23 14:05 ` Eli Zaretskii
2015-08-23 17:07 ` Keith David Bershatsky
2015-08-23 17:11 ` Eli Zaretskii
2015-08-23 23:41 ` Glenn Morris
2015-08-29 4:41 ` Keith David Bershatsky
2015-08-29 7:48 ` Eli Zaretskii
2015-08-29 16:15 ` Keith David Bershatsky
2015-08-29 16:34 ` Eli Zaretskii
2015-08-29 19:51 ` Keith David Bershatsky
2015-08-29 20:18 ` Eli Zaretskii
2015-08-29 21:52 ` Keith David Bershatsky [this message]
2015-10-08 21:26 ` Mustafa Kocaturk
2015-11-04 6:13 ` bug#21301: Fixed bug 21301 Anders Lindgren
2015-11-04 16:40 ` Glenn Morris
2015-11-04 16:51 ` Anders Lindgren
2015-11-04 16:53 ` bug#21301: Fwd: " Anders Lindgren
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=m27fodsqxp.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=21301@debbugs.gnu.org \
--cc=eliz@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).