Re: [PATCH] Adaptive Org faces in headings?

[Protesilaos Stavrou]

On 2020-10-07, 00:20 -0400, Kyle Meyer  wrote:

> Protesilaos Stavrou writes:
>
>> Sorry to re-open this issue.  The following change extends Ihor's patch
>> to also cover checkbox statistics.  Seems to work just fine on my end.
>> Thanks again!
>
> Thanks for the patch.  Looks good on my end too.
>
> Would you mind adding a commit message and sending the git-format-patch
> output (details at )?

Tried to format the patch.  Please see the attached file.  If it does
not work, feel free to dismiss it and just apply the change yourself.

-- 
Protesilaos Stavrou
protesilaos.com
>From 6fc8c6f2c5c81402e2d4a5416b68d8d595f7aaee Mon Sep 17 00:00:00 2001
From: Protesilaos Stavrou 
Date: Wed, 7 Oct 2020 08:04:24 +0300
Subject: [PATCH] Make headline faces precede checkbox statistics

* lisp/org.el (org-set-font-lock-defaults): Apply `prepend' to
checkbox statistics.  Affects `org-checkbox-statistics-done' and
`org-checkbox-statistics-todo'.

This builds on commit 979e82fc3: org-level-N faces are no longer
overridden by elements placed on top of them.
---
 lisp/org.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/org.el b/lisp/org.el
index 425e9391b..23c86ba0c 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -5684,7 +5684,7 @@ needs to be inserted at a specific position in the font-lock sequence.")
 	 1 'org-checkbox prepend)
 	   (when (cdr (assq 'checkbox org-list-automatic-rules))
 	 '("\\[\\([0-9]*%\\)\\]\\|\\[\\([0-9]*\\)/\\([0-9]*\\)\\]"
-	   (0 (org-get-checkbox-statistics-face) t)))
+	   (0 (org-get-checkbox-statistics-face) prepend)))
 	   ;; Description list items
 	   '("^[ \t]*[-+*][ \t]+\\(.*?[ \t]+::\\)\\([ \t]+\\|$\\)"
 	 1 'org-list-dt prepend)
-- 
2.28.0

Re: Bug: [PATCH] org-agenda: "Invalid face reference: t" errors [9.4 (release_9.4-49-g4b150d @ /home/n/.emacs.d/straight/build/org/)]

[Kyle Meyer]

No Wayman writes:

> I noticed recently that my message buffer was getting clobbered 
> with thousands of Invalid face reference errors when moving point 
> around an org-agenda buffer. e.g.:
>
>> Invalid face reference: t [4519 times]
[...]
> I believe the face spec in the call to `add-face-text-property' in 
> `org-display-outline-path' is incorrect.
> The attached patch replaces it with an anonymous face, which works 
> on my end.

Yeah, I'd guess the invalid (t ...) slipped in because of the
(DISPLAY . PLIST) used for defface.

Applied (f0902bf18), appending a period to your changelog description.

Thanks.

Re: [PATCH] Adaptive Org faces in headings?

[Kyle Meyer]

Protesilaos Stavrou writes:

> Sorry to re-open this issue.  The following change extends Ihor's patch
> to also cover checkbox statistics.  Seems to work just fine on my end.
> Thanks again!

Thanks for the patch.  Looks good on my end too.

Would you mind adding a commit message and sending the git-format-patch
output (details at )?

Re: :auto-sitemap in org-publish-project-alist ??

[David Masterson]

Nicolas Goaziou  writes:

> Hello,
>
> David Masterson  writes:
>
>> David Masterson  writes:
>>
>>> My org-publish-project-alist kind of looks like this:
>>>
>>> (setq org-publish-project-alist
>>>   '(("orgfiles"
>>>  :base-directory "~/DSM/MyOrg/"
>>>  :base-extension "org"
>>>  :publishing-directory "~/Publish/html/"
>>>  :publishing-function org-html-publish-to-html
>>>  :headline-levels 6
>>>  :section-numbers t
>>>  :makeindex t
>>>  :auto-sitemap t
>>>  :exclude "init.org"
>>>  :with-toc nil)))
>>>
>>>
>>> If I publish my files, sitemap.org is made in a buffer and written to a
>>> file,  Thereafter, org-publish always says sitemap.org has been changed
>>> on disk and asks about updating it.  Since it is a generated file, that
>>> shouldn't be necessary.
>>>
>>> Is there a way to turn that off and just have it overwrite the file?
>>
>> Anyone seeing this?
>
> No. Could you M-x toggle-degug-on-quit, reproduce it, C-g when you're
> asked about updating the file, and send the backtrace?

I'm confused -- now it works!  Maybe when I updated to 9.4?  The
org-publish process seems to be taking a lot longer to walk thru the
files like it is checking more deeply.  It rebuilds the sitemap file and
runs it thru latex to produce a pdf which is correct.

I'll keep an eye on it and see if the problem comes back.

Thanks
-- 
David Masterson

Re: PATCH: Display point of code block point when confirming evaluation

[Kyle Meyer]

Kyle Meyer writes:

> That sounds reasonable to me, and the change looks fine to me.  My only
> thought is that perhaps the line number would be friendlier to report,
> but I don't feel strongly about that.
>
> I'll wait a few days for any babel users to chime in and then apply
> (unless you reply that you'd like to reroll it to use line numbers).

A couple of votes came in favor of using line numbers here, and the idea
of using the source block name was also brought up.  (Thanks, Timothy
and Eric, for the input.)

Jarmo, what do you think?

Re: [PATCH] Omit file description when :file-desc has nil value

[Kyle Meyer]

Matt Huszagh writes:

> I've made those fixes and attached the updated patch.

Applied (d9884cfa7).

Thank you!

Re: Bug: [PATCH] org-agenda: "Invalid face reference: t" errors [9.4 (release_9.4-49-g4b150d @ /home/n/.emacs.d/straight/build/org/)]

[Samuel Wales]

i can confirm these errors in maint [didn't confirm the patch or
workaround].  thanks for debugging what i could not.


On 10/5/20, No Wayman  wrote:
>
> I noticed recently that my message buffer was getting clobbered
> with thousands of Invalid face reference errors when moving point
> around an org-agenda buffer. e.g.:
>
>> Invalid face reference: t [4519 times]
>
> Git bisect points to commit
> 7a12e149907b5921011710d869b7554c35859c89
>
>> org.el (org-display-outline-path): Fix faces of the message
>>
>> * lisp/org.el (org-display-outline-path): Set :height as the
>> default face height, and don't change other face attributes.
>>
>> See a3576543f for a previous fix, and this discussion:
>> 
>
> As a workaround, setting `org-agenda-show-outline-path' to nil
> prevents the errors.
> I believe the face spec in the call to `add-face-text-property' in
> `org-display-outline-path' is incorrect.
> The attached patch replaces it with an anonymous face, which works
> on my end.
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html

