Re: Interest in an Org video meetup?

[Adham Omran]

Ihor Radchenko  writes:

> Russell Adams  writes:
>
>>> We can make EmacsConf instance of BigBlueButton (BBB) available, as
>>> well.  FWIW I had more success with BBB than Jitsi for larger
>>> meetings.
>
> This thread had no activity for a while.
> Let me take the lead then.
>
> I am now in UTC+3 zone and can host a meetup in the evening my time
> (~6-10pm).
>
> Say, early next month. Like Aug 9. (Alternative suggestions welcome; I
> just randomly selected something no too far and no too close from now.)
>
> I will need a BBB account though.
>
> -- 
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 

The date works for me and I have no issue with changing the date, as for
the time it has to be in the evening UTC+3 (5-9pm).  Thank you for
taking the lead Ihor.

--
Adham Omran

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

[Paul Stansell]

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).

  #+name: Table1
  | x |  y | notes  |
  |---++|
  | 0 |  0 | [[note_1]] |
  | 1 |  1 ||
  | 2 |  4 ||

  <>: a note

  #+begin_src gnuplot :var d=Table1 :results silent
plot [][] d u 1:2 w lp
  #+end_src

However, trying the same in the newer org versions 9.3 or 9.7-pre gives the
error:

  Unable to resolve link: "note_1"




Emacs  : GNU Emacs 28.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.37, cairo version 1.16.0)
 of 2023-03-16, modified by Debian
Package: Org mode version 9.7-pre (release_9.6.7-579-gde9f89 @
/home/ps/.emacs.d_Kubuntu-23.04/org-mode-git/lisp/)

current state:
==
(setq
 org-link-elisp-confirm-function 'yes-or-no-p
 org-bibtex-headline-format-function 'org-bibtex-headline-format-default
 org-persist-after-read-hook '(org-element--cache-persist-after-read)
 org-export-before-parsing-hook '(org-attach-expand-links)
 org-cycle-tab-first-hook '(org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-odt-format-inlinetask-function
'org-odt-format-inlinetask-default-function
 org-ascii-format-drawer-function #[771 " \207" [] 4 "\n\n(fn NAME CONTENTS
WIDTH)"]
 org-cycle-hook '(org-cycle-hide-archived-subtrees
org-cycle-show-empty-lines
 org-cycle-optimize-window-after-visibility-change
 org-cycle-display-inline-images)
 org-persist-before-read-hook '(org-element--cache-persist-before-read)
 org-mode-hook '(#[0 "\300\301\302\303\304$\207"
  [add-hook change-major-mode-hook org-fold-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-babel-load-languages '((gnuplot . t))
 org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
 org-latex-format-headline-function
'org-latex-format-headline-default-function
 org-confirm-shell-link-function 'yes-or-no-p
 org-html-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
 outline-isearch-open-invisible-function 'outline-isearch-open-invisible
 org-odt-format-headline-function 'org-odt-format-headline-default-function
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-speed-command-hook '(org-speed-command-activate
org-babel-speed-command-activate)
 org-html-format-inlinetask-function
'org-html-format-inlinetask-default-function
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
 org-fold-core-isearch-open-function 'org-fold--isearch-reveal
 org-latex-format-inlinetask-function
