From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Alp Aker <alptekin.aker@gmail.com>
Cc: help-gnu-emacs@gnu.org,
Andrew Michael Levin <andrew.m.levin@vanderbilt.edu>
Subject: Re: line numbers
Date: Mon, 4 Jun 2012 17:28:31 +0200 [thread overview]
Message-ID: <CAMXnza1ERvnJNcuH019G2yjuuBkoazqE5bETRHe=Gy-UbC-ecg@mail.gmail.com> (raw)
In-Reply-To: <CACxch4ob1zTwuAmbFNn08tsXMjUFdNiOVoD-+UhBZTBnOC6GaA@mail.gmail.com>
On Mon, Jun 4, 2012 at 4:56 PM, Alp Aker <alptekin.aker@gmail.com> wrote:
> On Mon, Jun 4, 2012 at 9:55 AM, suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
>
>> A caveat. As far as I know linum mode shows line numbers using overlays.
>> This can be very expensive if the file is large (e.g. a log file, a
>> journal file etc). If possible I would advice the OP to adapt to not
>> using in-buffer line numbers and rely on line-number-mode for line
>> numbers on the mode line instead.
>
> linum-mode only creates as many overlays as is needed to cover that
> portion of a buffer that's visible at a given time; it removes them
> from locations that are no longer visible. As a result, its
> performance is independent of buffer size.
In the real world things can be very different. ;)
AFAIR, there is a long history of Heisenbug like issue with linum-mode
and large org-mode files. If you are interested you can check the
org-mode archive.
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2012-06-04 15:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 17:36 line numbers Andrew Michael Levin
2012-06-03 17:55 ` Michaël Bruneel
2012-06-03 18:18 ` Mark Skilbeck
2012-06-03 19:02 ` Andrew Michael Levin
2012-06-03 19:08 ` Drew Adams
2012-06-04 5:57 ` Bob Proulx
2012-06-04 13:55 ` suvayu ali
2012-06-04 14:56 ` Alp Aker
2012-06-04 15:28 ` suvayu ali [this message]
2012-06-04 6:30 ` Jai Dayal
2012-06-04 13:51 ` suvayu ali
2012-06-04 16:07 ` Jai Dayal
2012-06-04 16:15 ` suvayu ali
2012-06-04 16:24 ` Drew Adams
[not found] <mailman.2202.1338745946.855.help-gnu-emacs@gnu.org>
2012-06-03 19:36 ` Dan Espen
2012-06-04 2:23 ` rusi
2012-06-04 6:23 ` Christian Kellermann
-- strict thread matches above, loose matches on Subject: below --
2006-04-30 22:11 Gary Wessle
2006-05-01 2:43 ` Giorgos Keramidas
2006-05-01 3:55 ` Cameron Desautels
[not found] ` <mailman.1166.1146455721.9609.help-gnu-emacs@gnu.org>
2006-05-02 9:42 ` Gary Wessle
2006-05-01 6:33 ` Fredrik Bulow
2006-05-01 6:39 ` Burton Samograd
2003-01-16 17:24 andrew.maguire
2003-01-07 4:33 Matthew Low
2003-01-07 8:10 ` Benjamin Lewis
2003-01-07 20:17 ` Tuomo Takkula
2003-01-07 20:43 ` Benjamin Lewis
2003-01-13 8:44 ` Lee Sau Dan
2003-01-07 22:27 ` Bruce Korb
2003-01-09 2:45 ` Matthew Low
2003-01-09 5:18 ` Benjamin Lewis
[not found] ` <mailman.42.1041986128.21513.help-gnu-emacs@gnu.org>
2003-01-08 12:12 ` Reiner Steib
2003-01-13 8:44 ` Lee Sau Dan
2003-01-14 18:27 ` Kevin Rodgers
2003-01-20 7:50 ` Lee Sau Dan
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='CAMXnza1ERvnJNcuH019G2yjuuBkoazqE5bETRHe=Gy-UbC-ecg@mail.gmail.com' \
--to=fatkasuvayu+linux@gmail.com \
--cc=alptekin.aker@gmail.com \
--cc=andrew.m.levin@vanderbilt.edu \
--cc=help-gnu-emacs@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.
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).