From: Markus Triska <markus.triska@gmx.at>
To: mark.lillibridge@hp.com
Cc: lekktu@gmail.com, 5042@emacsbugs.donarmstrong.com
Subject: bug#5042: 23.1; linum-mode gives incorrect line numbers with narrowed buffers
Date: Fri, 08 Jan 2010 00:30:28 +0100 [thread overview]
Message-ID: <m2wrzta3xn.fsf@gmx.at> (raw)
In-Reply-To: 201001070538.o075cpux020583@mailhub-pa1.hpl.hp.com
Mark Lillibridge <mark.lillibridge@hp.com> writes:
> waiting on your opinion.
In my opinion, a more general solution than only for linum.el would be
best, one that also makes for example line-number-mode show line numbers
that work as expected with M-x goto-line RET also for narrowed buffers.
Ideally, it should work without having to customize each of these
features (and new modes in the future) separately. I think a promising
suggestion (found in this thread) is to generalise narrowing itself,
possibly with a single new customization option instead of many.
next prev parent reply other threads:[~2010-01-07 23:30 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
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 [this message]
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=m2wrzta3xn.fsf@gmx.at \
--to=markus.triska@gmx.at \
--cc=5042@debbugs.gnu.org \
--cc=5042@emacsbugs.donarmstrong.com \
--cc=lekktu@gmail.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.