emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <dandavison7@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org fontifies outside of src blocks
Date: Mon, 10 Jan 2011 18:20:30 +0000	[thread overview]
Message-ID: <m1fwt039jl.fsf@gmail.com> (raw)
In-Reply-To: E6963352-075E-48DF-9FC5-57250201EA08@tsdye.com

"Thomas S. Dye" <tsd@tsdye.com> writes:

> Hi Dan and Jeff,
>
> I remember slow response time and output to *Messages* when working
> outside code blocks, but no erroneous fontification of text outside
> code blocks.  My hunch at the time

The slowness and superfluous output to *Messages* during fontification
is something which emacs does on OS X which is not related to code
blocks or Org-mode. I think the default value of `font-lock-verbose'
should be changed to nil in emacs24. I'll suggest it.

Dan

> was that emacs was determining what
> text to display and how to fontify it, and that it would do this
> regardless of whether code blocks were actually displayed.  It has
> been a while since someone on the list pointed out the fix to me, but
> I haven't run into any problems since then and my buffers are
> fontified correctly.
>
> All the best,
> Tom
>
> On Jan 10, 2011, at 3:06 AM, Dan Davison wrote:
>
>> Jeff Horn <jrhorn424@gmail.com> writes:
>>
>>> Beautiful. Thanks, Tom!
>>
>> Hi Jeff, so you had two problems:
>>
>> 1. Erroneous fontification outside of blocks
>> 2. Slowness and too much output to *Messages*
>>
>> I was aware that Tom's fix fixes (2) on OS X, but I haven't heard of
>> (1)
>> before. Isn't it a bit weird that the same fix should fix (1)?
>>
>> Dan
>>
>>>
>>> On Sun, Jan 9, 2011 at 10:16 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
>>>> Aloha Jeff,
>>>>
>>>> I think I had this issue.  IIRC, this is a Mac issue.  I think you
>>>> can fix
>>>> it with this:
>>>>
>>>>  (setq font-lock-verbose nil)
>>>>
>>>> If not, let me know and I'll look harder.
>>>>
>>>> Tom
>>>>
>>>> On Jan 9, 2011, at 4:54 PM, Jeff Horn wrote:
>>>>
>>>>> Hey list,
>>>>>
>>>>> I have an annoying issue. When in *either* Aquamacs or terminal
>>>>> emacs,
>>>>> if I view my init file (it's in org rather than elisp) and I edit
>>>>> *anything* in the buffer, org attempts to fontify the text as
>>>>> emacs-lisp.
>>>>>
>>>>> It takes a few seconds for anything to show up in windowed emacsen.
>>>>> Terminal experiences no lag, so it's less of an issue. After
>>>>> typing a
>>>>> sentences, the message buffer has tens of instances of the
>>>>> following
>>>>> text:
>>>>>
>>>>>   Fontifying  org-src-fontification:emacs-lisp-mode...
>>>>> (regexps.................)
>>>>>
>>>>> Is this the expected behavior? I like fontification. I just only
>>>>> expect it to happen within a block, not outside of it. And yes,
>>>>> all of
>>>>> the blocks are closed correctly (I've double checked, but I used
>>>>> yasnippet to fill the buffer in the first place).
>>>>>
>>>>> Where should I start looking? :)
>>>>>
>>>>> --
>>>>> Jeffrey Horn
>>>>> http://www.failuretorefrain.com/jeff/
>>>>>
>>>>> _______________________________________________
>>>>> Emacs-orgmode mailing list
>>>>> Please use `Reply All' to send replies to the list.
>>>>> Emacs-orgmode@gnu.org
>>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>>
>>>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2011-01-10 18:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10  2:54 org fontifies outside of src blocks Jeff Horn
2011-01-10  3:16 ` Thomas S. Dye
2011-01-10  4:31   ` Jeff Horn
2011-01-10 13:06     ` Dan Davison
2011-01-10 15:31       ` Thomas S. Dye
2011-01-10 18:20         ` Dan Davison [this message]
2011-01-11  4:35         ` Jeff Horn

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=m1fwt039jl.fsf@gmail.com \
    --to=dandavison7@gmail.com \
    --cc=emacs-orgmode@gnu.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).