Re: Bug: (bug?) org-id-find-id-in-file doesn't close files after finding id [9.4 (9.4-7-g3eccc5-elpaplus @ ~/spacemacs/elpa/develop/org-plus-contrib-20200921/)]

[Samuel Wales]

thank you to both of you from me too.

i have noticed that the same problem occurs for me with refile targets
alist.  putting a file there seems to open the buffer for some reason
and not close it even if it had not been closed.  this might require a
refile or an id lookup or so.

however, it does not require doing anything with that file.

i frequently get org archive files sticking around.  i am guessing
this is due to id lookup.


On 10/6/20, Nicolas Goaziou  wrote:
> Hello,
>
> this nkk  writes:
>
>> when running org-id-find-id-in-file on an id and an unvisited file, the
>> buffer it creates to visit file isn't
>> closed after finding id.
>>
>> ** what should have happened
>> I was expecting it to close the buffer if the
>> file wasn't already visited by another buffer.
>>
>> Is this desired behavior?
>
> It depends. If MARKERP is non-nil, you certainly don't want to close the
> newly created buffer. Otherwise, it could be closed, indeed.
>
> I patched master along these lines. Thank you.
>
> Regards,
> --
> Nicolas Goaziou
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html

Re: Shower thought: submit an IETF RFC to register Org as a MIME type