'org-latex-format-inlinetask-default-function
 org-persist-before-write-hook '(org-element--cache-persist-before-write)
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
 org-link-shell-confirm-function 'yes-or-no-p
 org-babel-pre-tangle-hook '(save-buffer)
 org-agenda-loop-over-headlines-in-active-region nil
 org-occur-hook '(org-first-headline-recenter)
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-link-parameters '(("attachment" :follow org-attach-follow :complete
org-attach-complete-link)
  ("id" :follow org-id-open)
  ("eww" :follow org-eww-open :store org-eww-store-link)
  ("rmail" :follow org-rmail-open :store org-rmail-store-link)
  ("mhe" :follow org-mhe-open :store org-mhe-store-link)
  ("irc" :follow org-irc-visit :store org-irc-store-link :export
org-irc-export)
  ("info" :follow org-info-open :export org-info-export :store
org-info-store-link :insert-description
org-info-description-as-command)
  ("gnus" :follow org-gnus-open :store org-gnus-store-link)
  ("docview" :follow org-docview-open :export org-docview-export :store
org-docview-store-link)
  ("bibtex" :follow org-bibtex-open :store org-bibtex-store-link)
  ("bbdb" :follow org-bbdb-open :export org-bbdb-export :complete
org-bbdb-complete-link :store org-bbdb-store-link)
  ("w3m" :store org-w3m-store-link)
  ("doi" :follow org-link-doi-open :export org-link-doi-export)
  ("file+sys") ("file+emacs") ("shell" :follow org-link--open-shell)
  ("news" :follow
#[514 "\301\300\302 Q \"\207" ["news" browse-url ":"] 6
 "\n\n(fn URL ARG)"]
)
  ("mailto" :follow
#[514 "\301\300\302 Q \"\207" ["mailto" browse-url ":"] 6
 "\n\n(fn URL ARG)"]
)
  ("https" :follow
#[514 "\301\300\302 Q \"\207" ["https" browse-url ":"] 6
 "\n\n(fn URL ARG)"]
)
  ("http" :follow
#[514 "\301\300\302 Q \"\207" ["http" browse-url ":"] 6
 "\n\n(fn URL ARG)"]
)
  ("ftp" :follow
#[514 

Re: IDs below headline level (for paragraphs, lists, etc) (was: [PATCH] org-id: allow using parent's existing id in links to headlines)

[Rick Lupton]

I can see this being useful in general, but not avoiding the need for my patch. 
Org links using search strings already strike a good compromise between working 
with arbitrary plain text, and allowing links to specific locations. When a 
search string is enough to find the thing you want to link to, there’s no need 
to add more IDs manually. 

If this is already intended to be an unrelated discussion then feel free to 
ignore this comment!

On Thu, 27 Jul 2023, at 8:42 AM, Ihor Radchenko wrote:
> Samuel Wales  writes:
>
>> ...  but what if those smaller things
>> could have ids without drawers?  id markers.  then changes in
>> surrounding text would not break anything.
>
> I recall similar idea raised in
> https://list.orgmode.org/orgmode/cajniy+ovd0ncwzztpit5t7wvsblbgllxzmpub5tgq3gshsg...@mail.gmail.com/
>
> But there was not much interest.
>
> It was pointed that we already have link targets, although they are not
> global. Making link targets global is doable.
>
> -- 
> 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

[Rick Lupton]

Hi Ihor,

Thanks for the comments, I will take a look. A question below. 

On Wed, 26 Jul 2023, at 9:10 AM, Ihor Radchenko wrote:
>
> I am looking at it from an opposite direction: we already have file:
> links with ::search term, but file is not a very reliable link anchor.
> File ID will persist even when the file is moved. So, instead of having
> something like , we should better also
> provide  with ID defined in the top-level property
> drawer. ID being some sub-heading is then a natural extension of the
> same idea.

This is a good description of the motivation from my point of view. 

> 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]]

Thanks
Rick

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?)

[Jonathan Gregory]

On 28 Jul 2023, Ihor Radchenko wrote:

I am slightly confused because there seems to be a need to 
define some page settings manually to get "embedded" images. In 
the examples in 
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html#org2c29903, 
there is no mention that we need to define page geometry. Yet, 
the section is claiming that base mode "can embed LilyPond 
snippets into an Org-mode file".


It is confusing, I agree, and I'm still learning as we move 
forward. I guess the question is should basic mode *always* 
generate cropped images? If the answer is yes, and it looks like 
it is, then maybe we should include paper settings in the 
ob-lilypond file.


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


Noweb and babel references are not allowed in header args. And 
ob-emacs-lisp also does not support :prologue.


I see, so there's no built-in way to auto-insert a boilerplate 
without using the <<>> reference *inside* source blocks. 
Anyway, let's not worry about this for now.


There is, but you will have to use direct Elisp to get :prologue 
string:


#+name: test
#+begin_src emacs-lisp

(message "This is test")
#+end_src

#+begin_src emacs-lisp :prologue (org-sbe test)
(+ 1 2)
#+end_src


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)


if we replace "lilypond" with "org" in the version-and-paper 
block. Prologue is useful also for those of us who keep their 
settings in a separate file:


#+PROPERTY: header-args:lilypond :exports results :prologue 
"\\include \"settings.ly\""


Thanks!

--
Jonathan

Re: Interest in an Org video meetup?

[Sacha Chua]

