Re: [O] Invalid read syntax: "?" when switching org-dates or when tying to org-submit-bug-report

[michael . ziems]

Hello Nicolas, 

that worked perfectly. 

I had a strange character in that file and now it works good. 

Thanks, 

Michael

Am 2017-05-08 11:52, schrieb Nicolas Goaziou:

> michael.zi...@xiron.de writes:
> 
>> When i byte-compile the file i get the following error: 
>> 
>> Compiling file
>> c:/Users/sane/AppData/Roaming/.emacs.d/elpa/org-20170502/org-clock.el at
>> Mon May  8 11:27:30 2017
>> org-clock.el:1949:1:Error: Invalid read syntax: "?"
> 
> It looks odd. Could you double-check the modification you made? It
> should be made of the following characters: 
> 
> ? \ ·
> 
> without space between them.
> 
> Regards,

Re: [O] Invalid read syntax: "?" when switching org-dates or when tying to org-submit-bug-report

[Nicolas Goaziou]

michael.zi...@xiron.de writes:

> When i byte-compile the file i get the following error: 
>
> Compiling file
> c:/Users/sane/AppData/Roaming/.emacs.d/elpa/org-20170502/org-clock.el at
> Mon May  8 11:27:30 2017
> org-clock.el:1949:1:Error: Invalid read syntax: "?"

It looks odd. Could you double-check the modification you made? It
should be made of the following characters: 

  ? \ ·

without space between them.

Regards,

Re: [O] Invalid read syntax: "?" when switching org-dates or when tying to org-submit-bug-report

[michael . ziems]

Hello Nicolas, 

thanks for the answer. 

I'm not a big expert on lisp. As i did not find any information how a
.patch file works so fast, i just changed it manually in the
org-clock.el like this: 