[Palak Mathur]

> On Oct 6, 2020, at 2:03 PM, TEC  wrote:
> 
> 
> Wes Hardaker  writes:
> 
>> Ok, I'll try to create a template we can fill out in github next week
>> (I'm swamped this week with a deadline).
> 
> Sounds good :) I'm fairly busy for the next ~month and a half anyway so
> I'm happy to accommodate delays.
> 
> Would it be a good idea to use the markdown RFC as a template? That's
> what I was originally thinking.
> 

Let me know if you need help. I can help out as well.


> Thanks,
> 
> Timothy.
> 

Re: Shower thought: submit an IETF RFC to register Org as a MIME type

[TEC]

Wes Hardaker  writes:

Ok, I'll try to create a template we can fill out in github next 
week

(I'm swamped this week with a deadline).


Sounds good :) I'm fairly busy for the next ~month and a half 
anyway so

I'm happy to accommodate delays.

Would it be a good idea to use the markdown RFC as a template? 
That's

what I was originally thinking.

Thanks,

Timothy.

Re: Shower thought: submit an IETF RFC to register Org as a MIME type

[Wes Hardaker]

TEC  writes:

> Wes Hardaker  writes:
> 
> > IETF person here.  If you want help or a co-author, I can help if
> > needed.
> >
> > [not a mime expert, but I've been involved with the IETF for ~25
> > years]
> 
> Fantastic! I've never summited an RFC or interacted with the IETF
> before in my life, so that sounds great to me :)

