Dear all,

Here are the meetup notes (finally, on time, *before* the next meetup).

TL;DR: WIP multi-language PDF exports feature; multiple images as
output of R blocks; which-key-popup-type; completing bibtex citation
keys; citation styles list missing from Org manual.

- As usual, we started from the latest Emacs news
  https://sachachua.com/blog/2025/10/2025-10-06-emacs-news/

- Pedro shared his updates on multi-lang export branch
  (ongoing discussion: <https://list.orgmode.org/87ms5frp9v.fsf@localhost/T/#t>)
  - We discussed using babel vs polyglossia
    - AFAIK, LaTeX project officially supports babel as multi-language package
    - However, Pedro has more experience with polyglossia, so we
      include it as well.
  - We also discussed the intricacies of getting non-Latin fonts for pdflatex
    - This is non-trivial, although possible for some languages
    - In the past, we found one website that has instructions how to configure 
pdflatex
      for various languages, but later found that the instructions do not 
always work
    - I later (after the meetup) found
      
https://en.wikibooks.org/wiki/LaTeX/Internationalization#Specific_languages
      - We will include it in the manual
  - We also discussed that we may need to give users instructions about 
including
    other languages
    - In polyglossia, you can do
      : #+begin_greek
      : ...
      : #+end_greek
      which will directly translate into (=\begin{greek}...\end{greek}=)
    - Alas, babel is different. It uses =foreignlanguage= environment.
    - Will need to document both in the manual, maybe adding a special 
environment
      to Org mode in figure, so that users do not need to change the Org markup
      when they switch between babel and polyglossia

- Pedro also shared his manual setup for Org export menu
  - Rather than using built-in menu, he uses which-key with custom keymap
  - He also sets ~which-key-popup-type~ to show the which-key popups
    in the echo area rather than in a popup window
  - We are working on something similar in 
https://list.orgmode.org/orgmode/[email protected]/
    - There, the idea is to make Org menus use something built-in
      (transient/which-key/menus/etc) instead of rolling out custom menus

- yaca shared his problem with exporting R blocks
  - What he does is creating *multiple* images as an output (=:results graphics 
file=)
  - This is not what =ob-R.el= knows how to handle, so only one of the
    images is actually used as the output
  - We, however, managed to implement custom way to save multiple images
    - The idea is to write R block that will directly save images to disk using 
R code
      and then make use of =:results raw output=, directly printing links to 
*all*
      images in Org markup as
      : [[file:/path/to/image1]]
      : [[file:/path/to/image2]]
      : ...
    - This is pretty manual, but works

- yaca also asked about a way to get completion for citation keys in Org
  - By default, ~M-x org-cite-insert~ presents a minibuffer completion, but
    you can only match by author/title/year, not using underlying bibtex 
citation key
  - We than looked into https://github.com/emacs-citar/citar
    - AFAIR, you still cannot complete by bibtex keys by default
    - However, we found that =citar-capf= can do it:
      https://github.com/emacs-citar/citar?tab=readme-ov-file#citar-capf
      via in-buffer completion.

- yaca (AFAIR), also pointed that Org mode manual does not tell about citation 
styles
  that are available
  - Something like  
https://blog.tecosaur.com/tmio/2021-07-31-citations.html#cite-styles
    would be useful to have
  - Patches welcome! See https://orgmode.org/worg/org-contribute.html

- We than ran out of topics to discuss
  - I turned to Emacs news, and looked into org-social 
    https://github.com/tanrax/org-social
    and JS rendered you can load into HTML to directly transform raw Org markup
    into HTML rendering https://docs.lepisma.xyz/orgdeep/
  - However, none of the topics got traction, so we ended the meetup
  - Just 1:30 hours this time :)

:comments:
[17:52] yantar92 is now the presenter
[18:01] [yantar92 : MODERATOR]: The latest Emacs news: 
https://sachachua.com/blog/2025/10/2025-10-06-emacs-news/
[18:02] [yantar92 : MODERATOR]: We will wait a few minutes, so that more people 
can join. Then start
[18:05] Pedro A. Aranda is now the presenter, set by yantar92
[18:15] [yantar92 : MODERATOR]: which-key-popup-type
[18:16] yantar92 is now the presenter, set by yantar92
[18:33] [yaca : VIEWER]: I have some question
[18:34] [yaca : VIEWER]: Kinda regarding latex export 
[18:34] [yaca : VIEWER]: Mostly exporting graphs from an R sourceblock
[18:34] [yaca : VIEWER]: I'm trying to generate a plot for each element in an R 
loop. However, with current orgmode syntax, only the last plot is exported to 
pdf, whereas in Rmarkdown I can export all plots.
[18:34] [yaca : VIEWER]: I am 5 minutes away from my computer, but i can run to 
my office haha
[18:36] [yaca : VIEWER]: Ok, let me run to my office and I can share my screen
[18:38] [yaca : VIEWER]: Ok give me 1 sec
[18:40] [yantar92 : MODERATOR]: A reminder that we have 
https://pad.emacsconf.org/orgmeetup to write during and after the meetup
[18:40] yacaPC is now the presenter, set by yantar92
[18:52] [yantar92 : MODERATOR]: [[file:/path/to/file.png]]
[18:54] yantar92 is now the presenter, set by yantar92
[19:01] yacaPC is now the presenter, set by yantar92
[19:08] [yantar92 : MODERATOR]: https://github.com/emacs-citar/citar
[19:14] [yantar92 : MODERATOR]: M-: (citar-capf-setup)
[19:16] yantar92 is now the presenter, set by yantar92
[19:16] [yacaPC : VIEWER]: 
https://blog.tecosaur.com/tmio/2021-07-31-citations.html#cite-styles
[19:18] [yantar92 : MODERATOR]: https://orgmode.org/worg/org-contribute.html
[19:20] [Christian Moe : VIEWER]: This was an amazing live help session to 
follow!
:end:

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Reply via email to