From: Eli Zaretskii <eliz@gnu.org>
To: lekktu@gmail.com, contrib@chenlevy.com
Cc: 8867-done@debbugs.gnu.org
Subject: bug#8867: 24.0.50; bidi-display-reordering + lino-mode + move-up = beginning of buffer
Date: Thu, 14 Jul 2011 20:53:35 +0300 [thread overview]
Message-ID: <83fwm8iw9s.fsf@gnu.org> (raw)
In-Reply-To: <83fwnaxypp.fsf@gnu.org>
> Date: Thu, 16 Jun 2011 06:05:38 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: contrib@chenlevy.com, 8867@debbugs.gnu.org
>
> > From: Juanma Barranquero <lekktu@gmail.com>
> > Date: Thu, 16 Jun 2011 04:00:47 +0200
> > Cc: Chen Levy <contrib@chenlevy.com>, 8867@debbugs.gnu.org
> >
> > On Thu, Jun 16, 2011 at 02:44, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > >> 2. M-x lino-mode
> > >
> > > Tells me it doesn't know this command.
> >
> > I think the OP meant linum-mode, and if so, the bug is real
>
> Yes, linum-mode, and yes, it is easily reproducible.
>
> > (bidi still has trouble with invisible text).
>
> There's no invisible text anywhere in sight in linum.el, AFAICT. It
> works by creating overlays with before-string properties that are
> displayed in the left margin area. Before-strings in the margins is
> something I never tried before under bidi-display-reordering, so it's
> not a surprise it has problems.
>
> However, since I'm working on reordering strings, which will directly
> affect this use case (and also holds off code freeze), I'm putting
> this on hold until that job is done.
>
> > In fact, I thought this problem was already reported, but I've been
> > unable to find the relevant bug#, so perhaps no.
>
> If you mean invisible text, it's bug #7616.
This bug should be fixed now on the trunk (revision 105208).
prev parent reply other threads:[~2011-07-14 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 7:01 bug#8867: 24.0.50; bidi-display-reordering + lino-mode + move-up = beginning of buffer Chen Levy
2011-06-16 0:44 ` Stefan Monnier
2011-06-16 2:00 ` Juanma Barranquero
2011-06-16 3:05 ` Eli Zaretskii
2011-06-16 3:17 ` Juanma Barranquero
2011-06-16 15:07 ` Eli Zaretskii
2011-06-16 16:24 ` Juanma Barranquero
2011-07-14 17:53 ` Eli Zaretskii [this message]
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=83fwm8iw9s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=8867-done@debbugs.gnu.org \
--cc=contrib@chenlevy.com \
--cc=lekktu@gmail.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.