From: E Sabof <esabof@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, rgm@gnu.org
Cc: 14170@debbugs.gnu.org
Subject: bug#14170: 24.3; linum won't create all overlays after a folding
Date: Thu, 11 Apr 2013 02:44:41 +0100 [thread overview]
Message-ID: <CAEp6DyYpfLzUigNAaREUkdB-2+o3Cpmr7Ft7Mk+V8on8nRrO=Q@mail.gmail.com> (raw)
In-Reply-To: <CAEp6DybeY9N05rFLvu-M2Bchibw=H_57J=Vv9BYAY+nmMYt3KA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Although I should be able to remove all overlays between a modification and
the end of buffer. This however still leaves the case where I simply scroll
through a large buffer, without making changes, and overlays accumulate.
Evgeni
On Thu, Apr 11, 2013 at 2:37 AM, E Sabof <esabof@gmail.com> wrote:
> The reason I've noticed/reported this bug was because I was working on a
> mode with a similar implementation to linum's, and got the same behavior.
> This is not a linum bug.
>
> On a side note, I would prefer nlinum's approach for my package, but if
> I'm correct it would become slower over time, as it doesn't "GC" overlays.
> And I don't think jit-lock provides an easy method to do it, as it marks
> regions "fontified" (as opposed to "fontified-by-X-function").
>
> Evgeni
>
>
> On Wed, Apr 10, 2013 at 2:02 AM, E Sabof <esabof@gmail.com> wrote:
>
>> nlinum works correctly.
>>
>> Evgeni
>>
>>
>>
>> On Wed, Apr 10, 2013 at 1:38 AM, Stefan Monnier <monnier@iro.umontreal.ca
>> > wrote:
>>
>>> > Steps to reproduce:
>>> > Open emacs -Q
>>> > M-: (progn (linum-mode) (hs-mode))
>>> > Insert a block of comments
>>> > M-x hs-hide-block
>>>
>>> Could you test it with nlinum-mode (available from GNU ELPA)?
>>>
>>>
>>> Stefan
>>>
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 2404 bytes --]
next prev parent reply other threads:[~2013-04-11 1:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 21:33 bug#14170: 24.3; linum won't create all overlays after a folding E Sabof
2013-04-10 0:38 ` Stefan Monnier
2013-04-10 1:02 ` E Sabof
2013-04-10 1:51 ` Glenn Morris
2013-04-12 12:52 ` Eli Zaretskii
2013-04-14 1:21 ` Stefan Monnier
2013-04-14 6:15 ` Eli Zaretskii
2013-04-15 23:00 ` Stefan Monnier
2013-04-16 6:15 ` Eli Zaretskii
2013-04-11 1:37 ` E Sabof
2013-04-11 1:44 ` E Sabof [this message]
2013-04-11 2:50 ` Eli Zaretskii
2013-04-11 3:23 ` E Sabof
2013-04-11 16:14 ` Eli Zaretskii
2013-04-11 13:58 ` Stefan Monnier
[not found] ` <CAEp6DyZQx81yUkxKfqk2O8VJz68xYVs0+_Cii50MG4Wxc6q=rA@mail.gmail.com>
[not found] ` <jwvmwt1ucww.fsf-monnier+emacs@gnu.org>
2013-04-14 1:40 ` E Sabof
2013-04-14 3:16 ` Stefan Monnier
2016-06-09 3:03 ` Noam Postavsky
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='CAEp6DyYpfLzUigNAaREUkdB-2+o3Cpmr7Ft7Mk+V8on8nRrO=Q@mail.gmail.com' \
--to=esabof@gmail.com \
--cc=14170@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@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).