emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Tue, 08 Feb 2011 19:00:41 +0000	[thread overview]
Message-ID: <m1fwrybbc6.fsf@94.196.76.76.threembb.co.uk> (raw)
In-Reply-To: <80sjvzsjq7.fsf@missioncriticalit.com> ("Sébastien Vauban"'s message of "Mon, 07 Feb 2011 20:55:12 +0100")

Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
writes:

> Hi Dan,
>
> Dan Davison wrote:
>> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw-XMD5yJDbdMSQIYZ4X/+iSw@public.gmane.orgrg> writes:
>>> Dan Davison wrote:
>>>> 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. Do you see that?
>>>
>>> Yes, but that's already the current situation today, *when using faces with
>>> background*. My (future) patch does not change that, and I'm not sure
>>> whether it should or not. In a way, I find this better: it makes it very
>>> clear there is a code block folded at that point in the document. Yes, I
>>> definitively prefer it that way -- if you don't mind.
>>
>> Hi Seb, hmm, maybe we're talking about different things.
>
> I think so as well. I was thinking you were talking about the delimiter line
> (begin_src and end_src) going up to the right end of the screen if the fully
> expanded view.
>
> Your picture shows it when folded.
>
>> I would say this is a bug.
>
> Indeed, that's definitely a bug.
>
>> A key part of Org's visual model is that folding hides content. Imo. I'm not
>> saying I know how to fix it, but that's a separate issue. Here are three
>> screenshots:
>>
>> org-overview:
>> org-content:
>> show-all:
>
> Can you send me your file, for me to test if I have the same problem?

I don't have that file any longer, but the problem occurs with all
files. It is somewhat unpredictable -- I mess about with block
show/hide, and global visibility cycling, and it happens eventually if
not at first. E.g. this file

---------------------------------
* heading
#+begin_src emacs-lisp
1
#+end_src
---------------------------------

>
> FYI, I've seen that once when working on my patch[1], but never ever since the
> last versions. Hence, just checking (plizz don't mind), are you really using
> the version committed in the trunk,

yes, clean, HEAD is 88b793946.

Note I'm on OS X (cocoa builds). Maybe someone else with OSX could try
to reproduce this?  It occurs with a distributed binary of aquamacs, and
when loading nothing but Org, so it doesn't seem to be any local stuff
of mine that's the problem.

Dan

> or some older version I may have sent on
> this list?
>
>> (Btw, that's with the box face attribute set with your patch. Just
>> playing with it to see if I like it.)
>
> Maybe make a try with underline and overline -- discovered not that long ago.
> I find that the nicest combination... As well for headings 1 and 2. I'll send
> my newest color theme very soon for you to see this, if you're interested.
> Nope: correction, I'll put it directly on Worg. I'll ask for access, and try
> being autonomous for such things.
>
> Best regards,
>   Seb
>
> Footnotes:
> [1] IIRC, Eric Fraga did see that as well, at some point in time.

  reply	other threads:[~2011-02-08 19:00 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 [this message]
2011-02-08 20:14                   ` Sébastien Vauban
2011-02-09  8:40                     ` Dan Davison
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=m1fwrybbc6.fsf@94.196.76.76.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).