From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Richard Stanton <stanton@haas.berkeley.edu>
Cc: "11052@debbugs.gnu.org" <11052@debbugs.gnu.org>
Subject: bug#11052: 24.0.94; Display problem under OS X Lion
Date: Sat, 31 Mar 2012 19:57:28 +0200 [thread overview]
Message-ID: <B4732EAE-3E8B-42BD-B981-28F8B7FF4E06@swipnet.se> (raw)
In-Reply-To: <40C7B1BFC291ED4E9D10436D07736A334702B5FFCF@EXMAIL7.haas.uc.berkeley.edu>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
Hello.
20 mar 2012 kl. 18:52 skrev Richard Stanton:
> The truncated numbers and line of extra pixels both go away if you execute M-x fringe-mode -> no-fringes, so I suspect a counter in the left-fringe code may be off by a few pixels somewhere.
You are correct, there is some strange adjustment going on in ns_draw_fringe_bitmap:
/* NS-specific: move internal border inside fringe */
int x = p->bx < 0 ? p->x : p->bx;
int wd = p->bx < 0 ? p->wd : p->nx;
BOOL fringeOnVeryLeft
= x - WINDOW_LEFT_SCROLL_BAR_COLS (w) * WINDOW_FRAME_COLUMN_WIDTH (w)
- FRAME_INTERNAL_BORDER_WIDTH (f) < 10;
BOOL fringeOnVeryRight
= FRAME_PIXEL_WIDTH (f) - x - wd - FRAME_INTERNAL_BORDER_WIDTH (f)
- WINDOW_RIGHT_SCROLL_BAR_COLS (w) * WINDOW_FRAME_COLUMN_WIDTH (w) < 10;
int xAdjust = FRAME_INTERNAL_BORDER_WIDTH (f) *
(fringeOnVeryLeft ? -1 : (fringeOnVeryRight ? 1 : 0));
Now, if you set xAdjust unconditionally to zero, the problem goes away. I don't yet know the rationale for this. It may be something that was needed at some point, or is needed on some systems. What OSX version are you running?
Jan D.
[-- Attachment #2: Type: text/html, Size: 2608 bytes --]
next prev parent reply other threads:[~2012-03-31 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 16:55 bug#11052: 24.0.94; Display problem under OS X Lion Richard Stanton
2012-03-20 17:52 ` Richard Stanton
2012-03-31 17:57 ` Jan Djärv [this message]
2012-03-31 23:10 ` Richard Stanton
2012-04-01 13:38 ` Jan Djärv
2012-09-08 12:49 ` Jan Djärv
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=B4732EAE-3E8B-42BD-B981-28F8B7FF4E06@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=11052@debbugs.gnu.org \
--cc=stanton@haas.berkeley.edu \
/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.