From: Rick Frankel <firstname.lastname@example.org>
To: Bastien <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>,
Julien Cubizolles <firstname.lastname@example.org>
Subject: Re: org-hide sometimes wrong
Date: Fri, 15 Mar 2013 18:54:49 -0400 [thread overview]
Message-ID: <20130315225449.GB14263@BigDog.local> (raw)
On Fri, Mar 15, 2013 at 10:01:45PM +0100, Bastien wrote:
> Rick Frankel <email@example.com> writes:
> > On Mar 15, 2013, at 7:13 AM, Julien Cubizolles <firstname.lastname@example.org> wrote:
> >> Lately, the leading stars have been reappearing, seemingly
> >> randomly. I've checked the org-hide face and its value changes:
> > I've been noticing the same behavior (and broken indenting) since some recent git pull...
> > Closing and reopening the file fixes it, but it seems to be a
> > regression
> Can someone try to bisect?
I try to find time :)
> Maybe git blame and check lines >5341 for the last changes
> against `org-find-invisible-foreground'. But the last ones
> are pretty old now.
> As for the broken indenting, what is the issue exactly?
I have an org file with lots of source blocks and deep level, when i
open and expand the headings, sometimes the source blocks are against
the left margin and not properly indented.
BTW, org-bullets also seems to be broken now. The "(require
'org-mode)" on line 85 fails because there is no org-mode.el not sure
what else has changed. I noticed there was a big commit on 9-March.
I will also try to find time this weekend to bisect that as well...
prev parent reply other threads:[~2013-03-15 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 11:13 org-hide sometimes wrong Julien Cubizolles
2013-03-15 18:02 ` Rick Frankel
2013-03-15 21:01 ` Bastien
2013-03-15 21:43 ` Julien Cubizolles
2013-03-15 22:54 ` Rick Frankel [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).