From: Carsten Dominik <dominik@science.uva.nl>
To: Tom Weissmann <trmsw@yahoo.co.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode font-locking clobbers the rear-nonsticky text property; for other modes it doesn't
Date: Thu, 4 Oct 2007 10:44:50 +0200 [thread overview]
Message-ID: <41eb77917bfd2add86e8e9392e935da4@science.uva.nl> (raw)
In-Reply-To: <loom.20071003T092541-350@post.gmane.org>
On Oct 3, 2007, at 11:34, Tom Weissmann wrote:
> I am trying to work out why font-lock for Org-mode changes the
> rear-nonsticky
> property of text I insert, while it doesn't do it for other modes.
>
> For example:
>
> (with-current-buffer
> (get-buffer-create "foo")
> (insert (propertize ";;Try adding text after this ->"
> 'read-only t
> 'face 'underline
> 'rear-nonsticky '(read-only))))
>
> In the "foo" buffer you will be able to add text after the arrow.
> Turning on
> lisp-interaction mode will fontify the text as a comment, but if you
> delete the
> text you added you'll still be able to add some more - whereas in
> org-mode you
> can't.
>
> Does anyone know why this happens and how I can prevent it?
Hi Tom,
the reason is this: Org-mode uses font-lock to activate links and
dates,
and it adds a rear-nonsticky property to make sure that the properties
behave well. Because of this, the unfontification function I wrote for
org-mode does remove the rear-nonsticky property indiscriminately.
I did not know that you can select the individual properties that
should be
non-sticky - I only learned that from your example. Thanks!
This problem will be fixed in 5.11.
- Carsten
prev parent reply other threads:[~2007-10-04 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 9:34 org-mode font-locking clobbers the rear-nonsticky text property; for other modes it doesn't Tom Weissmann
2007-10-04 8:44 ` Carsten Dominik [this message]
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=41eb77917bfd2add86e8e9392e935da4@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=trmsw@yahoo.co.uk \
/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).