Hello, Ihor!

Thanks for taking the lead! I've sent you an invite from bbb.emacsverse.org.
Once you decide on a time and date, please let me know a week or two
beforehand so that I can put it in Emacs News. Do you want to go with Aug 9
at 6pm UTC+3?  I can't make it (still focused on kiddo), but maybe if at
least one or two other people confirm, then that could be a good starting
point and we can see who else shows up.


Sacha


On Thu, Jul 27, 2023, 03:52 Ihor Radchenko  wrote:

> Russell Adams  writes:
>
> >> We can make EmacsConf instance of BigBlueButton (BBB) available, as
> >> well.  FWIW I had more success with BBB than Jitsi for larger
> >> meetings.
>
> This thread had no activity for a while.
> Let me take the lead then.
>
> I am now in UTC+3 zone and can host a meetup in the evening my time
> (~6-10pm).
>
> Say, early next month. Like Aug 9. (Alternative suggestions welcome; I
> just randomly selected something no too far and no too close from now.)
>
> I will need a BBB account though.
>
> --
> 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?

[Ihor Radchenko]

Sacha Chua  writes:

> Thanks for taking the lead! I've sent you an invite from bbb.emacsverse.org.

Thanks!

> Once you decide on a time and date, please let me know a week or two
> beforehand so that I can put it in Emacs News. Do you want to go with Aug 9
> at 6pm UTC+3?  I can't make it (still focused on kiddo), but maybe if at
> least one or two other people confirm, then that could be a good starting
> point and we can see who else shows up.

Feel free to suggest an alternative date in August.
My main constraint is that time should be in the evening.
Can be any date others are comfortable with.

-- 
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/)]

[Bastien Guerry]

Hi Ihor and Jens,

Ihor Radchenko  writes:

> Bastien, may your please check FSF records?

Done, Jens records are okay.  Thanks for contributing!

-- 
 Bastien Guerry

Re: Subscript entity in the name of files or some advise for alternatives

[Ihor Radchenko]

Ypo  writes:

> I wanted to avoid this: "Campayo_2009_BLOQUE1Leyendo3FotosRenglon-2.png"
>
> to look like this:
>
> https://i.ibb.co/CJm99pG/Captura.png
>
>
> I have solved it by setting "Org Pretty Entities Include Sub 
> Superscripts" to nil.

You can set `org-use-sub-superscripts' to '{} as one option.
Or you can wrap file names into verbatim markers.

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

Re: [FR] Add an option to use ID links during tangling

[Ihor Radchenko]

Evgenii Klimov  writes:

>> Ideally, we should improve the detangling to understand the order of
>> blocks better instead of searching the containing heading independently.
>
> Maybe recent feature suggestion [1] will be of use here.
>
> [1] 
> https://list.orgmode.org/118435e8-0b20-46fd-af6a-88de8e19f...@app.fastmail.com

Detangling should work even when IDs are not used at all.
Using IDs will always be just a partial fix and leave edge cases.

The right thing to do would be something like
http://leoeditor.com/appendices.html#the-mulder-ream-update-algorithm
But we need someone™.

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

Re: [FR] Add an option to use ID links during tangling

[Evgenii Klimov]

Ihor Radchenko  writes:

> Evgenii Klimov  writes:
>
>> I see in the comment there the reason for that, but still would prefer
>> to use unique IDs in tangled files: the probability to overwrite wrong
>> source block under nonunique header overweights a side-effect of
>> creating new ID in Org file during tangling.
>
> Did you actually encounter such situation?
> `org-babel-detangle' is far from ideal in general.
> For example, detangling noweb references is pretty much guaranteed to
> create mess.

Yes, I did.  I keep my whole emacs configuration in an Org file and
tangle it after adjustments at Emacs startup (~org-babel-load-file~).
Recently I decided to split the tangled file and learned about
detangling.

And I have a lot of similar headers since my Org file looks like this:

#+begin_example
* package 1
** basic
** custom functions
** custom bindings
* package 2
** basic
** custom functions
** custom bindings
#+end_example

