all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Issue with font rendering caused by one of the commits in last 48 hrs #master
Date: Sat, 21 Jan 2017 17:43:59 +0000	[thread overview]
Message-ID: <CAFyQvY3cOD+bO4_N4G6vyNXzN-qe--5U-th8LbYfXGFV=HSvxw@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY096uosF01cyXgTKGMksE1XXk-ec7SS44gHnAHJmxnaSw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2890 bytes --]

Hello everyone,

I apologize, but I cannot recreate the issue I saw last night. It's very
strange given that the 'bad' build and 'good' build were installed with
different --prefix flags. So they are 'make install'ed in completely
separate directories.

Though my building directory is the same.

Here are the sequence of events:

1. I update my build to
    e5e42ce diff-hunk-kill independent of point inside headers
2. Start a fresh emacsclient session, and see that issue.
3. I keep that session open, checkout the branch that last worked fine for
me:
    8c0fcaf Avoid inefficient regex in diff-refine-hunk
4. I take a screenshot of the bad build and kill that session.
5. Start another fresh emacsclient session using the build of the 'good'
branch.
6. And everything looks good again.

Sorry guys, as the issue magically went away, I fear it will arrive again.
Will open a bug report next time with more info as possible.

======
On Sat, Jan 21, 2017 at 9:02 AM Noam Postavsky <
npostavs@users.sourceforge.net> wrote:

I can't see a plausible way any these could affect the font, are you
sure it wasn't the commit I pushed last night [1: 6a788d2]?

1: 2017-01-20 23:36:26 -0500 6a788d2fc18c23dcfc5d0352649b2f690e9cbff7
  Don't wait for frame to become visible


Thanks for the reply, yes I confirmed that was not the case. This was my
emacs build info:

===
Emacs version: GNU Emacs 26.0.50.20 (x86_64-unknown-linux-gnu, GTK+ Version
2.24.23)
 of 2017-01-20, built using commit e5e42cefd7f2eb47d2c8660a7a317e8b08d36a82.

./configure options:
  --with-modules --prefix=/home/kmodi/usr_local/apps/6/emacs/master
'--program-transform-name=s/^ctags$/ctags_emacs/' 'CPPFLAGS=-fgnu89-inline
-I/home/kmodi/usr_local/6/include -I/usr/include/freetype2 -I/usr/include'
'CFLAGS=-ggdb3 -O0' 'CXXFLAGS=-ggdb3 -O0'
'LDFLAGS=-L/home/kmodi/usr_local/6/lib -L/home/kmodi/usr_local/6/lib64
-ggdb3'

Features:
  XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GCONF GSETTINGS
NOTIFY ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE LIBOTF XFT ZLIB
TOOLKIT_SCROLL_BARS GTK2 X11 MODULES
===

>> Tino Calancha
> I don't see this issue in my box.
> Is it feasible for you to perform a git bisect?

Sorry, that's what I was just trying to do, but cannot recreate the issue.
:(

>> Eli Zaretskii

> The only thing I can glean from the images is that the "good" version
uses a fixed-pitch
> face, while the "bad" one uses a variable-pitch face.

It's the exact same font and exact same emacs config.

> E.g., is the same font used in both cases?

Yes.

> What do you see in the Custom buffer if you try to customize the face
used by this display?

Ah! Sorry, should have done that. But cannot recreate the issue. Sorry.

> (I also wonder why you post here and not to the bug tracker.)

Will do that next time. I did not see an "error message" or debug info to
report other than the screenshot.

-- 

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 8322 bytes --]

      parent reply	other threads:[~2017-01-21 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-21  5:45 Issue with font rendering caused by one of the commits in last 48 hrs #master Kaushal Modi
2017-01-21 11:08 ` Tino Calancha
2017-01-21 12:24 ` Eli Zaretskii
2017-01-21 14:02 ` Noam Postavsky
     [not found]   ` <CAFyQvY096uosF01cyXgTKGMksE1XXk-ec7SS44gHnAHJmxnaSw@mail.gmail.com>
2017-01-21 17:43     ` Kaushal Modi [this message]

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='CAFyQvY3cOD+bO4_N4G6vyNXzN-qe--5U-th8LbYfXGFV=HSvxw@mail.gmail.com' \
    --to=kaushal.modi@gmail.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 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.