unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dalanicolai <dalanicolai@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: displaying margins leads to Emacs hanging
Date: Sat, 25 Feb 2023 15:42:12 +0200	[thread overview]
Message-ID: <834jr9lv4b.fsf@gnu.org> (raw)
In-Reply-To: <CACJP=3=ewgNbEJDXBO2t60by_BBeMsvwy2Hi4hs5nA009XOs6A@mail.gmail.com> (message from dalanicolai on Sat, 25 Feb 2023 14:17:24 +0100)

> From: dalanicolai <dalanicolai@gmail.com>
> Date: Sat, 25 Feb 2023 14:17:24 +0100
> Cc: emacs-devel@gnu.org
> 
> This is great! Indeed, it works perfectly now.
> I think using the margins is just much more elegant.
> 
> Although, I might have read about this behavior somewhere,
> obviously, it was not clear to me that `erase-buffer` does not
> remove the overlays. Maybe a warning/reminder about this could
>  be added in the 'erase-buffer' docstring? What do you think?
> I would be happy to create a patch for that (if desired).

This is not related to erasing a buffer, it is related to deleting
text "covered" by the overlay.  What happens in that case depends on
the 'evaporate' property of the overlay, which is already described in
the ELisp manual, see the node "Overlay Properties" there.



  reply	other threads:[~2023-02-25 13:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 19:29 displaying margins leads to Emacs hanging dalanicolai
2023-02-24 19:41 ` Eli Zaretskii
2023-02-24 20:26   ` dalanicolai
2023-02-24 20:29     ` Eli Zaretskii
2023-02-24 20:41       ` dalanicolai
2023-02-24 20:53         ` dalanicolai
2023-02-24 21:19           ` dalanicolai
2023-02-24 21:43             ` dalanicolai
2023-02-25 10:51           ` Eli Zaretskii
2023-02-25 13:17             ` dalanicolai
2023-02-25 13:42               ` Eli Zaretskii [this message]
2023-03-06 22:51                 ` dalanicolai
2023-02-24 21:25         ` Eli Zaretskii
2023-02-24 21:41           ` dalanicolai

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=834jr9lv4b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dalanicolai@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 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).