unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 14170@debbugs.gnu.org
Subject: bug#14170: 24.3; linum won't create all overlays after a folding
Date: Fri, 12 Apr 2013 15:52:22 +0300	[thread overview]
Message-ID: <834nfbap2x.fsf@gnu.org> (raw)
In-Reply-To: <jwmwt72lvk.fsf@fencepost.gnu.org>

> From: Glenn Morris <rgm@gnu.org>
> Date: Tue, 09 Apr 2013 21:51:59 -0400
> 
> E Sabof wrote:
> 
> > nlinum works correctly.
> 
> This is the answer to most recent bug reports involving linum, as I
> recall. Will nlinum replace linum at some point?

Btw, if nlinum is our response to the problems in linum, then nlinum
should be a bit more friendly to bidirectional text, and determine
whether to put numbers on the left or right margin by looking at what
current-bidi-paragraph-direction returns.  (Yes, this means that if
some paragraphs are L2R and others R2L, some numbers will be on the
left, while others on the right.)





  reply	other threads:[~2013-04-12 12:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 21:33 bug#14170: 24.3; linum won't create all overlays after a folding E Sabof
2013-04-10  0:38 ` Stefan Monnier
2013-04-10  1:02   ` E Sabof
2013-04-10  1:51     ` Glenn Morris
2013-04-12 12:52       ` Eli Zaretskii [this message]
2013-04-14  1:21         ` Stefan Monnier
2013-04-14  6:15           ` Eli Zaretskii
2013-04-15 23:00             ` Stefan Monnier
2013-04-16  6:15               ` Eli Zaretskii
2013-04-11  1:37     ` E Sabof
2013-04-11  1:44       ` E Sabof
2013-04-11  2:50       ` Eli Zaretskii
2013-04-11  3:23         ` E Sabof
2013-04-11 16:14           ` Eli Zaretskii
2013-04-11 13:58       ` Stefan Monnier
     [not found]         ` <CAEp6DyZQx81yUkxKfqk2O8VJz68xYVs0+_Cii50MG4Wxc6q=rA@mail.gmail.com>
     [not found]           ` <jwvmwt1ucww.fsf-monnier+emacs@gnu.org>
2013-04-14  1:40             ` E Sabof
2013-04-14  3:16               ` Stefan Monnier
2016-06-09  3:03 ` Noam Postavsky

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=834nfbap2x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14170@debbugs.gnu.org \
    --cc=rgm@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.
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).