From: Markus Triska <markus.triska@gmx.at>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: something like linum.el ought to be added
Date: Wed, 12 Sep 2007 14:55:28 +0200 [thread overview]
Message-ID: <m1ps0oavr3.fsf@gmx.at> (raw)
In-Reply-To: <46E7D700.5080106@gmx.at> (martin rudalics's message of "Wed\, 12 Sep 2007 14\:09\:36 +0200")
martin rudalics <rudalics@gmx.at> writes:
> Then you'd have to update line numbers in `after-make-frame-functions'
Yes, that would also be an option; the current way subsumes more
specialized cases like this with little overhead.
> An aside: Sometimes configuration, buffer text, and some window start
> position change within one and the same command. Did you check whether
> this cause line number updating run two, three times after the command?
No; generally, I found updates to be so fast that this, even if it
should occur, is not a concern. Also, when line numbers for a window
are updated twice in a row, all overlays are already created and in
the right place, so it is even less noticable than starting anew.
next prev parent reply other threads:[~2007-09-12 12:55 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 10:04 something like linum.el ought to be added Joe Wells
2007-09-09 10:43 ` Leo
2007-09-10 16:53 ` Richard Stallman
2007-09-10 17:34 ` Markus Triska
2007-09-10 20:00 ` David Kastrup
2007-09-11 18:15 ` Markus Triska
2007-09-11 20:27 ` Davis Herring
2007-09-11 21:24 ` Markus Triska
2007-09-12 8:47 ` Richard Stallman
2007-09-12 9:14 ` Joe Wells
2007-09-12 9:21 ` David Kastrup
2007-09-12 18:52 ` Richard Stallman
2007-09-13 17:06 ` Markus Triska
2007-09-14 13:59 ` Stefan Monnier
2007-09-14 16:15 ` Joe Wells
2007-09-14 17:20 ` Stefan Monnier
[not found] ` <m1bqajgpc8.fsf_-_@gmx.at>
2007-10-28 18:46 ` motivation for recent bug reports on overlays and properties like before-string, display, after-string, and face (was: linum.el and display properties) Joe Wells
2007-09-15 2:09 ` something like linum.el ought to be added Richard Stallman
2007-09-14 15:04 ` brianjiang
2007-09-14 15:56 ` Markus Triska
2007-09-15 14:46 ` Juanma Barranquero
2007-09-15 16:12 ` Markus Triska
2007-09-15 16:54 ` Juanma Barranquero
2007-09-11 20:30 ` Richard Stallman
2007-09-11 20:31 ` Richard Stallman
2007-09-11 23:48 ` Markus Triska
2007-09-12 9:19 ` martin rudalics
2007-09-12 11:17 ` Markus Triska
2007-09-12 12:09 ` martin rudalics
2007-09-12 12:55 ` Markus Triska [this message]
2007-09-15 14:24 ` Juanma Barranquero
2007-09-15 16:01 ` Markus Triska
2007-09-15 16:14 ` Juanma Barranquero
2007-09-16 5:34 ` Richard Stallman
2007-09-16 15:57 ` Markus Triska
2007-09-17 3:58 ` Richard Stallman
2007-09-16 23:04 ` Stefan Monnier
2007-09-17 3:58 ` Richard Stallman
2007-09-17 5:12 ` brianjiang
2007-09-17 13:49 ` Stefan Monnier
2007-09-17 13:17 ` Stefan Monnier
2007-09-17 22:24 ` Richard Stallman
2007-09-18 0:49 ` Stefan Monnier
2007-09-18 3:30 ` Richard Stallman
2007-09-18 14:31 ` Stefan Monnier
2007-09-11 7:08 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1ps0oavr3.fsf@gmx.at \
--to=markus.triska@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.