From: Anders Lindgren <andlind@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16856@debbugs.gnu.org, Alan Third <alan@idiocy.org>,
Keith David Bershatsky <esq@lawlist.com>,
David Reitter <david.reitter@gmail.com>
Subject: bug#16856: Enable fringe cursor when *almost* exact_window_width_line_p
Date: Sat, 11 Nov 2017 18:49:03 +0100 [thread overview]
Message-ID: <CABr8ebZ+qdRVh96dpV7-B3NA8Mjty4XcOZMw9C_jLw+EsMjnSg@mail.gmail.com> (raw)
In-Reply-To: <83bmk8ohgn.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Hi!
On Sat, Nov 11, 2017 at 6:25 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> ??? Are you saying that drawing on macOS is not clipped by the
> window's edge?
Yes, when it comes to the cursor, that is correct.
> > When the cursor is moved, the
> > fringe isn't updated, so artefacts are left behind.
>
> I saw no artifacts on the image that was posted.
I just verified that the following recipe (posted in 2016) demonstrates the
problem, on NS. (The original recipe from 2014 no longer works, though).
emacs -Q
(setq truncate-partial-width-windows nil)
C-x 3
C-x o
C-u 37 x
Here, the cursor which is in text area blinks, while the part in the
fringe doesn't.
Wait until the the cursor stop blinking
C-a
Now, the right fringe contains half a cursor.
-- Anders
[-- Attachment #2: Type: text/html, Size: 1033 bytes --]
next prev parent reply other threads:[~2017-11-11 17:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 21:39 bug#16856: 24.3.50; Cursor leaves garbage in fringe (and a request: width of fringes + scroll bar should be full characters) Anders Lindgren
2014-02-24 3:44 ` Eli Zaretskii
2014-02-24 7:41 ` martin rudalics
2014-02-24 10:12 ` Anders Lindgren
2014-02-24 10:53 ` martin rudalics
2014-02-24 15:12 ` Anders Lindgren
2014-02-26 10:15 ` martin rudalics
2014-02-26 12:51 ` Anders Lindgren
2016-05-17 18:30 ` Alan Third
2016-05-17 19:06 ` Anders Lindgren
2016-05-17 21:14 ` bug#16856: [PATCH] Prevent cursor from over-drawing the fringe Alan Third
2016-05-20 19:33 ` Anders Lindgren
2016-05-21 7:35 ` Alan Third
2016-05-21 19:07 ` Anders Lindgren
2016-07-17 6:57 ` bug#16856: 24.3.50; Cursor leaves garbage in fringe David Reitter
2017-11-09 18:50 ` bug#16856: Enable fringe cursor when *almost* exact_window_width_line_p Keith David Bershatsky
2017-11-09 18:58 ` bug#29233: " Keith David Bershatsky
2017-11-09 22:11 ` Alan Third
2017-11-10 7:53 ` bug#16856: " Eli Zaretskii
2017-11-11 16:34 ` Anders Lindgren
2017-11-11 17:25 ` Eli Zaretskii
2017-11-11 17:49 ` Anders Lindgren [this message]
2017-11-11 18:46 ` Alan Third
2017-11-11 20:36 ` Anders Lindgren
2017-11-10 0:31 ` bug#29233: " Keith David Bershatsky
2017-11-11 22:33 ` Keith David Bershatsky
2017-11-12 4:10 ` Eli Zaretskii
2017-12-12 23:24 ` Noam Postavsky
2017-11-09 19:00 ` bug#16856: Cursor leaves garbage in fringe Keith David Bershatsky
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=CABr8ebZ+qdRVh96dpV7-B3NA8Mjty4XcOZMw9C_jLw+EsMjnSg@mail.gmail.com \
--to=andlind@gmail.com \
--cc=16856@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=david.reitter@gmail.com \
--cc=eliz@gnu.org \
--cc=esq@lawlist.com \
/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).