Re: New Orgmode LaTex Document Class ?

[David Masterson]

Ihor Radchenko  writes:

> David Masterson  writes:
>
>> ...  Someone should
>> probably add something like this in the Org manual to help people begin
>> the bridge of setup into more advanced LaTex while using Org (maybe it's
>> there already?).
>
> It will not be productive to explain LaTeX in the Org manual. There are
> whole books dedicated to various aspects of LaTeX out there.
>
> The best we can do it pointing users to some resources about TeX or to
> the existence of such resources.

Agreed.  I was only suggesting a tidbit on how Org connects to LaTeX,
but, looking further at the docs, I think it is already covered.
Mentioning the (previously mentioned) 'kpsewhich' for finding what are
the LaTex classes (etc.) to which Org can refer might be useful.  From
there, the newbie (like me) can go research what the classes can do in
the LaTeX manuals.

-- 
David Masterson

Re: New Orgmode LaTex Document Class ?

[Ihor Radchenko]

David Masterson  writes:

> ...  Someone should
> probably add something like this in the Org manual to help people begin
> the bridge of setup into more advanced LaTex while using Org (maybe it's
> there already?).

It will not be productive to explain LaTeX in the Org manual. There are
whole books dedicated to various aspects of LaTeX out there.

The best we can do it pointing users to some resources about TeX or to
the existence of such resources.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Interest in an Org video meetup?

[Esteban Ordóñez]

Thank you very much Sachac and Igor.  I would love to attend.  I bet a
lot of other people would also.  I would expect about 10.

Re: Worg: issue with org-tools page

[Max Nikulin]

On 29/07/2023 19:14, Ihor Radchenko wrote:

I suspect that there is some misconfiguration of the build.


Despite the .build.yml file file installs the elpa-ess package, it is 
ignored when .org files are processed due to the --quick option in 
publish.sh. Perhaps --no-init-file (-q) will help, but it may cause 
other issues. Alternatively --directory (-L) may be added to specify the 
path to the ess package explicitly. Unfortunately it will make 
publish.sh less portable.


P.S. I am in doubts if it is reasonable to execute all src blocks on 
each build since it requires enough external dependencies. Committer 
should have them installed, so their should provide proper #+results:. 
Perhaps in some cases source blocks may be re-evaluated manually, e.g. 
before releases or when babel files are changed.

Re: New Orgmode LaTex Document Class ?

[David Masterson]

Stefan Nobis  writes:

> David Masterson  writes:
>
>> I want to install a resume document class for LaTex
>
> There are the variables org-latex-classes and org-latex-default-class
> on the Org side, but that's only about some structural metadata (how
> to map Org headline levels to LaTeX structure macros).
>
> To find the new class file you have to put it into a folder where
> LaTeX will find it. Org just puts the name of the class into the TeX
> file and everything else is up to LaTeX.
>
> Usually, on Unix systems, there is the optional hierarchy $HOME/texmf
> where you can store you private, local files. It is a good idea to
> mimic the usual TeX directory structure, therefore class and style
> files for LaTeX should go into $HOME/texmf/tex/latex (you may add
> subdirectories there).
>
> Nowadays it should suffice to just drop your class file there and
> everything should work on the LaTeX side.
>
> A quick check whether LaTeX will be able to find the file could be
> done with the tool kpsewhich:
>
> kpsewhich myltxclass.cls
>
> This tool uses the same configuration and search algorithms for the
> files as the TeX engines. So if kpsewhich finds the file, the engines
> should find it too.
>
> One side note: On macOS the default path for the user texmf tree is
> $HOME/Library/texmf. On all systems you may find the correct base
> directory for the user texmf tree with the command
>
> kpsewhich -var-value TEXMFHOME
>
> Hope this helps.

Thank you.  This is very helpful for a newbie like me.  Someone should
probably add something like this in the Org manual to help people begin
the bridge of setup into more advanced LaTex while using Org (maybe it's
there already?).

-- 
David Masterson

Re: [BUG] org-export-data: Unable to resolve link [9.7-pre (release_9.6.7-579-gde9f89)]

[Paul Stansell]

On Sat, 29 Jul 2023 at 09:30, Ihor Radchenko  wrote

>
> Thanks for reporting!
> Fixed, on main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=d38ca5923


 It's working fine now.  Thanks very much for your quick response!

Re: Worg: issue with org-tools page

[Ihor Radchenko]

Karl Voit  writes:

>> I believe that I fixed the issue in
>> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=4929f0c55f
>>
>> But I am not sure if I actually did. We need to trigger WORG rebuild to
>> see, I think.
>
> I just committed a minimal change to that file which caused the CI
> to re-build the page: https://builds.sr.ht/~bzg/job/975519 which
> ended successfully but still shows an error:

I suspect that there is some misconfiguration of the build.
But before we go into this, let's first address the problem with
publishing being silent when some files fail to be exported.
We cannot even notice the failures now unless we check changes manually!
WORG build thinks that publishing is "success" and does not trigger
failure email.

