unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: 19422@debbugs.gnu.org
Subject: bug#19422: 25.0.50; `remove-overlays` needs one additional `point` at end of narrowed	region.
Date: Mon, 22 Dec 2014 18:32:01 +0200	[thread overview]
Message-ID: <83r3vrprwe.fsf@gnu.org> (raw)
In-Reply-To: <m2y4q0vr03.wl%esq@lawlist.com>

> Date:  Sun, 21 Dec 2014 09:42:36 -0800
> From:  Keith David Bershatsky <esq@lawlist.com>
> Cc:  19422@debbugs.gnu.org
> 
> In my particular use case, I am narrowing to a region and then inserting an `after-string` overlay at `point-max`:
> 
> (overlay-put (make-overlay (point-max) (point-max)) 'after-string "|")
> 
> I have a minor mode that draws a vertical line that tracks the cursor position and I extend that to window-end or point-max.  The end of the buffer has a different color and a different character overlay depending upon where `point` is --- a leading cushion is used if the vertical column extends beyond the point at the end of the line.

It looks like overlays-in treats EOB specially, and does not treat
(point-max) in the same way.  This is explicitly stated in the doc
string of overlays-in.

I don't know what are the reasons for such a special treatment, and
why a narrowed region doesn't get the same treatment.  I always
thought that Emacs treats both the same.  Perhaps all we need is to
give both the same treatment, and that's it.

Besides that, the doc string of remove-overlays is inaccurate and
misleading; I will take care of that.





  reply	other threads:[~2014-12-22 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21  8:39 bug#19422: 25.0.50; `remove-overlays` needs one additional `point` at end of narrowed region Keith David Bershatsky
2014-12-21 16:45 ` Eli Zaretskii
2014-12-21 17:42 ` Keith David Bershatsky
2014-12-22 16:32   ` Eli Zaretskii [this message]
2021-08-16 13:41     ` Lars Ingebrigtsen

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=83r3vrprwe.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19422@debbugs.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).