From: martin rudalics <rudalics@gmx.at>
To: Markus Triska <markus.triska@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: something like linum.el ought to be added
Date: Wed, 12 Sep 2007 14:09:36 +0200 [thread overview]
Message-ID: <46E7D700.5080106@gmx.at> (raw)
In-Reply-To: <m1ir6guo95.fsf@gmx.at>
>>Why do you want to update numbers on any but the selected frame
>>here?
>
>
> Because I found cases where the previous command created a frame with
> a buffer that must have its line numbers shown, yet was not selected.
Then you'd have to update line numbers in `after-make-frame-functions'
too.
>>Also, after scrolling it should be sufficient to consider the
>>scrolled window only.
>
>
> No: The scrolled window can use overlays that another window needs.
Not if the other window displays another buffer. For the same buffer
this can be easily handled by giving overlays a window property.
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?
next prev parent reply other threads:[~2007-09-12 12:09 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 [this message]
2007-09-12 12:55 ` Markus Triska
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
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=46E7D700.5080106@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=markus.triska@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 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).