I am attaching tentative patch that will revert demoting errors to
messages. However, I do not fully understand the purpose of the original
`condition-case' code in the publish.sh. Bastien?

>From 1a26aa06f1504d7c9da650c83964351f3cc61715 Mon Sep 17 00:00:00 2001
Message-ID: <1a26aa06f1504d7c9da650c83964351f3cc61715.1690632604.git.yanta...@posteo.net>
From: Ihor Radchenko 
Date: Sat, 29 Jul 2023 15:08:59 +0300
Subject: [PATCH] * publish.sh: Trigger error when any file fails to export

If we do not throw an error, it may go unnoticed and will not trigger
CI report.

Link: https://orgmode.org/list/2023-04-18t15-32...@devnull.karl-voit.at
---
 publish.sh | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/publish.sh b/publish.sh
index fd931893..71c3a175 100755
--- a/publish.sh
+++ b/publish.sh
@@ -53,6 +53,4 @@
 	(message " [skipping] unchanged %s" org-file)
   (message "[exporting] %s" (file-relative-name org-file default-directory))
   (with-current-buffer (find-file org-file)
-	(condition-case err
-	(org-html-export-to-html)
-  (error (message (error-message-string err
+   (org-html-export-to-html)
-- 
2.41.0


-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH] org-id: allow using parent's existing id in links to headlines

[Ihor Radchenko]

"Rick Lupton"  writes:

>> What about inherited CUSTOM_ID?
>
> I’m not sure what you mean. 
>
> Are you thinking of CUSTOM_ID links, and whether they would behave 
> consistently with a search string to this proposal? Like: 
> [[custom-id:my-id::*H2][H2]]
>
> Or using custom id as a search string? Like: [[id:abc::#my-id][Description]]

No. I was thinking about something like [[#my-id::search string]].
However, this will only make sense in internal links. file: links would
need multiple search terms, which we currently do not support.

So, never mind my comment.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] org-export-data: Unable to resolve link [9.7-pre (release_9.6.7-579-gde9f89)]

[Ihor Radchenko]

Paul Stansell  writes:

> In org version 9.3, the gnuplot code block below successfully plots the data
> in Table1 (which includes a local hyperlink in the last column).
> ...
> However, trying the same in the newer org versions 9.3 or 9.7-pre gives the
> error:
>
>   Unable to resolve link: "note_1"

Thanks for reporting!
Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=d38ca5923

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] Issues in ol-gnus when storing links in nnvirtual and nnselect articles [9.7-pre (release_9.6.7-570-gd6f3ae.dirty @ /home/jschmidt/work/org-mode/lisp/)]

[Ihor Radchenko]

Bastien Guerry  writes:

>> Bastien, may your please check FSF records?
>
> Done, Jens records are okay.  Thanks for contributing!

Thanks for checking!
Updated our records.
https://git.sr.ht/~bzg/worg/commit/95559f89

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] WORG example for ob-lilypond is no longer working as described (was: Moving some lisp/ob-*.el files to org-contrib - your advice?)

[Ihor Radchenko]

Jonathan Gregory  writes:

> The basic-mode term is not very helpful. Perhaps 
> [inline/cropped/embedded]-mode would have been more descriptive in 
> terms of what it does.

Sounds reasonable. I like "inline-mode", although no strong opinion.

> ... Anyway, hard-coding paper settings would 
> simplify things a bit, but I'm not sure that hard-coding the 
> version is a good idea and may produce errors with older 
> installations.

Do people have reasons to use older versions even when they could use
the newest?

For example, python2/3 or MathJax4,4- were breaking and some people were
relying on legacy code. So, we had to provide some extra versions checks
and toggles on Org side as well.

>> #+name: test
>> #+begin_src emacs-lisp
>> (message "This is test")
>> #+end_src
>>
>> #+begin_src emacs-lisp :prologue (org-sbe test)
>> (+ 1 2)
>> #+end_src

Correction: `org-sbe' will execute src block. So, my example is not
completely accurate. Getting src block body is still doable, but a tiny
bit more tricky:

#+begin_src emacs-lisp :prologue (org-babel-ref-resolve "test[]")
(+ 1 2)
#+end_src

It think that it will be logical to add reference resolution to
:prologue/:epilogue. I will see what I can do.
(I may need to look through which header args are resolved and which are
not - there seems to be no consistency)

> Interesting. I didn't know about org-sbe. Looks useful. I'll look 
> into it when I find time. In the meantime, we can use:
>
> #+PROPERTY: header-args:lilypond :noweb yes :exports results 
>  :prologue (org-sbe version-and-paper)

(This will work because ob-org, by accident, produces body as result of
evaluation, with default header args)

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH] Re: [bug] Setting org-id-link-to-org-use-id to t creates IDs properties when tangling

[Ihor Radchenko]

Bastien  writes:

> Ihor Radchenko  writes:
>
>> The fix is attached.
>
> Applied, thanks!

In a recent feature request [1], one user expressed an interest in using
ID links during tangling, as they are more reliable wrt heading renames.

I am now re-considering this fix.

`org-id-link-to-org-use-id', apart from t, can be set to
'create-if-interactive, which could be used by people who do not want ID
links be created during tangling.

Rodrigo, would setting org-id-link-to-org-use-id to
'create-if-interactive work for you?

[1] https://orgmode.org/list/874jlouytx@lipklim.org

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at