From: Carsten Dominik <carsten.dominik@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs-orgmode@gnu.org, Richard Riley <rileyrg@gmail.com>,
Bastien <bastien.guerry@wikimedia.fr>
Subject: Re: Re: Org now fontifies code blocks
Date: Tue, 7 Sep 2010 16:22:40 +0200 [thread overview]
Message-ID: <AANLkTin8tGnqzNazMcbwzLaOsKG1eU+uQqO+xRGoNbZC@mail.gmail.com> (raw)
In-Reply-To: <87sk1lmzyo.fsf@stats.ox.ac.uk>
On Tue, Sep 7, 2010 at 3:43 PM, Dan Davison <davison@stats.ox.ac.uk> wrote:
> "David O'Toole" <dto1138@gmail.com> writes:
>
>> I agree Bastien :)
>
> I agree too, but note that what we are agreeing to is a conditional
> statement...
>
>>
>> On Mon, Sep 6, 2010 at 2:30 PM, Bastien <bastien.guerry@wikimedia.fr> wrote:
>>> If setting org-src-fontify-natively to `t' by default triggers a debate
>>> on whether we need to set org-warn-when-editing-src-block-in-org-buffer
>
> I don't think it is clear that there is such a debate.
>
> But I do think we are gravitating towards turning it off, if it is
> causing noticeable slowness on startup. So unless there are more voices
> in favour of keeping it turned on for new users then I'll turn it off
> later today.
Just to add to this: After trying it more, I see another reason why
it would be good
to have it turned off by default. Fontification gives meaning to pieces
of text, and that meaning is different in different major modes. So
this is watering
down the meaning of org-mode syntax font locking. So it is good for experts,
but confusing for newbies. So my vote goes to off.
I *do* like the idea mentioned earlier to use a different background
when fontification is turned on. Just a slight grey instead of white,
for example. That would help distinguish things in export mode.
- Carsten
next prev parent reply other threads:[~2010-09-07 14:22 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 23:12 [PATCH] Mode-specific fontification of babel source blocks David O'Toole
2010-08-03 23:14 ` David O'Toole
2010-08-03 23:23 ` Erik Iverson
2010-08-04 2:55 ` Dan Davison
2010-08-04 5:55 ` David O'Toole
2010-08-09 21:35 ` Dan Davison
2010-09-02 15:51 ` Org now fontifies code blocks Dan Davison
2010-09-02 17:04 ` Erik Iverson
2010-09-02 19:06 ` Native TAB in code blocks [WAS Re: Org now fontifies code blocks] Dan Davison
2010-09-02 19:18 ` Carsten Dominik
2010-09-02 20:36 ` Native TAB in code blocks Dan Davison
2010-09-03 8:11 ` Julien Fantin
2010-09-02 20:26 ` Org now fontifies " Sébastien Vauban
2010-09-03 17:30 ` Eric S Fraga
2010-09-03 19:10 ` Thomas S. Dye
2010-09-06 16:49 ` David O'Toole
2010-09-07 13:23 ` Dan Davison
2010-09-07 13:55 ` Richard Riley
2010-09-07 16:05 ` Thomas S. Dye
2010-09-08 16:36 ` Darlan Cavalcante Moreira
2010-09-08 17:41 ` Dan Davison
2010-09-09 13:02 ` Darlan Cavalcante Moreira
2010-09-09 21:40 ` Thomas S. Dye
2010-09-09 22:35 ` Dan Davison
2010-09-09 23:03 ` Thomas S. Dye
2010-10-28 11:10 ` Dan Davison
2010-10-28 12:08 ` Jules Bean
2010-10-28 12:47 ` Jambunathan K
2010-10-28 13:35 ` Dan Davison
2010-10-28 16:24 ` Thomas S. Dye
2010-09-06 16:59 ` Richard Riley
2010-09-06 17:53 ` David O'Toole
2010-09-06 18:30 ` Bastien
2010-09-06 18:52 ` David O'Toole
2010-09-06 18:59 ` Richard Riley
2010-09-07 13:43 ` Dan Davison
2010-09-07 14:22 ` Carsten Dominik [this message]
2010-09-07 14:33 ` Bastien
2010-09-07 14:37 ` Carsten Dominik
2010-09-07 14:41 ` Sebastian Rose
2010-09-07 16:20 ` Dan Davison
2010-09-07 15:03 ` Sébastien Vauban
2010-09-07 16:54 ` Dan Davison
2010-09-08 16:30 ` Bastien
2010-09-08 18:35 ` Sébastien Vauban
2010-09-08 18:42 ` Erik Iverson
2010-09-08 19:17 ` Dan Davison
2010-09-07 14:24 ` Bastien
2010-09-07 14:33 ` Tom Short
2010-09-07 14:47 ` Richard Riley
2010-09-06 17:59 ` Erik Iverson
2010-09-06 18:23 ` Dan Davison
2010-09-06 18:49 ` Richard Riley
2010-09-07 13:33 ` Dan Davison
2010-09-07 7:24 ` Sébastien Vauban
2010-08-15 6:33 ` [PATCH] Mode-specific fontification of babel source blocks Dan Davison
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=AANLkTin8tGnqzNazMcbwzLaOsKG1eU+uQqO+xRGoNbZC@mail.gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bastien.guerry@wikimedia.fr \
--cc=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=rileyrg@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 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).