--- Begin Message ---
|
Subject: |
23.1; hl-line-mode appears to not be compatible with line prefix text properties |
|
Date: |
Wed, 05 Aug 2009 23:49:32 +0100 |
|
User-agent: |
Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.7 Emacs/23.1 (i486-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the address@hidden mailing list,
and to the gnu.emacs.bug news group.
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
I use org-mode extensively. In a recent upgrade to org-mode, text
properties are used to display the text automatically indented.
However, this use of line prefix text properties, in particular, seems
to interact badly with hl-line-mode. Specifically, the highlighting
done by hl-line-mode starts at an indented position, not at the
physical start of the line, and continues onto the next screen line to
line up with the start position.
A sample screenshot of this erroneous behaviour can be found (for a
short while, at least) at
http://www.homepages.ucl.ac.uk/~ucecesf/tmp/indent-highlight.png
Thanks,
eric
If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
`bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/usr/share/emacs/23.1/etc/DEBUG for instructions.
In GNU Emacs 23.1.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2009-08-03 on raven, modified by Debian
Windowing system distributor `The X.Org Foundation', version 11.0.10402000
configured using `configure '--build=i486-linux-gnu' '--host=i486-linux-gnu'
'--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib'
'--localstatedir=/var/lib' '--infodir=/usr/share/info'
'--mandir=/usr/share/man' '--with-pop=yes'
'--enable-locallisppath=/etc/emacs23:/etc/emacs:/usr/local/share/emacs/23.1/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/23.1/site-lisp:/usr/share/emacs/site-lisp:/usr/share/emacs/23.1/leim'
'--with-x=yes' '--with-x-toolkit=athena' '--with-toolkit-scroll-bars'
'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu' 'CFLAGS=-DDEBIAN -g
-O2' 'LDFLAGS=-g' 'CPPFLAGS=''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_GB.ISO-8859-15
value of $XMODIFIERS: nil
locale-coding-system: iso-latin-9-unix
default-enable-multibyte-characters: t
Major mode: Summary
Minor modes in effect:
iswitchb-mode: t
display-time-mode: t
show-paren-mode: t
global-hl-line-mode: t
delete-selection-mode: t
recentf-mode: t
diff-auto-refine-mode: t
icomplete-mode: t
global-highlight-changes-mode: t
highlight-changes-visible-mode: t
shell-dirtrack-mode: t
tooltip-mode: t
mouse-wheel-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
global-auto-composition-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
size-indication-mode: t
column-number-mode: t
line-number-mode: t
transient-mark-mode: t
Recent input:
(not relevant)
Recent messages:
(not relevant)
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#4053: 23.1; hl-line-mode appears to not be compatible with line prefix text properties |
|
Date: |
Mon, 11 Jul 2011 15:53:37 -0400 |
|
User-agent: |
Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) |
This bug is being closed because we need more information to proceed and
it has not been provided. If you reply with the requested information it
can be reopened if needed.
You can view the whole report at http://debbugs.gnu.org/BUGNUMBER
Chong Yidong wrote:
> Org mode has been updated in Emacs since your bug report. Would it be
> possible for you to test if the bug still exists with the latest Emacs
> bzr repository? If that's inconvenient, could you please provide a
> precise step-by-step recipe for reproducing this problem?
>
> Thanks.
--- End Message ---