From: Juanma Barranquero <lekktu@gmail.com>
To: mark.lillibridge@hp.com
Cc: 5042@emacsbugs.donarmstrong.com
Subject: bug#5042: 23.1; linum-mode gives incorrect line numbers with narrowed buffers
Date: Thu, 10 Dec 2009 12:41:21 +0100 [thread overview]
Message-ID: <f7ccd24b0912100341q62e2259as90a1a26bbda73739@mail.gmail.com> (raw)
In-Reply-To: <200912100534.nBA5YSva008256@mailhub-pa1.hpl.hp.com>
On Thu, Dec 10, 2009 at 06:34, Mark Lillibridge <mark.lillibridge@hp.com> wrote:
> The entire point of having line numbers is that they correspond to
> something useful. Either an external program's line number (e.g., a gcc
> error number) or an internal Emacs notion such as that provided by
> goto-line. The current behavior does neither.
Well, there are many definitions of useful. I find the current
behavior useful, because my main use of linum is knowing at a glance
how many lines there are in the file (or in the region, if narrowing
is in effect).
> Note that other line numbering modes like wb-line-number implement
> the behavior that I describe as correct.
Yes. But linum allows you to use line numbers in a quite more flexible
way. You could do
(defvar num-of-lines nil)
(defvar num-format nil)
(make-variable-buffer-local 'num-of-lines)
(make-variable-buffer-local 'num-format)
(add-hook 'linum-before-numbering-hook
(lambda ()
(save-restriction
(widen)
(let ((lines (count-lines (point-min) (point-max))))
(setq num-format (format "%%%dd" (length
(int-to-string lines))))
(setq num-of-lines (1+ lines))))))
(setq linum-format
(lambda (line)
(format num-format (- num-of-lines line))))
if you fancied numbering lines in reverse, for example.
Juanma
next prev parent reply other threads:[~2009-12-10 11:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 0:39 bug#5042: 23.1; linum-mode gives incorrect line numbers with narrowed buffers Mark Lillibridge
2009-12-01 0:32 ` Juanma Barranquero
2009-12-10 5:34 ` Mark Lillibridge
2009-12-10 11:41 ` Juanma Barranquero [this message]
2009-12-21 6:59 ` Mark Lillibridge
2009-12-21 10:37 ` Juanma Barranquero
2009-12-21 15:50 ` Drew Adams
2009-12-23 20:49 ` Mark Lillibridge
2009-12-23 21:01 ` Drew Adams
2009-12-23 21:44 ` Mark Lillibridge
2009-12-24 3:49 ` Stefan Monnier
2009-12-29 7:02 ` Kevin Rodgers
2010-01-07 5:38 ` Mark Lillibridge
2010-01-07 23:30 ` Markus Triska
2010-01-10 1:32 ` Mark Lillibridge
2010-01-10 1:56 ` Juanma Barranquero
2010-01-16 22:08 ` Mark Lillibridge
2010-01-16 23:03 ` Juanma Barranquero
2010-01-23 23:28 ` Mark Lillibridge
2010-01-24 0:07 ` Drew Adams
2010-02-03 5:01 ` Mark Lillibridge
2010-01-24 9:21 ` Juanma Barranquero
2010-01-10 2:05 ` Lennart Borgman
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=f7ccd24b0912100341q62e2259as90a1a26bbda73739@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=5042@emacsbugs.donarmstrong.com \
--cc=mark.lillibridge@hp.com \
/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.