Ok, I'll try to create a template we can fill out in github next week
(I'm swamped this week with a deadline).
-- 
Wes Hardaker 
My Pictures:   http://capturedonearth.com/
My Thoughts:   http://blog.capturedonearth.com/

Re: Bug: Code block :results raw replace issue [9.3.7 (9.3.7-22-gbd9785-elpaplus @ /Users/skoshelev/.emacs.d/elpa/26.2/develop/org-plus-contrib-20200824/)]

[Sergey]

Thank you, Nicolas. I suspected as much.
I think it would be nice to update the manual to clearly state this behavior.


Cheers,
Sergey.

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Tuesday, October 6th, 2020 at 4:59 AM, Nicolas Goaziou 
 wrote:

> Hello,
>
> Sergey srg.koshe...@protonmail.com writes:
>
> > Code block header argument ~replace~ seems to not to work in conjunction
> >
> > with ~raw~. This leads to output being pre-pended instead of being
> >
> > replaced to the results block.
> >
> > Below is a working example:
> >
> > #+begin_src python :session python-test :results output raw replace
> >
> > print('This line will be added every time this code runs')
> >
> > #+end_src
> >
> > #+RESULTS:
> >
> > This line will be added every time this code runs
>
> This is expected. With "raw", Org has no way to determine where the
>
> output starts, ends, or even if there is one already. You may want to
>
> use another option if you want to replace results.
>
> Regards,
> --
>
> Nicolas Goaziou

Re: org-->latex add local variables after \end{document}

[Eric S Fraga]

On Tuesday,  6 Oct 2020 at 13:22, Uwe Brauer wrote:
> On problem of this approach is now: if I open this org file emacs uses
> LaTeX mode not org mode :-(

What if you remove the mode: line and let Emacs choose the mode
according to file name?

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.4-38-g16f505

Re: [PATCH] Omit file description when :file-desc has nil value

[Matt Huszagh]

Kyle Meyer  writes:

> So, with the typo/spurious space change clean-ups, this looks good to
> me.  IIRC from a previous thread, you haven't yet completed the
> copyright paperwork.  Is that the case?

I've made those fixes and attached the updated patch.

I also sent you the paperwork separately (didn't post to the thread
since the PDF is too large).

Thanks
Matt

>From 7452f3e8315be63fa8ae160f6be00963bac898a7 Mon Sep 17 00:00:00 2001
From: Matt Huszagh 
Date: Tue, 29 Sep 2020 14:11:59 -0700
Subject: [PATCH] lisp/ob-core.el: Allow passing empty vector to :file-desc to
 omit description

* doc/org-manual.org (Type): Document empty vector argument for
file-desc.
* etc/ORG-NEWS (New argument for ~file-desc~ babel header): Add entry
to NEWS.
* lisp/ob-core.el (org-babel--file-desc): Add new function to evaluate
file description value.
(org-babel-execute-src-block): Correctly evaluate file description
when executing src block.
(org-babel-insert-result): Correctly evaluate file description value
when inserting the result of src block execution into the buffer.
* testing/lisp/test-ob.el (test-ob/file-desc-header-argument): Add
test case for new behavior.
---
 doc/org-manual.org  |  8 +---
 etc/ORG-NEWS| 11 +++
 lisp/ob-core.el | 16 +++-
 testing/lisp/test-ob.el | 20 +++-
 4 files changed, 46 insertions(+), 9 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index e7d25b90e..ef2dad9ef 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -17482,10 +17482,12 @@ default behavior is to automatically determine the result type.
   #+end_example
 
   #+cindex: @samp{file-desc}, header argument
-  The =file-desc= header argument defines the description (see
-  [[*Link Format]]) for the link.  If =file-desc= is present but has no value,
+  The =file-desc= header argument defines the description (see [[*Link
+  Format]]) for the link.  If =file-desc= is present but has no value,
   the =file= value is used as the link description.  When this
-  argument is not present, the description is omitted.
+  argument is not present, the description is omitted.  If you want to
+  provide the =file-desc= argument but omit the description, you can
+  provide it with an empty vector (i.e., :file-desc []).
 
   #+cindex: @samp{sep}, header argument
   By default, Org assumes that a table written to a file has
diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index 5dc68cba4..7f935bf52 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -24,6 +24,17 @@ Earlier, IDs generated using =ts= method had a hard-coded format (i.e. =20200923
 The new option allows user to customise the format.
 Defaults are unchanged.
 
+*** New argument for ~file-desc~ babel header
+
+It is now possible to provide the =file-desc= header argument for a
+babel source block but omit the description by passing an empty vector
+as an argument (i.e., :file-desc []).  This can be useful because
+providing =file-desc= without an argument results in the result of
+=file= being used in the description.  Previously, the only way to
+omit a file description was to omit the header argument entirely,
+which made it difficult/impossible to provide a default value for
+=file-desc=.
+
 ** New features
 *** =ob-python= improvements to =:return= header argument 
 
diff --git a/lisp/ob-core.el b/lisp/ob-core.el
index 7300f239e..075e3f928 100644
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -646,6 +646,14 @@ a list with the following pattern:
   (replace-regexp-in-string
(org-src-coderef-regexp coderef) "" expand nil nil 1
 
+(defun org-babel--file-desc (params result)
+  "Retrieve file description."
+  (pcase (assq :file-desc params)
+(`nil nil)
+(`(:file-desc) result)
+(`(:file-desc . ,(and (pred stringp) val)) val)
+(`(:file-desc . []) nil)))
+
 ;;;###autoload
 (defun org-babel-execute-src-block ( arg info params)
   "Execute the current source code block.
@@ -749,8 +757,7 @@ block."
 		(let ((*this* (if (not file) result
 (org-babel-result-to-file
  file
- (let ((desc (assq :file-desc params)))
-   (and desc (or (cdr desc) result)))
+ (org-babel--file-desc params result)
 		  (setq result (org-babel-ref-resolve post))
 		  (when file
 			(setq result-params (remove "file" result-params))
@@ -2257,9 +2264,8 @@ INFO may provide the values of these header arguments (in the
 	 (setq result (org-no-properties result))
 	 (when (member "file" result-params)
 	   (setq result (org-babel-result-to-file
-			 result (when (assq :file-desc (nth 2 info))
-  (or (cdr (assq :file-desc (nth 2 info)))
-  result))
+			 result
+			 (org-babel--file-desc (nth 2 info) result)
 	((listp result))
 	(t (setq result (format "%S" result
   (if (and result-params (member "silent" result-params))
diff --git a/testing/lisp/test-ob.el b/testing/lisp/test-ob.el
index 648e9c115..df4b13498 100644
--- 

Re: org-->latex add local variables after \end{document}

[Uwe Brauer]

>>> "ESF" == Eric S Fraga  writes:

> On Monday,  5 Oct 2020 at 10:11, Uwe Brauer wrote:
>> Right this is correct and this is what I tried, however I hoped for a
>> more, hm, elegant solution. But on the other hand, what the heck...

> This is pretty much my view: elegance is a bonus but anything that works
> is enough!  But if somebody does know an elegant solution, please chime
> in. :-)

On problem of this approach is now: if I open this org file emacs uses
LaTeX mode not org mode :-(


smime.p7s
Description: S/MIME cryptographic signature

Re: A small idea to simplify (further) time input in the date/time prompt

[Gustavo Barros]

Hi All,
Hi Bastien,

if I may kindly bump this patch for review.

Best regards,
Gustavo.

On Wed, 03 Jun 2020 at 10:14, Gustavo Barros  
wrote:



Hi Bastien,

On Tue, Jun 02 2020, Bastien wrote:


Hi Gustavo,

I like this idea, thanks for proposing it.  We are in feature freeze
for core features, so we have time to work on this for Org 9.5.



[...]


Would you agree?  Would you like to work on this change?


Well, I did give it a shot.  And, as it turns out, this might be 
manageable within my limitations.


A preliminary patch is attached, for comments.

I took here the stance of following the same treatment which is given 
to 
am/pm times, and of using the letter "h" as sole main identifier.  In 
particular, standard "HH:MM" times take precedence, as is the case for 
am/pm times.  And duration specification with numbers only are 
presumed 
to be hours, which was already the case, the patch does not introduce 
any changes here.  The input will match for this format for "number h 
2-digit-number", where either the hour or the minutes, but not both, 
can 
be omitted and, if so, is presumed to be zero.  24h format is also 
presumed.


With it, some example inputs/outputs for time in the date/time prompt:

| input |  output |
|---+-|
| 9h|   09:00 |
| h45   |   00:45 |
| 21h   |   21:00 |
| 9h-10h| 09:00-10:00 |
| 9h--10h30 | 09:00-10:30 |
| 18h30+h30 | 18:30-19:00 |
| 18h30+1   | 18:30-19:30 |
| 18h30+1h  | 18:30-19:30 |

And some sanity checks:

| input | output   | Observation 
  |

|---+--+---|
| 10:00 9h  | 10:00| by design, as for am/pm times 
  |
| 10am 9h   | 10:00| expected from coming after am/pm 
  handling |
| 10:00-11h | 10:00-11:00  | 
  |
| 10h-11:00 | no match | am/pm also does not match here 
  |
| +9h   | no match | 
  |
| -9h   | no match | 
   |
| h | no match | 
  |
| 10h+h | no match | 
  |
| h5| no match | 
  |
| 10h70 | no match | 
  |
| 29h   | 2020-06-04 Thu 05:00 | makes sense, same as for 29:00 
  |
| 30h   | no match | as per the regexp 
  |


WDYT?

Best,
Gustavo.

Re: :auto-sitemap in org-publish-project-alist ??

[Nicolas Goaziou]

Hello,

David Masterson  writes:

> David Masterson  writes:
>
>> My org-publish-project-alist kind of looks like this:
>>
>> (setq org-publish-project-alist
>>   '(("orgfiles"
>>   :base-directory "~/DSM/MyOrg/"
>>   :base-extension "org"
>>   :publishing-directory "~/Publish/html/"
>>   :publishing-function org-html-publish-to-html
>>   :headline-levels 6
>>   :section-numbers t
>>   :makeindex t
>>   :auto-sitemap t
>>   :exclude "init.org"
>>   :with-toc nil)))
>>
>>
>> If I publish my files, sitemap.org is made in a buffer and written to a
>> file,  Thereafter, org-publish always says sitemap.org has been changed
>> on disk and asks about updating it.  Since it is a generated file, that
>> shouldn't be necessary.
>>
>> Is there a way to turn that off and just have it overwrite the file?
>
> Anyone seeing this?

No. Could you M-x toggle-degug-on-quit, reproduce it, C-g when you're
asked about updating the file, and send the backtrace?

Regards,
-- 
Nicolas Goaziou

Re: Bug: (bug?) org-id-find-id-in-file doesn't close files after finding id [9.4 (9.4-7-g3eccc5-elpaplus @ ~/spacemacs/elpa/develop/org-plus-contrib-20200921/)]

[Nicolas Goaziou]

Hello,

this nkk  writes:

> when running org-id-find-id-in-file on an id and an unvisited file, the
> buffer it creates to visit file isn't
> closed after finding id.
>
> ** what should have happened
> I was expecting it to close the buffer if the
> file wasn't already visited by another buffer.
>
> Is this desired behavior?

It depends. If MARKERP is non-nil, you certainly don't want to close the
newly created buffer. Otherwise, it could be closed, indeed.

I patched master along these lines. Thank you.

Regards,
-- 
Nicolas Goaziou

Re: Bug: Code block :results raw replace issue [9.3.7 (9.3.7-22-gbd9785-elpaplus @ /Users/skoshelev/.emacs.d/elpa/26.2/develop/org-plus-contrib-20200824/)]

[Nicolas Goaziou]

Hello,

Sergey  writes:

> Code block header argument ~replace~ seems to not to work in conjunction
> with ~raw~. This leads to output being pre-pended instead of being
> replaced to the results block.
>
> Below is a working example:
>
> #+begin_src python :session *python-test* :results output raw replace
> print('This line will be added every time this code runs')
> #+end_src
>
> #+RESULTS:
> This line will be added every time this code runs

This is expected. With "raw", Org has no way to determine where the
output starts, ends, or even if there is one already. You may want to
use another option if you want to replace results.

Regards,
-- 
Nicolas Goaziou

Bug: Code block :results raw replace issue [9.3.7 (9.3.7-22-gbd9785-elpaplus @ /Users/skoshelev/.emacs.d/elpa/26.2/develop/org-plus-contrib-20200824/)]

[Sergey]

Code block header argument ~replace~ seems to not to work in conjunction
with ~raw~. This leads to output being pre-pended instead of being
replaced to the results block.

Below is a working example:

#+begin_src python :session *python-test* :results output raw replace
print('This line will be added every time this code runs')
#+end_src

#+RESULTS:
This line will be added every time this code runs

Best regards,
Sergey Koshelev.

Setup info:

Emacs : GNU Emacs 26.2 (build 1, x86_64-apple-darwin18.2.0, NS appkit-1671.20 
Version 10.14.3 (Build 18D109))
of 2019-04-12
Package: Org mode version 9.3.7 (9.3.7-22-gbd9785-elpaplus @ 
/Users/skoshelev/.emacs.d/elpa/26.2/develop/org-plus-contrib-20200824/)

current state:
==
(setq
org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
org-latex-listings 'minted
org-capture-prepare-finalize-hook '(org-roam-capture--install-finalize)
org-link-shell-confirm-function 'yes-or-no-p
org-babel-after-execute-hook '(spacemacs/ob-fix-inline-images)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-roam-title-to-slug-function 'org-roam--title-to-slug
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-refile-targets '((org-agenda-files :maxlevel . 3))
org-html-format-inlinetask-function 'org-html-format-inlinetask-default-function
org-enforce-todo-dependencies t
org-src-tab-acts-natively t
org-odt-format-headline-function 'org-odt-format-headline-default-function
org-latex-pdf-process '("pdflatex -shell-escape -interaction nonstopmode 
-output-directory %o %f"
"pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f")
org-imenu-depth 8
org-download-annotate-function 'org-download-annotate-default
org-agenda-files '("~/org/gcal.org" "~/org/Projects.org" "~/org/brain/Brain.org"
"~/org/todo list.org")
org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
org-latex-to-mathml-convert-command "latexmlmath \"%i\" --presentationmathml=%o"
org-reveal-start-hook '(org-decrypt-entry)
org-modules '(org-habit ol-w3m ol-bbdb ol-bibtex ol-docview ol-gnus ol-info 
ol-irc ol-mhe ol-rmail
ol-eww)
org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent)
org-roam-buffer-prepare-hook '(org-roam-buffer--insert-title 
org-roam-buffer--insert-backlinks
org-roam-buffer--insert-ref-links)
org-archive-location "~/org/Archived projects.org::"
org-mode-hook '(org-tempo-setup flyspell-mode spacemacs/org-setup-evil-surround
spacemacs/load-yasnippet toc-org-enable org-superstar-mode
#[0 "\301\211\207" [imenu-create-index-function org-imenu-get-tree] 2]
#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-hook org-show-all append local] 5]
#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-hook org-babel-show-result-all append local] 5]
org-babel-result-hide-spec org-babel-hide-all-hashes org-download-enable
dotspacemacs//prettify-spacemacs-docs spacemacs//org-babel-do-load-languages
spacemacs//evil-org-mode org-eldoc-load spacemacs//init-company-org-mode
company-mode)
org-roam-mode t
org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
org-outline-path-complete-in-steps nil
org-archive-hook '(org-attach-archive-delete-maybe)
org-agenda-restore-windows-after-quit t
org-confirm-elisp-link-function 'yes-or-no-p
org-startup-indented t
org-gcal-fetch-file-alist '(("srg.koshe...@gmail.com" . "~/org/gcal.org")
("lifg1dsiqjkpd3ms7sq3sct...@group.calendar.google.com" .
"~/org/work.org")
)
org-roam-title-change-hook '(org-roam--update-file-name-on-title-change
org-roam--update-links-on-title-change)
org-brain-visualize-sort-function 'org-brain-title<
org-download-file-format-function 'org-download-file-format-default
org-roam-db-gc-threshold 402653184
org-roam-capture-function 'org-capture
org-journal-mode-hook '(#[0 "\301\302\303\304$\207"
[org-journal-encrypt-on add-hook org-journal-encryption-hook nil t] 5]
(lambda nil
(add-hook org-journal-encrypt-on (quote org-journal-encryption-hook) nil t)
)
)
org-projectile-per-project-filepath "TODOs.org"
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 "\n\n(fn 
ENTRY)"]
org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
org-babel-pre-tangle-hook '(save-buffer)
org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
org-babel-load-languages '((python . t) (calc . t) (shell . t) (gnuplot . t) 
(ditaa . t))
org-log-done 'time
org-journal-date-format "%A, %B %d %Y"
org-brain-visualize-mode-hook '((lambda nil
(define-key org-brain-visualize-mode-map (kbd "o")
(quote brain-open-narrow))
)
)
org-ascii-format-drawer-function #[771 "\207" [] 4 "\n\n(fn NAME CONTENTS 
WIDTH)"]
org-src-lang-modes '(("arduino" . arduino) ("redis" . redis) ("php" . php) ("C" 
. c) ("C++" . c++)
("asymptote" . asy) ("bash" . sh) ("beamer" . latex) ("calc" . fundamental)