(defun org-clock-put-overlay (time)
  "Put an overlays on the current line, displaying TIME.
This creates a new overlay and stores it in `org-clock-overlays', so
that it
will be easy to remove."
  (let (ov tx)
(beginning-of-line)
(let ((case-fold-search nil))
  (when (looking-at org-complex-heading-regexp)
(goto-char (match-beginning 4
(setq ov (make-overlay (point) (point-at-eol))
  tx (concat (buffer-substring-no-properties (point) (match-end 4))
 (org-add-props
 (make-string
  (max 0 (- (- 60 (current-column))
(- (match-end 4) (match-beginning 4))
(length (org-get-at-bol 'line-prefix
  ?·)
 '(face shadow))
 (org-add-props
 (format " %9s " (org-minutes-to-clocksum-string time))
 '(face org-clock-overlay))
 ""))
(overlay-put ov 'display tx)
(push ov org-clock-overlays))) 

When i byte-compile the file i get the following error: 

Compiling file
c:/Users/sane/AppData/Roaming/.emacs.d/elpa/org-20170502/org-clock.el at
Mon May  8 11:27:30 2017
org-clock.el:1949:1:Error: Invalid read syntax: "?"

Thanks for your patience. 

Michael 

Am 2017-05-08 11:09, schrieb Nicolas Goaziou:

> Hello,
> 
> michael.zi...@xiron.de writes:
> 
>> when i try to swicht an active timestamp via org-shitright or when i
>> fire M-x org-submit-bug-report i get the following error: 
>> 
>> Debugger entered--Lisp error: (invalid-read-syntax "?")
>> eval-buffer(# nil
>> "c:/Users/sane/AppData/Roaming/.emacs.d/elpa/org-20170502/org-clock.el"
>> nil t)  ; Reading at buffer position 72111
>> 
>> load-with-code-conversion("c:/Users/sane/AppData/Roaming/.emacs.d/elpa/org-20170502/org-clock.el"
>> "c:/Users/sane/AppData/Roaming/.emacs.d/elpa/org-20170502/org-clock.el"
>> nil t)
>> require(org-clock)
>> mapc(require (org-agenda org-archive org-attach org-clock org-colview
>> org-id org-table org-timer))
>> org-require-autoloaded-modules()
>> org-submit-bug-report()
>> call-interactively(org-submit-bug-report record nil)
>> command-execute(org-submit-bug-report record)
>> execute-extended-command(nil "org-submit-bug-report")
>> call-interactively(execute-extended-command nil nil) 
>> 
>> I tried to do the same with Edebug on, but somehow it looks fine
>> there.
> 
> Would the attached patch fix your issue?
> 
> Regards,

Re: [O] Invalid read syntax: "?" when switching org-dates or when tying to org-submit-bug-report

[Nicolas Goaziou]

Hello,

michael.zi...@xiron.de writes:

> when i try to swicht an active timestamp via org-shitright or when i
> fire M-x org-submit-bug-report i get the following error: 
>
> Debugger entered--Lisp error: (invalid-read-syntax "?")
>   eval-buffer(# nil
> "c:/Users/sane/AppData/Roaming/.emacs.d/elpa/org-20170502/org-clock.el"
> nil t)  ; Reading at buffer position 72111
>  
> load-with-code-conversion("c:/Users/sane/AppData/Roaming/.emacs.d/elpa/org-20170502/org-clock.el"
> "c:/Users/sane/AppData/Roaming/.emacs.d/elpa/org-20170502/org-clock.el"
> nil t)
>   require(org-clock)
>   mapc(require (org-agenda org-archive org-attach org-clock org-colview
> org-id org-table org-timer))
>   org-require-autoloaded-modules()
>   org-submit-bug-report()
>   call-interactively(org-submit-bug-report record nil)
>   command-execute(org-submit-bug-report record)
>   execute-extended-command(nil "org-submit-bug-report")
>   call-interactively(execute-extended-command nil nil) 
>
> I tried to do the same with Edebug on, but somehow it looks fine
> there.

Would the attached patch fix your issue?

Regards,

-- 
Nicolas Goaziou
>From 144c4ba61ba325f682088ba8501dccb3e20dbc8a Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou 
Date: Mon, 8 May 2017 11:08:10 +0200
Subject: [PATCH] org-clock: Disambiguate character syntax

* lisp/org-clock.el (org-clock-put-overlay): Escape character in
  character syntax.
---
 lisp/org-clock.el | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lisp/org-clock.el b/lisp/org-clock.el
index 462eda682..ea1ead47d 100644
--- a/lisp/org-clock.el
+++ b/lisp/org-clock.el
@@ -1967,7 +1967,8 @@ will be easy to remove."
 			 (make-string
 			  (max 0 (- (- 60 (current-column))
 (- (match-end 4) (match-beginning 4))
-(length (org-get-at-bol 'line-prefix ?·)
+(length (org-get-at-bol 'line-prefix
+			  ?\·)
 			 '(face shadow))
 		 (org-add-props
 			 (format " %9s " (org-duration-from-minutes time))
-- 
2.12.2

Re: [O] Invalid-read-syntax

[Colin Baxter]

I would like to thank everyone for their help in resolving something
which I should have done myself had I but gave the matter a little more
thought.

Best wishes,

Colin.

Re: [O] Invalid-read-syntax

[Colin Baxter]

On Wed, Apr 20 2016, Nick Dokos wrote:

> Colin Baxter  writes:
>
>> The file /lisp/ox-html.el of org-mode release_8.3.4-743-g516bbf has
>> binary content at line 1952, whereas the same file of org-mode
>> release_8.3.4-721-g16ad80 has not. Perhaps this is significant.
>>
>
> Perhaps I'm missing something but I don't see anything like that.I also
> don't see any changes to ox-html.el between 16ad80 and 516bbf. I
> checked out 516bbf and lines 1950+ of ox_html.el look like this:
>
>(when title
>(format
> (if html5-fancy
> "\n%s\n%s"
>   "%s%s\n")
> (org-export-data title info)
>
> Maybe your local copy is corrupted somehow? What happens if you
>
>  git checkout -- .../lisp/ox-html.el
>
> ?
>
> --
> Nick

git checkout /path/to/ox-html.el worked and removed the binary stuff. I
guess it must have been corrupted during the git pull. Thank you.

Best wishes,

Colin.

Re: [O] Invalid-read-syntax

[Nick Dokos]

Colin Baxter  writes:

> The file /lisp/ox-html.el of org-mode release_8.3.4-743-g516bbf has
> binary content at line 1952, whereas the same file of org-mode
> release_8.3.4-721-g16ad80 has not. Perhaps this is significant.
>

Perhaps I'm missing something but I don't see anything like that.I also
don't see any changes to ox-html.el between 16ad80 and 516bbf. I
checked out 516bbf and lines 1950+ of ox_html.el look like this:

   (when title
 (format
  (if html5-fancy
  "\n%s\n%s"
"%s%s\n")
  (org-export-data title info)

Maybe your local copy is corrupted somehow? What happens if you

 git checkout -- .../lisp/ox-html.el

?

--
Nick

Re: [O] Invalid-read-syntax

[Colin Baxter]

On Wed, Apr 20 2016, Alan Schmitt wrote:

> On 2016-04-20 07:59, Colin Baxter  writes:
>
>> On Tue, Apr 19 2016, Nicolas Goaziou wrote:
>>
>>> Hello,
>>>
>>> Colin Baxter  writes:
>>>
 With the latest org-mode release_8.3.4-739-g7894129, I'm getting an lisp 
 error
 (invalid-read-syntax "#"). This ocurs with emacs-25.1.50.1 and
 emacs-24.5.1.
>>>
>>> Could you provide an ECM? What command triggered that?
>>>
>>> Regards,
>>
>> I'm afraid I don't know what ECM means. If you can give me some more
>> information, I'll have a go at providing it.
>
> It's a TLA (three letters acronym) for MWE (minimal working example) in
> French: Exemple Complet Minimal.
>
> HTH,
>
> Alan

Thanks for the clarification of ECM.

The file /lisp/ox-html.el of org-mode release_8.3.4-743-g516bbf has
binary content at line 1952, whereas the same file of org-mode
release_8.3.4-721-g16ad80 has not. Perhaps this is significant.

Best wishes,

Colin.

Re: [O] Invalid-read-syntax

[Colin Baxter]

On Tue, Apr 19 2016, Nicolas Goaziou wrote:

> Hello,
>
> Colin Baxter  writes:
>
>> With the latest org-mode release_8.3.4-739-g7894129, I'm getting an lisp 
>> error
>> (invalid-read-syntax "#"). This ocurs with emacs-25.1.50.1 and
>> emacs-24.5.1.
>
> Could you provide an ECM? What command triggered that?
>
> Regards,

I'm afraid I don't know what ECM means. If you can give me some more
information, I'll have a go at providing it.

The error is immediately triggered when I launch emacs. The offending lines in 
my
~/.emacs are just

(add-to-list 'load-path (expand-file-name "~/git/org-mode/lisp"))
(add-to-list 'load-path (expand-file-name "~/git/org-mode/contrib/lisp"))

There are no errors if I use org-mode release_8.3.4-721-g16ad80. The
error occurred first with release_8.3.4-739-g7894129 and is present also
with release_8.3.4-743-g516bbf. The package ox-html looks a candidate
for suspicion, perhaps.

Best wishes,

Colin.

Re: [O] Invalid-read-syntax

[Alan Schmitt]

On 2016-04-20 07:59, Colin Baxter  writes:

> On Tue, Apr 19 2016, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> Colin Baxter  writes:
>>
>>> With the latest org-mode release_8.3.4-739-g7894129, I'm getting an lisp 
>>> error
>>> (invalid-read-syntax "#"). This ocurs with emacs-25.1.50.1 and
>>> emacs-24.5.1.
>>
>> Could you provide an ECM? What command triggered that?
>>
>> Regards,
>
> I'm afraid I don't know what ECM means. If you can give me some more
> information, I'll have a go at providing it.

It's a TLA (three letters acronym) for MWE (minimal working example) in
French: Exemple Complet Minimal.

HTH,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂ (2016-03, Mauna Loa Obs.): 404.83


signature.asc
Description: PGP signature

Re: [O] Invalid-read-syntax

[Nicolas Goaziou]

Hello,

Colin Baxter  writes:

> With the latest org-mode release_8.3.4-739-g7894129, I'm getting an lisp error
> (invalid-read-syntax "#"). This ocurs with emacs-25.1.50.1 and
> emacs-24.5.1.

Could you provide an ECM? What command triggered that?

Regards,

-- 
Nicolas Goaziou

Re: [O] Invalid read syntax (#) in org-element parse tree

[Nicolas Goaziou]

Thorsten Jolitz tjol...@gmail.com writes:

 I'm not sure about what you want to do with the parse tree. The usual
 function to work with it is `org-element-map'. You may want to have
 a look at its docstring, as it contains examples.

 I want to write an 'unusual' backend that does not need anything else
 from the exporting framework but the parse-tree as a list. 

Then you don't want the exporting framework at all, only org-element.el.

Anyway I'm confused. The parse-tree _is_ a list. To convince yourself,
evaluate the following in any Org buffer:

  (listp (org-element-parse-buffer))

 So all I need would be a workaround for this read-error issue, i.e.
 a tip how to get a version of the parse tree that can be used as list
 in a Lisp program.

Have you tried (setq print-circle t) ?

 I could not find any explanation for the '#1' and '#2' syntax I
 encountered, so I don't really know what its all about.

It is explained in the info link I gave you.


Regards,

-- 
Nicolas Goaziou

Re: [O] Invalid read syntax (#) in org-element parse tree

[Thorsten Jolitz]

Nicolas Goaziou n.goaz...@gmail.com writes:

 I want to write an 'unusual' backend that does not need anything else
 from the exporting framework but the parse-tree as a list. 

 Then you don't want the exporting framework at all, only org-element.el.

yes, only the parser. 

 Anyway I'm confused. The parse-tree _is_ a list. To convince yourself,
 evaluate the following in any Org buffer:

   (listp (org-element-parse-buffer))

 So all I need would be a workaround for this read-error issue, i.e.
 a tip how to get a version of the parse tree that can be used as list
 in a Lisp program.

 Have you tried (setq print-circle t) ?

 I could not find any explanation for the '#1' and '#2' syntax I
 encountered, so I don't really know what its all about.

 It is explained in the info link I gave you.

I read this link, it says:

,
| To represent shared or circular structures within a complex of Lisp
| objects, you can use the reader constructs ‘#n=’ and ‘#n#’.
`

what is not quite the same like 

,---
| :parent #1
`---

but with your other hints, I now understand the problem. I wanted to see
how the parse tree looks like, so I printed it out (I did not know about
the existance of 'print-circle' then, but it was set to nil). Then I
tried to experiment with the printed representation, but the #1 syntax
gave me an error. 

When I set 'print-circle' to t, the printed result looks like described
in the info page, with elements like 

[...] :parent #66# #67=(headline [...]


-- 
cheers,
Thorsten

Re: [O] Invalid read syntax (#) in org-element parse tree

[Thorsten Jolitz]

Thorsten Jolitz tjol...@gmail.com writes:

[continuation, prior message sent unfinished by accident]

 but with your other hints, I now understand the problem. I wanted to see
 how the parse tree looks like, so I printed it out (I did not know about
 the existance of 'print-circle' then, but it was set to nil). Then I
 tried to experiment with the printed representation, but the #1 syntax
 gave me an error. 

 When I set 'print-circle' to t, the printed result looks like described
 in the info page, with elements like 

 [...] :parent #66# #67=(headline [...]

So it was all about the difference between printed representation and
the actual list object, and the special syntax when 'print-circle' is
nil that I could not find in the manual. 

Thanks for the tips, I have to read more about circular lists in Emacs
Lisp, ,first time I see them in action. 

-- 
cheers,
Thorsten

Re: [O] Invalid read syntax (#) in org-element parse tree

[Nicolas Goaziou]

Hello,

Thorsten Jolitz tjol...@gmail.com writes:

 here is an excerpt of a parse tree produced with
 'org-element-parse-buffer': 

 ,-
 | (section (:begin 1 :end 624 :contents-begin
 | 1 :contents-end 623 :post-blank 1 :parent #0) (keyword (:key
 | TITLE :value Program Blues for Icke :begin 1 :end
 | 39 :post-blank 0 :post-affiliated 1 :parent #1)))
 `-

 When I evaluate a function with this list as data, I get an error:

 ,
 | Debugger entered--Lisp error: (invalid-read-syntax #)
 |   read(#buffer *scratch*)
 |   preceding-sexp()
 |   eval-last-sexp-1(t)
 |   eval-last-sexp(t)
 |   eval-print-last-sexp()
 |   call-interactively(eval-print-last-sexp nil nil)
 `

[...]

 There are a lot of usages of '#' in Emacs Lisp, but I couldn't figure
 out how (and why) it is used in ':parent #1'. 

See (info (elisp) Read Syntax for Circular Objects)

 Nic Ferrier wrote an exhaustive library with routines for working with
 key/value data structures like hash-tables and alists and plists
 (https://github.com/nicferrier/emacs-kv/blob/master/kv.el), but I cannot
 apply any of the functions due to the read error. Do I really have to
 treat the parse tree as text first and eliminate the '#' before I can
 use it as list in Emacs Lisp, or did I simply manage to get the wrong
 represantation of the parse tree somehow?

I'm not sure about what you want to do with the parse tree. The usual
function to work with it is `org-element-map'. You may want to have
a look at its docstring, as it contains examples.


Regards,

-- 
Nicolas Goaziou

Re: [O] Invalid read syntax (#) in org-element parse tree

[Thorsten Jolitz]

Nicolas Goaziou n.goaz...@gmail.com writes:

Hello,

 I'm not sure about what you want to do with the parse tree. The usual
 function to work with it is `org-element-map'. You may want to have
 a look at its docstring, as it contains examples.

I want to write an 'unusual' backend that does not need anything else
from the exporting framework but the parse-tree as a list. So all I need
would be a workaround for this read-error issue, i.e. a tip how to get
a version of the parse tree that can be used as list in a Lisp program. 

I could not find any explanation for the '#1' and '#2' syntax I
encountered, so I don't really know what its all about. 

-- 
cheers,
Thorsten

Re: [O] Invalid read syntax #?

[Alan Schmitt]

On 28 Jan 2012, at 16:55, Bastien wrote:

 For some reason, the first code block is evaluated twice.

Ah, this explains why I was being asked twice if I allowed the code to run.

 When putting a headline on top of this first block, the error
 disappears.

 Sorry I can't help further with this for now.  Hope Eric can
 make something of these infos, together with Nick's backtrace.

Anything I can do to help debug this?

Thanks,

Alan

Re: [O] Invalid read syntax #?

[Bastien]

Hi Alan,

Alan Schmitt alan.schm...@polytechnique.org writes:

 I'm trying this example to export nicely formatted code in LaTeX:
 http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3

 Unfortunately it fails with an error 'Invalid read syntax #'. If I delete
 the second code block (the python one), it works.

For some reason, the first code block is evaluated twice.

When putting a headline on top of this first block, the error
disappears.

Sorry I can't help further with this for now.  Hope Eric can
make something of these infos, together with Nick's backtrace.

-- 
 Bastien

Re: [O] Invalid read syntax #?

[Nick Dokos]

Nick Dokos nicholas.do...@hp.com wrote:

 Alan Schmitt alan.schm...@polytechnique.org wrote:
 
  Hello,
  
  I'm trying this example to export nicely formatted code in LaTeX:
  http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
  
  Unfortunately it fails with an error 'Invalid read syntax #'. If I
  delete the second code block (the python one), it works.
  
  Is there something wrong in the example or in my setup (org-mode from
  yesterday's git, Aquamacs 3 from two days ago, Pygments easy-installed
  today)?
  
 
 I got the same thing, so it's probably not a setup problem. Here's
 a backtrace - looks like a babel problem.
 

Uhh, maybe not: it looks as if something gets out of sync in the parsing and
babel is asked to evaluate the wrong part of the string (see the shortened
backtrace below). But I haven't looked at code, so these are guesses in the
wild.

Nick

 
 Org-mode version 7.8.03 (release_7.8.03.241.g043d)
 GNU Emacs 24.0.92.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.4) of 
 2012-01-24
 
 Debugger entered--Lisp error: (invalid-read-syntax #)
  ...
   org-babel-exp-results((emacs-lisp #+end_src\n#+name: 
 another-listing\n#+begin_src python :exports code ((:cache . no) 
 (:colname-names) (:colnames . no) (:comments . ) (:exports . both) 
 (:hlines . yes) (:noweb . no) (:padline . ) (:padnewline . yes) 
 (:result-params silent) (:result-type . value) (:results . silent) 
 (:rowname-names) (:session . none) (:shebang . ) (:tangle . no))  
 setup-minted 0) block nil 2a39b675a6bec8c15b0ed8928d030e836ddd17d5)
   org-babel-exp-src-block( #(emacs-lisp 0 10 (font-lock-fontified t 
 fontified t)) #(:exports 0 8 (font-lock-fontified t fontified t)) #(both 
 0 4 (font-lock-fontified t fontified t)) #(:results 0 8 
 (font-lock-fontified t fontified t)) #(silent 0 6 (font-lock-fontified t 
 fontified t)))
  ...
   org-export-blocks-preprocess()
  ...
   org-export-preprocess-string(#(#+LATEX_CLASS: article\n#+LaTeX_HEADER: 
 \\usepackage{minted}\n#+LaTeX_HEADER: 
 \\usemintedstyle{emacs}\n#+LaTeX_HEADER: 
 \\newminted{common-lisp}{fontsize=\\footnotesize}\n\n#+name: 
 setup-minted\n#+begin_src emacs-lisp :exports both :results silent\n 
 (setq org-export-latex-listings 'minted)\n (setq 
 org-export-latex-custom-lang-environments\n   '(\n
 (emacs-lisp \common-lispcode\)\n ))\n (setq 
 org-export-latex-minted-options\n   '((\frame\ \lines\)\n 
 (\fontsize\ \scriptsize\)\n (\linenos\ \\)))\n
  (setq org-latex-to-pdf-process\n   '(\pdflatex -shell-escape 
 -interaction nonstopmode -output-directory %o %f\\n \pdflatex 
 -shell-escape -interaction nonstopmode -output-directory %o %f\\n
  \pdflatex -shell-escape -interaction nonstopmode -output-directory %o 
 %f\))\n#+end_src\n\n#+name: another-listing\n#+begin_src pytho
 n 
  :exports code\n   x = str(y)\n#+end_src\n 0 22 (fontified t 
 font-lock-fontified t face org-meta-line) 22 23 (fontified t 
 font-lock-fontified t face org-meta-line) 23 58 (fontified t 
 font-lock-fontified t face org-meta-line) 58 59 (fontified t 
 font-lock-fontified t face org-meta-line) 59 97 (fontified t 
 font-lock-fontified t face org-meta-line) 97 98 (fontified t 
 font-lock-fontified t face org-meta-line) 98 161 (fontified t 
 font-lock-fontified t face org-meta-line) 161 162 (fontified t 
 font-lock-fontified t face org-meta-line) 162 163 (fontified t 
 :org-license-to-kill t) 163 183 (fontified t font-lock-fontified t face 
 org-meta-line) 183 184 (fontified t font-lock-fontified t face org-meta-line) 
 184 236 (fontified t font-lock-fontified t face org-block-begin-line 
 font-lock-multiline t) 236 237 (fontified t font-lock-fontified t 
 font-lock-multiline t face org-block-begin-line) 237 524 (fontified t 
 font-lock-fontified t font-lock-multiline t face org-block :org-license-to-kil
 l 
  t) 524 764 (fontified t font-lock-fontified t font-lock-multiline t face 
 org-block :org-license-to-kill t) 764 852 (fontified t font-lock-fontified t 
 font-lock-multiline t face org-block :org-license-to-kill t) 852 853 
 (fontified t font-lock-fontified t font-lock-multiline t face org-block 
 :org-license-to-kill t) 853 862 (fontified t font-lock-fontified t face 
 org-block-end-line font-lock-multiline t) 862 863 (fontified t 
 font-lock-fontified t face org-block-end-line) 863 864 (fontified t 
 :org-license-to-kill t) 864 887 (fontified t font-lock-fontified t face 
 org-meta-line) 887 888 (fontified t font-lock-fontified t face org-meta-line) 
 888 920 (fontified t font-lock-fontified t face org-block-begin-line 
 font-lock-multiline t) 920 921 (fontified t font-lock-fontified t 
 font-lock-multiline t face org-block-begin-line) 921 934 (fontified t 
 font-lock-fontified t font-lock-multiline t face org-block 
 :org-license-to-kill t) 934 935 (fontified t font-lock-fontified t 
 font-lock-mu
 lt
  iline t face org-block :org-license-to-kill t) 935