>> Can we do something with this?  Add another option or provide an even
>> eager value in =org-id-link-to-org-use-id=.
>
> I do not like the idea of creating side effects in the original Org
> document during tangling.
> We can, however, use (org-id-link-to-org-use-id 'use-existing) to use
> the already present IDs.

Understandable, with (org-id-link-to-org-use-id 'use-existing) I would
at least be able to manually add them where needed.

> Ideally, we should improve the detangling to understand the order of
> blocks better instead of searching the containing heading independently.

Maybe recent feature suggestion [1] will be of use here.

[1] 
https://list.orgmode.org/118435e8-0b20-46fd-af6a-88de8e19f...@app.fastmail.com

Re: New Orgmode LaTex Document Class ?

[Stefan Nobis]

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.

-- 
Until the next mail...,
Stefan.

Re: New Orgmode LaTex Document Class ?

[Ihor Radchenko]

David Masterson  writes:

> I want to install a resume document class for LaTex so that I can (more
> easily) write good looking resumes from Org.  I think I see how to
> identify the new document class to Org (org-latex-classes), but I'm not
> sure if that tells Org *where* the new document class is.

You need to install the class file where LaTeX can find it.
Either using your system package manager or into ~/texmf

You may check
https://tex.stackexchange.com/questions/1137/where-do-i-place-my-own-sty-or-cls-files-to-make-them-available-to-all-my-te
 
-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [FR] Add an option to use ID links during tangling

[Ihor Radchenko]

Evgenii Klimov  writes:

> I see in the comment there the reason for that, but still would prefer
> to use unique IDs in tangled files: the probability to overwrite wrong
> source block under nonunique header overweights a side-effect of
> creating new ID in Org file during tangling.

Did you actually encounter such situation?
`org-babel-detangle' is far from ideal in general.
For example, detangling noweb references is pretty much guaranteed to
create mess.

> Can we do something with this?  Add another option or provide an even
> eager value in =org-id-link-to-org-use-id=.

I do not like the idea of creating side effects in the original Org
document during tangling.
We can, however, use (org-id-link-to-org-use-id 'use-existing) to use
the already present IDs.

Ideally, we should improve the detangling to understand the order of
blocks better instead of searching the containing heading independently.

-- 
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:

>> May your please explain what is "basic mode".
>
> Basic mode is explained in 
> https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html. 
> In summary:
>
> With basic-mode you can embed LilyPond snippets into an Org-mode 
> file, compile and export them using typical Org-mode commands 
> (such as C-c C-e l p for PDF export). This is useful if you want 
> to mix blocks of LilyPond-generated score with text, and perhaps 
> other images to export to LaTeX, Docbook, PDF, or HTML.

I am slightly confused because there seems to be a need to define some
page settings manually to get "embedded" images. In the examples in
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html#org2c29903,
there is no mention that we need to define page geometry. Yet, the
section is claiming that base mode "can embed LilyPond snippets into an
Org-mode file".

What am I missing?

>> And what about users who do want a full page?
>
> In that case the user would use "arrange mode", which is also 
> explained in the ob-doc-lilypond.html page.

Thanks for the clarification!

>> Noweb and babel references are not allowed in header args. And 
>> ob-emacs-lisp also does not support :prologue.
>
> I see, so there's no built-in way to auto-insert a boilerplate 
> without using the <<>> reference *inside* source blocks. Anyway, 
> let's not worry about this for now.

There is, but you will have to use direct Elisp to get :prologue string:

#+name: test
#+begin_src emacs-lisp
(message "This is test")
#+end_src

#+begin_src emacs-lisp :prologue (org-sbe test)
(+ 1 2)
#+end_src

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

Re: [PATCH v5] ob-tangle.el: Blocks overwrite each other when grouping before tangling

[Ihor Radchenko]

Evgenii Klimov  writes:

> Hope new version is cleaner.

Thanks!
Applied, onto main. With minor amendments.
Fixed.

https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=fcac0039a
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=3ee10d57f

Amendments:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=410cecc0e

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

New Orgmode LaTex Document Class ?

[David Masterson]

I want to install a resume document class for LaTex so that I can (more
easily) write good looking resumes from Org.  I think I see how to
identify the new document class to Org (org-latex-classes), but I'm not
sure if that tells Org *where* the new document class is.  Do I have to
install the .cls file somewhere (where?) in my LaTex installation
(TexLive) or can it be referenced elsewhere (like $HOME/tex) by proper
configuration of an Org variable?  I'm not a LaTex user -- this is my
first attempt to add something to LaTex that I can then leverage in Org,
-- 
David Masterson