From: Dan Davison <dandavison7@gmail.com>
To: "Sébastien Vauban"
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@lo.gmane.org>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Fontification of blocks
Date: Wed, 09 Feb 2011 08:40:17 +0000 [thread overview]
Message-ID: <m1sjvx1tzi.fsf@94.196.91.150.threembb.co.uk> (raw)
In-Reply-To: 80oc6mz3jy.fsf@missioncriticalit.com
>>>>>> Just quickly, one thing I noticed is that the begin/end lines were
>>>>>> visible even inside folded trees. I.e., in a folded org file, containing
>>>>>> many src blocks, I could see the coloured backgrounds "poking out" of
>>>>>> the folded sections, extending to the right of the screen.
[...]
>> E.g. this file
>>
>> ---------------------------------
>> * heading
>> #+begin_src emacs-lisp
>> 1
>> #+end_src
>> ---------------------------------
>
> I could reproduce it with your above file, if the file ends on the end_src
> line.
>
> The following:
>
> * heading
>
> #+begin_src emacs-lisp
> 1
> #+end_src
> * other heading
>
> also exhibits the problem, but this one:
>
> * heading
>
> #+begin_src emacs-lisp
> 1
> #+end_src
>
> * other heading
>
> does not.
>
> So, it is related to the fact that the block is the last line of the subtree
> or of the file.
>
> As I always have newlines before headings, I don't see such a problem on my
> docs.
>
> Dan, can you confirm the above observation?
Confirm. Good point.
>
> Knowing this, do you have an idea on how to fix it?
No. I do see things like this from time to time with
outline-minor-mode. Can anyone suggest how to solve this
folding/overlay/visibility problem?
Dan
> If not, I'll try having a
> play with the patched file.
>
> Best regards,
> Seb
next prev parent reply other threads:[~2011-02-09 8:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 9:02 Fontification of blocks Sébastien Vauban
2010-12-10 11:12 ` David O'Toole
2010-12-13 21:25 ` Sébastien Vauban
2010-12-22 13:36 ` Dan Davison
2010-12-22 14:46 ` Sébastien Vauban
2010-12-13 19:50 ` Eric Schulte
2010-12-13 20:46 ` Sébastien Vauban
2010-12-15 17:22 ` Eric Schulte
2011-02-01 21:04 ` Sébastien Vauban
2011-02-02 7:25 ` Eric S Fraga
2011-02-02 14:34 ` Dan Davison
2011-02-02 20:19 ` Sébastien Vauban
2011-02-07 12:54 ` Dan Davison
2011-02-07 19:55 ` Sébastien Vauban
2011-02-08 19:00 ` Dan Davison
2011-02-08 20:14 ` Sébastien Vauban
2011-02-09 8:40 ` Dan Davison [this message]
2011-02-02 22:24 ` Sébastien Vauban
2011-02-02 22:46 ` Eric S Fraga
2011-02-03 15:02 ` Eric Schulte
2011-02-03 19:57 ` Sébastien Vauban
2011-02-03 20:05 ` Eric S Fraga
2011-02-03 20:44 ` Sébastien Vauban
2011-02-04 9:21 ` Sébastien Vauban
2011-02-04 16:18 ` Eric S Fraga
2011-02-04 20:50 ` Eric Schulte
2011-02-06 8:52 ` Sébastien Vauban
-- strict thread matches above, loose matches on Subject: below --
2010-12-10 9:01 Sébastien Vauban
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1sjvx1tzi.fsf@94.196.91.150.threembb.co.uk \
--to=dandavison7@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@lo.gmane.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/org-mode.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).