Case insensitivity of simple [[links]]

[Rudolf Adamkovič]

Howdy!

A while ago, I asked about case insensitivity of the syntactically
simplest "[[links]]" in Org.  I am interested in using these links
because they are the most practical with the "literal" view.

In 'emacs -Q' Org 9.6.9, "[[links]]" are case _sensitive_ when looking
for headings.  This was originally not the case, and case _insensitive_
linking was broken in Org 7 and then fixed in Org 8, as per [1] and [2].
Is it broken again?  I ask because 'org-link-search' documentation says
that search is "case-insensitive and ignores white spaces".

On top of the above, yesterday I noticed that

  (setq org-link-search-must-match-exact-headline nil)

makes "[[link]]" find "* Link" when clicked.  My joy was short-lived,
however, as I soon found that I cannot export anything due to

  org-export-data: Unable to resolve link: "link".

As a user, I am a bit lost here.  I cannot figure out what is a bug and
what is a feature in all of the above.  In a nutshell, all I want is to
make "[[link]]" find "* Link" while editing, after exporting, and on any
Emacs, that is 'emacs -Q'.  I have been struggling with this problem for
a while now, down-casing my headings as a workaround.  Any ideas?

Thank you!

Rudy

[1]
https://stackoverflow.com/questions/35542208/how-to-make-internal-link-in-org-mode-case-insensitive

[2] 
https://emacs.stackexchange.com/questions/20441/how-to-make-internal-links-in-org-mode-case-insensitive

-- 
"All you have to do is write one true sentence.  Write the truest sentence that
you know."
--- Ernest Miller Hemingway (1899-1961)

Rudolf Adamkovič  [he/him]
Studenohorská 25
84103 Bratislava
Slovakia

Re: Exporting elisp: and shell: links

[Rudolf Adamkovič]

Ihor Radchenko  writes:

> Another idea: use code as description displayed in the tooltip (in html).
> Copy-on-clip also makes sense.
>
> Yet another idea: export code inside a footnote. This will work across
> all the backends.

Yet another, another idea: export the description as a Lisp comment,
after converting it to plain text.  To use Max's example:

src_elisp[:exports code]{(server-start) ; Launch server}
src_elisp[:exports code]{(server-start) ; `M-x server-start RET'}

Rudy
-- 
"Logic is a science of the necessary laws of thought, without which no
employment of the understanding and the reason takes place."
-- Immanuel Kant, 1785

Rudolf Adamkovič  [he/him]
Studenohorská 25
84103 Bratislava
Slovakia

Re: [FR] Make notion of "modification time" configurable during publishing

[Suhail Singh]

Ihor Radchenko writes:

> I am a bit confused. What do you mean by "git author date" and "git
> commit date"?

In the output of `git log --pretty=fuller`, there is AuthorDate which is
distinct from CommitDate. In case unfamiliar, an elaboration on the
distinction: .

> I think that we should use an alternative approach. Both "git time" and
> "fs time" are only an approximation. The true decision to re-publish an
> article should be triggered by article text being modified. So, we may
> better decide based on the file text hash, not the modification times.

For it to work, the "file text hash" would have to also take into
account the "file text hash" of included files, or the decision to
re-publish would have to be predicated on the hash of included files as
well. I.e., the equivalent of this logic in
org-publish-cache-file-needs-publishing :

(let ((mtime (org-publish-cache-mtime-of-src filename)))
  (or (time-less-p pstamp mtime)
  (cl-some (lambda (ct) (time-less-p mtime ct))
   included-files-mtime)))

But assuming the existence of equivalent logic, yes something like a
file hash would work. In fact, at least in the case of git, the VCS
could even be queried for it (via git hash-object).

-- 
Suhail

Re: [BUG] org-element-context doesn't recognize link inside property drawer [9.6.6 (release_9.6.6 @ /usr/local/share/emacs/29.1/lisp/org/)]

[Gustavo Barros]

On Fri, 22 Sept 2023 at 15:11, Gustavo Barros  wrote:

Sorry, some poor copy-paste from my part on the original report. The
following...

> (Setting `eval-expression-print-level' and
> `eval-expression-print-length' to nil).

... was meant to come after:

> Placing point on the link and calling `(org-element-context)' returns:

It doesn't make sense where it was placed.

[BUG] Point position with org-open-at-point on a heading [9.6.6 (release_9.6.6 @ /usr/local/share/emacs/29.1/lisp/org/)]

[Gustavo Barros]

Hi All,

When point is on a heading, `org-open-at-point' offers to open links
in the subtree. This is a very useful feature, and I use it a lot.
However, in this case, `org-open-at-point' not only opens the link,
but also moves point to said link. Perhaps there's some reason why
point is not preserved in this case. But for me at least, this is not
what I'd expect, and I find it somewhat disrupting, especially when
I'm working on a folded tree (defeats speed keys, etc.).

A simple test file to reproduce the described behavior:

#+begin_src org
,* Heading

Foo.

https://orgmode.org/

Bar.
#+end_src

How about adding a `save-excursion' for this case inside `org-open-at-point'?

Best regards,
Gustavo.


Emacs  : GNU Emacs 29.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version
3.24.33, cairo version 1.16.0)
 of 2023-07-30
Package: Org mode version 9.6.6 (release_9.6.6 @
/usr/local/share/emacs/29.1/lisp/org/)

current state:
==
(setq
 org-link-elisp-confirm-function 'yes-or-no-p
 org-bibtex-headline-format-function #[257 "\300 \236A\207" [:title] 3
"\n\n(fn ENTRY)"]
 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-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-confirm-shell-link-function 'yes-or-no-p
 outline-isearch-open-invisible-function 'outline-isearch-open-invisible
 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-persist-directory "/tmp/org-persist-IhBaHK"
 org-fold-core-isearch-open-function 'org-fold--isearch-reveal
 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 "\301\300\302 Q \"\207" ["ftp" browse-url ":"]
  

[BUG] org-element-context doesn't recognize link inside property drawer [9.6.6 (release_9.6.6 @ /usr/local/share/emacs/29.1/lisp/org/)]

[Gustavo Barros]

Hi All,

When a link is placed as a property value, `org-element-context' does
not recognize it as a link.
(Setting `eval-expression-print-level' and
`eval-expression-print-length' to nil).

Consider the following document:

#+begin_src org
,* Heading
:PROPERTIES:
:LINK: [[https://orgmode.org/][Org mode for Emacs]]
:END:
#+end_src

Placing point on the link and calling `(org-element-context)' returns:

#+begin_src emacs-lisp
(node-property
 (:key "LINK"
  :value "[[https://orgmode.org/][Org mode for Emacs]]"
  :begin 24
  :end 76
  :post-blank 0
  :post-affiliated 24
  :mode node-property
  :granularity element
  :cached t
  :parent
  (property-drawer
   (:begin 11
:end 82
:contents-begin 24
:contents-end 76
:post-blank 0
:post-affiliated 11
:mode planning
:granularity element
:cached t
:parent
(section
 (:begin 11
  :end 82
  :contents-begin 11
  :contents-end 82
  :robust-begin 11
  :robust-end 80
  :post-blank 0
  :post-affiliated 11
  :mode section
  :granularity element
  :cached t
  :parent
  (headline
   (:raw-value "Heading"
:begin 1
:end 82
:pre-blank 0
:contents-begin 11
:contents-end 82
:robust-begin nil
:robust-end nil
:level 1
:priority nil
:tags nil
:todo-keyword nil
:todo-type nil
:post-blank 0
:footnote-section-p nil
:archivedp nil
:commentedp nil
:post-affiliated 1
:LINK "[[https://orgmode.org/][Org mode for Emacs]]"
:title "Heading"
:mode first-section
:granularity element
:cached t
:parent
(org-data
 (:begin 1
  :contents-begin 1
  :contents-end 82
  :end 82
  :robust-begin 3
  :robust-end 80
  :post-blank 0
  :post-affiliated 1
  :path "~/test.org"
  :mode org-data
  :CATEGORY "test"
  :cached t))
#+end_src

In particular, the "link" element is not present, as would be the case
if the exact same link were not inside the property drawer. On the
other hand, the link is active (fontified, works, etc.). Thus,
`org-element.el` and `ol.el` seem to disagree as to what that part of
the buffer actually is.

Best regards,
Gustavo.


Emacs  : GNU Emacs 29.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version
3.24.33, cairo version 1.16.0)
 of 2023-07-30
Package: Org mode version 9.6.6 (release_9.6.6 @
/usr/local/share/emacs/29.1/lisp/org/)

current state:
==
(setq
 org-link-elisp-confirm-function 'yes-or-no-p
 org-bibtex-headline-format-function #[257 "\300 \236A\207" [:title] 3
"\n\n(fn ENTRY)"]
 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-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-confirm-shell-link-function 'yes-or-no-p
 outline-isearch-open-invisible-function 'outline-isearch-open-invisible
 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-persist-directory "/tmp/org-persist-DRjSU9"
 org-fold-core-isearch-open-function 'org-fold--isearch-reveal
 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)
 

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Fri, Sep 22, 2023 at 5:13 PM Juan Manuel Macías 
wrote:

> Zenny writes:
>
> > Appended the above line, but the rendering became much worse, see
> > Ganapati and BiSht lines:
>
> Well, try this:
>
> 1. remove \newfontscript{Devanagari}{deva}
>
> 2. modify the \babelprovide for Bengali like this:
>
> \babelprovide[onchar=ids fonts,import,script=Bengali]{sanskrit-bengali}
>
> (it seems like something strange is happening between the Noto Sans
> Bengali font and LuaTeX. I don't know if it's a bug, but if I explicitly
> add the script name, it seems to render the words well. With Noto Serif
> Bengali it doesn't happen).
>

Thank you, I made the changes as you advised and changed the font to Noto
Serif variant, and it worked like wonder.

The problem is solved. Thanks a zillion.

Now it renders alright as seen in the screenshot. Have a nice weekend, Juan.


>
> Sorry, I'm afraid I don't know the language, so I'm going a bit blind
> here...
>


-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

Re: [BUG] [PATCH] Add yank-media and DND handler [9.6.7 (9.6.7-g6eb773 @ /home/viz/lib/emacs/straight/build/org/)]

[Visuwesh]

[வெள்ளி செப்டம்பர் 22, 2023] Max Nikulin wrote:

> On 22/09/2023 21:52, Visuwesh wrote:
>> Attached patch adds yank-media and DND handler to attach files in the
>> clipboard and dropped onto an Emacs frame respectively.
>
> Thank you for your work in this area.
>
> I am not an active DND user, I am just curious what cases are supported:
>
> - X11

Yes.

> - Wayland

I don't know nor am I willing to setup a test environment for it.

> - Sandboxed applications communicating with desktop environment
>   through XDG desktop portal (flatpack/snap/AppImage or just running
>  in bubblewrap)

Same as above.

> - Emacs running on a remote host (ssh + X11 forwarding)

If the DND links are of the form file://HOST/ then the current DND
handler won't run.  I don't have a way to test it myself so I can't
write a handler for remote files.  I am not sure if we can even reuse
the existing the org-attach code for remote files.

> - Windows

I don't have access to a Windows machine so can't test it unfortunately.

> When a file is dropped into an Org buffer I would consider inserting a
> link or storing it in addition to attachment options.

The current code already inserts a link to the dropped files.

Re: [BUG] [PATCH] Add yank-media and DND handler [9.6.7 (9.6.7-g6eb773 @ /home/viz/lib/emacs/straight/build/org/)]

[Max Nikulin]

On 22/09/2023 21:52, Visuwesh wrote:

Attached patch adds yank-media and DND handler to attach files in the
clipboard and dropped onto an Emacs frame respectively.


Thank you for your work in this area.

I am not an active DND user, I am just curious what cases are supported:

- X11
- Wayland
- Sandboxed applications communicating with desktop environment through 
XDG desktop portal (flatpack/snap/AppImage or just running in bubblewrap)

- Emacs running on a remote host (ssh + X11 forwarding)
- Windows

When a file is dropped into an Org buffer I would consider inserting a 
link or storing it in addition to attachment options.

Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword

[Max Nikulin]

On 17/09/2023 01:00, Juan Manuel Macías wrote:


[1] A longer example to export to a pdf that has pdf-x compliance, with
the pdfx package:

\providecommand{\pdfxopts}{x-1a}
\begin{filecontents*}{\jobname.xmpdata}
   \Title{Some Title}
   \Author{Author}
   \Language{es-ES}
   \Keywords{keywords}
   \Publisher{publisher}
\end{filecontents*}
\documentclass{...


Perhaps you have in mind other cases, but I am unsure concerning this 
one. However I have tried only setting metadata for hyperref only, so I 
may miss some important aspects.


First of all, I was unaware of .xmpdata and, trying to get more info, I 
have found hyperxmp that declares to reuse data from \hypersetup without 
extra files and without the requirement to add settings before 
\documentclass.


Do you need to add commands before \documentclass because you are using 
custom classes that loads a lot of packages, so there is no chance to 
specify various options after \documentclass, but before specific 
packages are loaded?


I do not think the lines above should be used directly in 
LATEX_PRE_HEADER. They should be generated from #+AUTHOR:, #+TITLE:, 
#+LANGUAGE: keywords. Have you considered the option to generate 
.xmpdata files directly from Org instead of delegating the task to LaTeX?


Another idea is to try export filter to insert content of a source block 
to the beginning of the export buffer. Unsure if it is convenient.

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Zenny writes:

> Appended the above line, but the rendering became much worse, see
> Ganapati and BiSht lines:

Well, try this:

1. remove \newfontscript{Devanagari}{deva}

2. modify the \babelprovide for Bengali like this:

\babelprovide[onchar=ids fonts,import,script=Bengali]{sanskrit-bengali}

(it seems like something strange is happening between the Noto Sans
Bengali font and LuaTeX. I don't know if it's a bug, but if I explicitly
add the script name, it seems to render the words well. With Noto Serif
Bengali it doesn't happen).

Sorry, I'm afraid I don't know the language, so I'm going a bit blind
here...

[BUG] [PATCH] Add yank-media and DND handler [9.6.7 (9.6.7-g6eb773 @ /home/viz/lib/emacs/straight/build/org/)]

[Visuwesh]

Attached patch adds yank-media and DND handler to attach files in the
clipboard and dropped onto an Emacs frame respectively.

The yank-media handler for images is well tested, I use it frequently
however, rest of the stuff aren't really tested since I don't use a GUI
file manager.  I tested enough to make sure the logic is right so I
don't know if they are ergonomic enough.  As noted in the comments,
files copied/cut to clipboard doesn't seem to have a solid spec and most
of the code was written with pcmanfm as the file manager, testing with
other file managers are highly welcome.

Better names for the newly added defcustoms are highly welcome since I
don't find them to be clear enough from their name.

The patch compiles cleanly without warnings but I haven't tested _this_
patch yet, I have these functions in my init.el and have tested those.

>From b6f1315cbdc331f2f54e1801b03272915d344cfd Mon Sep 17 00:00:00 2001
From: Visuwesh 
Date: Fri, 22 Sep 2023 20:11:41 +0530
Subject: [PATCH] Add support for yank-media and DND

* lisp/org.el (org-mode): Call the setup function for yank-media and
DND.
(org-setup-yank-dnd-handlers): Register yank-media-handler and DND
handler.
(org-media-image-save-type, org-dnd-default-attach-method): New
defcustoms.
(org--image-yank-media-handler, org--copied-files-yank-media-handler)
(org--dnd-local-file-handler): Add yank-media and DND handlers.

* etc/ORG-NEWS: Advertise the new features.
---
 etc/ORG-NEWS |  16 ++
 lisp/org.el  | 153 +--
 2 files changed, 164 insertions(+), 5 deletions(-)

diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index 252c5a9..f193c54 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -596,6 +596,22 @@ return a matplotlib Figure object to plot. For output results, the
 current figure (as returned by =pyplot.gcf()=) is cleared before
 evaluation, and then plotted afterwards.
 
+*** Images and files in clipboard can be attached
+
+Org can now attach images in clipboard and files copied/cut to the
+clipboard from file managers using the ~yank-media~ command which also
+inserts a link to the attached file.
+
+Images can be saved to a separate directory instead of being attached,
+customize ~org-media-image-save-type~.
+
+*** Files and images can be attached by dropping onto Emacs
+
+Attachment method other than ~org-attach-method~ for dropped files can
+be specified using ~org-dnd-default-attach-method~.
+
+Images dropped also respect the value of ~org-media-image-save-type~.
+
 ** New functions and changes in function arguments
 *** =TYPES= argument in ~org-element-lineage~ can now be a symbol
 
diff --git a/lisp/org.el b/lisp/org.el
index d0b2355..5c66f04 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -4999,7 +4999,10 @@ The following commands are available:
   (org--set-faces-extend '(org-block-begin-line org-block-end-line)
  org-fontify-whole-block-delimiter-line)
   (org--set-faces-extend org-level-faces org-fontify-whole-heading-line)
-  (setq-local org-mode-loading nil))
+  (setq-local org-mode-loading nil)
+
+  ;; `yank-media' handler and DND support.
+  (org-setup-yank-dnd-handlers))
 
 ;; Update `customize-package-emacs-version-alist'
 (add-to-list 'customize-package-emacs-version-alist
@@ -15125,20 +15128,20 @@ INCREMENT-STEP divisor."
 	(setq hour (mod hour 24))
 	(setq pos-match-group 1
   new (format "-%02d:%02d" hour minute)))
-   
+
((org-pos-in-match-range pos 6) ;; POS on "dmwy" repeater char.
 	(setq pos-match-group 6
   new (car (rassoc (+ nincrements (cdr (assoc (match-string 6 ts-string) idx))) idx
-   
+
((org-pos-in-match-range pos 5) ;; POS on X in "Xd" repeater.
 	(setq pos-match-group 5
   ;; Never drop below X=1.
   new (format "%d" (max 1 (+ nincrements (string-to-number (match-string 5 ts-string)))
-   
+
((org-pos-in-match-range pos 9) ;; POS on "dmwy" repeater in warning interval.
 	(setq pos-match-group 9
   new (car (rassoc (+ nincrements (cdr (assoc (match-string 9 ts-string) idx))) idx
-   
+
((org-pos-in-match-range pos 8) ;; POS on X in "Xd" in warning interval.
 	(setq pos-match-group 8
   ;; Never drop below X=0.
@@ -20254,6 +20257,146 @@ it has a `diary' type."
 		(org-format-timestamp timestamp fmt t))
 	  (org-format-timestamp timestamp fmt (eq boundary 'end)))
 
+;;; Yank media handler and DND
+(defun org-setup-yank-dnd-handlers ()
+  "Setup the `yank-media' and DND handlers for buffer."
+  (setq-local dnd-protocol-alist
+  (cons '("^file:///" . org--dnd-local-file-handler)
+dnd-protocol-alist))
+  (yank-media-handler "image/.*" #'org--image-yank-media-handler)
+  ;; Looks like different DEs go for different handler names,
+  ;; https://larsee.com/blog/2019/05/clipboard-files/.
+  (yank-media-handler "x/special-\\(?:gnome\|KDE\|mate\\)-files"
+  

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Fri, Sep 22, 2023 at 12:02 PM Juan Manuel Macías 
wrote:

> Zenny  writes:
>
> > It still shows the problem with
> > glyphs:
> >
> > Should look like in the attached
> > screenshots, in emacs orgmode
> > and rendered to pdf (from org to
> > docx using pandoc)
>
> Add this line to the bottom:
>
> #+LaTeX_Header:\defaultfontfeatures{Renderer=HarfBuzz}
>

Appended the above line, but the rendering became much worse, see Ganapati
and BiSht lines:

 Thanks.


-- 
Cheers,
/z

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Zenny  writes:

> It still shows the problem with
> glyphs:
>
> Should look like in the attached
> screenshots, in emacs orgmode
> and rendered to pdf (from org to
> docx using pandoc)

Add this line to the bottom:

#+LaTeX_Header:\defaultfontfeatures{Renderer=HarfBuzz}

Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom)

[Ihor Radchenko]

Leo Butler  writes:

>> What is the purpose of this `unwind-protect'?
>> In its current form, it does nothing because no UNWINDFORMS are
>> provided.
>
> I copied the forms from tests I had written for ob-octave, without
> thinking about why those tests were wrapped in an `unwind-protect'
> form. The attached patch removes them, otherwise it is identical to the
> previous patch.

Thanks! Now, may you also add etc/ORG-NEWS entry and update the WORG docs?

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

Re: [FR] Make notion of "modification time" configurable during publishing

[Ihor Radchenko]

Suhail Singh  writes:

>>   The new suggested feature is (optionally) using last git commit time
>>   instead of file modification time.
>
> The requested feature is for the notion of "modification time" to be
> configurable by the user. Even in the specific situation quoted above,
> different users may desire different alternative notions of
> "modification time". For instance,
>
> - the value of the DATE keyword
> - if using git as vc, the "git author date"
> - if using git as vc, the "git commit date"

I am a bit confused. What do you mean by "git author date" and "git
commit date"?

> It would help for the notion of "modification time" (currently
> hard-coded as file-attribute-modification-time ) to be configurable in
> the following functions:
>
> - org-publish-cache-mtime-of-src: this is used to decide whether or not
>   a particular file needs to be republished. I.e., the function at the
>   heart of the motivating situation discussed during the meetup.

I think that we should use an alternative approach. Both "git time" and
"fs time" are only an approximation. The true decision to re-publish an
article should be triggered by article text being modified. So, we may
better decide based on the file text hash, not the modification times.

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

Re: [PATCH] Add backslash to list of POST characters for text markup

[Ihor Radchenko]

"Tom Alexander"  writes:

> Backslash appears to be supported. To test I used the following test document:
> ```
> foo ~bar~\& baz
> ```

Thanks!
You are right.
Applied, onto master, with minor amendments to the commit message.
https://git.sr.ht/~bzg/worg/commit/ba6cda89

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

Re: Consecutive plain list items of different types

[Ihor Radchenko]

"Tom Alexander"  writes:

> The org-mode documentation[1] states for plain lists that:
>> List types are mutually exclusive at the same level of indentation, if both 
>> types are present consecutively then they parse as separate lists.
>
> first a minor nit-pick that "both" is probably not the correct word here 
> since there are 3 types of lists, not two (unordered, ordered, and 
> descriptive). I'd go with "multiple" instead IMO.

Fixed.
https://git.sr.ht/~bzg/worg/commit/c7445f84

> but more importantly, based on that description I would expect the following 
> test document to parse into three separate plain lists, but it parses as a 
> single plain list with 3 items:
>
> ```
> 1. foo
> - bar
> - lorem :: ipsum
> ```
>
> [1] https://orgmode.org/worg/org-syntax.html#Plain_Lists

AFAIK, the first item determines the list type in our parser.
Timothy, do you remember why you wrote about different list types being
parsed separately?

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

Re: Subscript with parenthesis

[Ihor Radchenko]

"Tom Alexander"  writes:

> Some additional things I'm noticing:
>
> - when using parenthesis, :use-brackets-p is nil, so they're not equivalent 
> to curly braces.

`org-element-subscript-parser' uses `org-match-substring-regexp', which
indeed allows foo_(...). This is not documented in org-syntax.org and in
the manual (12.3 Subscripts and Superscripts).

> - it does not support objects inside the parenthesis, just plain text, which 
> again means they're not equivalent to braces.

Not true. I tried

b^(*asd*) and bold inside superscript does get parsed.

> - it, however, seems to require that the parenthesis are balanced because 
> this test document does NOT contain a subscript:
> ```
> foo_(b(ar)
> ```
> which is closer to the curly braces requirement since that seems to be the 
> only part of the subscript/superscript documentation that mentions needing 
> balance.

Yup - the regexp used is the same with what we do for curly braces:

(defconst org-match-substring-regexp
  (concat
   "\\(\\S-\\)\\([_^]\\)\\("
   "\\(?:" (org-create-multibrace-regexp "{" "}" org-match-sexp-depth) "\\)"
   "\\|"
   "\\(?:" (org-create-multibrace-regexp "(" ")" org-match-sexp-depth) "\\)"
   "\\|"
   "\\(?:\\*\\|[+-]?[[:alnum:].,\\]*[[:alnum:]]\\)\\)")
  "The regular expression matching a sub- or superscript.")

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

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Zenny writes:

> Here it comes:
>
> | Original | Anglicized | Switch |
> |--++|
> | सत्य   | Satya  | Sathya |
> | सरस्वती | Saraswati  | Saraswathy |
> | गणपति | Ganapati   | Ganapathy  |
> | गोषाल  | goShal | Ghoshal|
> | गोष्ठ   | GoShTha| Ghosht |
> | मुम्बा   | Mumba  | Bombay |
> | घोष   | GhoSha | Ghosh  |
> | बिष्ट   | BiSht  | Bista  |
> | अंग   | Anga   | Banga  |
>
> Gosala Mankhya (घोषाला  मंख्य  in Sanskrit and ঘোষালা মঙ্গ্যায় in Bengali)

See screenshot. It's right?

https://i.imgur.com/OD5nl1Q.png

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Fri, Sep 22, 2023 at 10:54 AM Juan Manuel Macías 
wrote:

> Zenny writes:
>
> > 
> > 
> > 
> >
> > With this both languages (scripts) were rendered) but both renderings
> > has no correct glyphs (see screenshots)
>
> Could you please copy the text of your example here, so I can compile
> it?
>

Here it comes:

| Original | Anglicized | Switch |
|--++|
| सत्य   | Satya  | Sathya |
| सरस्वती | Saraswati  | Saraswathy |
| गणपति | Ganapati   | Ganapathy  |
| गोषाल  | goShal | Ghoshal|
| गोष्ठ   | GoShTha| Ghosht |
| मुम्बा   | Mumba  | Bombay |
| घोष   | GhoSha | Ghosh  |
| बिष्ट   | BiSht  | Bista  |
| अंग   | Anga   | Banga  |

Gosala Mankhya (घोषाला  मंख्य  in Sanskrit and ঘোষালা মঙ্গ্যায় in Bengali)

-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Zenny writes:

> 
> 
> 
>
> With this both languages (scripts) were rendered) but both renderings
> has no correct glyphs (see screenshots)

Could you please copy the text of your example here, so I can compile
it?

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Fri, Sep 22, 2023 at 10:49 AM Zenny  wrote:

> On Fri, Sep 22, 2023 at 10:41 AM Juan Manuel Macías <
> maciasch...@posteo.net> wrote:
>
>> Zenny writes:
>>
>> > Also the Bengali letters were omitted with:
>>
>> Sorry, this is the correct MWE:
>>
>> #+LaTeX_Header: \usepackage[english]{babel}
>> #+LaTeX_Header: \usepackage{fontspec}
>> #+LaTeX_Header: \newfontscript{Devanagari}{deva}
>> #+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
>> #+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-bengali}
>> #+LaTeX_Header: \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}
>> #+LaTeX_Header: \babelfont[sanskrit-bengali]{rm}{Noto Sans Bengali}
>>
>> 
>> 
>> 
>>
>
> With this both languages (scripts) were rendered) but both renderings has
> no correct glyphs (see screenshots)
> Thanks!
>

Actually, the former should look like the latter, for a comparison.


> --
> Cheers,
> /z
>
> -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
> CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
> contents by anyone other than the intended recipient is unauthorized as it
> contains privileged and confidential information, and is subject to legal
> privilege. Please do not re/distribute it.  If you are not the intended
> recipient (or responsible for delivery of the message to such person), you
> may not use, copy, distribute or deliver the email and part of its contents
> to anyone this message (or any part of its contents or take any action in
> connection to it. In such case, you should destroy this message, and notify
> the sender immediately. If you have received this email in error, please
> notify the sender or your sysadmin immediately by e-mail or telephone, and
> delete the e-mail from any computer. If you or your employer does not
> consent to internet e-mail messages of this kind, please notify the sender
> immediately. All reasonable precautions have been taken to ensure no
> viruses are present in this e-mail and attachments included. As the sender
> cannot accept responsibility for any loss or damage arising from the use of
> this e-mail or attachments it is recommended that you are responsible to
> follow your virus checking procedures prior to use. The views, opinions,
> conclusions and other informations expressed in this electronic mail are
> not given or endorsed by any company including the network providers unless
> otherwise indicated by an authorized representative independent of this
> message.
> -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
>
>

-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Fri, Sep 22, 2023 at 10:41 AM Juan Manuel Macías 
wrote:

> Zenny writes:
>
> > Also the Bengali letters were omitted with:
>
> Sorry, this is the correct MWE:
>
> #+LaTeX_Header: \usepackage[english]{babel}
> #+LaTeX_Header: \usepackage{fontspec}
> #+LaTeX_Header: \newfontscript{Devanagari}{deva}
> #+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
> #+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-bengali}
> #+LaTeX_Header: \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}
> #+LaTeX_Header: \babelfont[sanskrit-bengali]{rm}{Noto Sans Bengali}
>
> 
> 
> 
>

With this both languages (scripts) were rendered) but both renderings has
no correct glyphs (see screenshots)
Thanks!
-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

Re: How to hide square brackets around [[url][links]]?

[Ihor Radchenko]

William Denton  writes:

> Sometimes when searching with Swiper, the display of (some) links is changed 
> and 
> instead of seeing the anchor text formatted as a link I see the full raw 
> [[URL][anchor text]].
>
> How can I make this go back to showing just the anchor text?  I've tried 
> toggling visible-mode and using org-toggle-link-display but neither work, so 
> I 
> have to C-x C-v and reload the file.  Should these commands be reformatting 
> all 
> the links in the buffer, and the fact they don't work is a sign of the bug?

For isearch compatibility, Org has to convert back-and-forth between
overlays and text properties. If `org-toggle-link-display' does not
work, we most likely have some isearch overlays leftover and not
converted back.

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

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Zenny writes:

> Also the Bengali letters were omitted with:

Sorry, this is the correct MWE:

#+LaTeX_Header: \usepackage[english]{babel}
#+LaTeX_Header: \usepackage{fontspec}
#+LaTeX_Header: \newfontscript{Devanagari}{deva}
#+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
#+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-bengali}
#+LaTeX_Header: \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}
#+LaTeX_Header: \babelfont[sanskrit-bengali]{rm}{Noto Sans Bengali}

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Fri, Sep 22, 2023 at 10:18 AM Juan Manuel Macías 
wrote:

> Zenny writes:
>
> > Thanks, this was extremely helpful. The pdf is produced, but the
> > Devanagari glyphs were not respected. See screenshot.
>
> Could you please create this MWE, and execute the same process?
>
> #+LaTeX_Header: \usepackage[english]{babel}
> #+LaTeX_Header: \usepackage{fontspec}
> #+LaTeX_Header: \newfontscript{Devanagari}{deva}
> #+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
> #+LaTeX_Header: \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}
>
> 
>
> 
>

Thanks!

With above MWE, the org can directly be exported to pdf, but

1. Glyphs in Devanagari are not respected as earlier
2. Bengali is completely skipped.



-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Zenny writes:

> Thanks, this was extremely helpful. The pdf is produced, but the
> Devanagari glyphs were not respected. See screenshot.

Could you please create this MWE, and execute the same process?

#+LaTeX_Header: \usepackage[english]{babel}
#+LaTeX_Header: \usepackage{fontspec}
#+LaTeX_Header: \newfontscript{Devanagari}{deva}
#+LaTeX_Header: \babelprovide[onchar=ids fonts]{sanskrit-devanagari}
#+LaTeX_Header: \babelfont[sanskrit-devanagari]{rm}{Noto Sans Devanagari}

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Fri, Sep 22, 2023 at 10:07 AM Zenny  wrote:

>
> On Fri, Sep 22, 2023 at 10:00 AM Juan Manuel Macías <
> maciasch...@posteo.net> wrote:
>
>> Zenny writes:
>>
>> > Exactly done as you advised, but no pdf is produced even after waiting
>> > for ~10minutes (attached screenshot)
>>
>> Let's try the following:
>>
>> 1. Export your document to a 'your-document.tex' file: C-c C-e l l
>>
>> 2. Open a terminal in your directory and run:
>>
>> latexmk -f -pdf -lualatex -interaction=nonstopmode your-document.tex
>>
>
> Thanks, this was extremely helpful. The pdf is produced, but the
> Devanagari glyphs were not respected. See screenshot.
>
>>
>> (a pdf would have to be created after compilation. If there are any
>> errors, please copy your-document.log here).
>>
>
> Also the Bengali letters were omitted with:
>
> Latexmk: Summary of warnings from last run of *latex:
>>   =Latex reported missing or unavailable character(s).
>> =See log file for details.
>> Latexmk: List of undefined refs and citations:
>>   Missing character: There is no ঘ (U+0998) in font
>> [lmroman10-regular]:+tlig;!Missing character: There is no ো (U+09CB) in
>> font [lmroman10-regular]:+tlig;!Missing character: There is no ষ (U+09B7)
>> in font [lmroman10-regular]:+tlig;!Missing character: There is no া
>> (U+09BE) in font [lmroman10-regular]:+tlig;!Missing character: There is no
>> ল (U+09B2) in font [lmroman10-regular]:+tlig;!Missing character: There is
>> no া (U+09BE) in font [lmroman10-regular]:+tlig;!Missing character: There
>> is no ম (U+09AE) in font [lmroman10-regular]:+tlig;!Missing character:
>> There is no ঙ (U+0999) in font [lmroman10-regular]:+tlig;!Missing
>> character: There is no  (U+09CD) in font [lmroman10-regular]:+tlig;!Missing
>> character: There is no গ (U+0997) in font
>> [lmroman10-regular]:+tlig;!Missing character: There is no  (U+09CD) in font
>> [lmroman10-regular]:+tlig;!Missing character: There is no য (U+09AF) in
>> font [lmroman10-regular]:+tlig;!Missing character: There is no া (U+09BE)
>> in font [lmroman10-regular]:+tlig;!Missing character: There is no য
>> (U+09AF) in font [lmroman10-regular]:+tlig;!Missing character: There is no
>>  (U+09BC) in font [lmroman10-regular]:+tlig;!] [2] [3
>>   Missing character: There is no ঘ (U+0998) in font
>> [lmroman10-regular]:+tlig;!Missing character: There is no ো (U+09CB) in
>> font [lmroman10-regular]:+tlig;!Missing character: There is no ষ (U+09B7)
>> in font [lmroman10-regular]:+tlig;!Missing character: There is no প
>> (U+09AA) in font [lmroman10-regular]:+tlig;!Missing character: There is no
>> ত (U+09A4) in font [lmroman10-regular]:+tlig;!Missing character: There is
>> no  (U+09C1) in font [lmroman10-regular]:+tlig;!Missing character: There is
>> no আ (U+0986) in font [lmroman10-regular]:+tlig;!Missing character: There
>> is no ঘ (U+0998) in font [lmroman10-regular]:+tlig;!Missing character:
>> There is no ো (U+09CB) in font [lmroman10-regular]:+tlig;!Missing
>> character: There is no ষ (U+09B7) in font
>> [lmroman10-regular]:+tlig;!Missing character: There is no প (U+09AA) in
>> font [lmroman10-regular]:+tlig;!Missing character: There is no ত (U+09A4)
>> in font [lmroman10-regular]:+tlig;!Missing character: There is no  (U+09C1)
>> in font [lmroman10-regular]:+tlig;!Missing character: There is no আ
>> (U+0986) in font [lmroman10-regular]:+tlig;!] [4] [5]
>>
>
The bengali is already installed by tlmgr:

# tlmgr install bengali
> tlmgr: package repository
> https://ftpmirror1.infania.net/mirror/CTAN/systems/texlive/tlnet
> (verified)
> tlmgr install: package already present: bengali
>


>
>
>
>
>> Best regards,
>>
>> Juan Manuel
>>
>>
>
> --
> Cheers,
> /z
>
> -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
> CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
> contents by anyone other than the intended recipient is unauthorized as it
> contains privileged and confidential information, and is subject to legal
> privilege. Please do not re/distribute it.  If you are not the intended
> recipient (or responsible for delivery of the message to such person), you
> may not use, copy, distribute or deliver the email and part of its contents
> to anyone this message (or any part of its contents or take any action in
> connection to it. In such case, you should destroy this message, and notify
> the sender immediately. If you have received this email in error, please
> notify the sender or your sysadmin immediately by e-mail or telephone, and
> delete the e-mail from any computer. If you or your employer does not
> consent to internet e-mail messages of this kind, please notify the sender
> immediately. All reasonable precautions have been taken to ensure no
> viruses are present in this e-mail and attachments included. As the sender
> cannot accept responsibility for any loss or damage arising from the use of
> this e-mail or attachments it is recommended that you are responsible to
> follow your virus checking 

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Fri, Sep 22, 2023 at 10:00 AM Juan Manuel Macías 
wrote:

> Zenny writes:
>
> > Exactly done as you advised, but no pdf is produced even after waiting
> > for ~10minutes (attached screenshot)
>
> Let's try the following:
>
> 1. Export your document to a 'your-document.tex' file: C-c C-e l l
>
> 2. Open a terminal in your directory and run:
>
> latexmk -f -pdf -lualatex -interaction=nonstopmode your-document.tex
>

Thanks, this was extremely helpful. The pdf is produced, but the Devanagari
glyphs were not respected. See screenshot.

>
> (a pdf would have to be created after compilation. If there are any
> errors, please copy your-document.log here).
>

Also the Bengali letters were omitted with:

Latexmk: Summary of warnings from last run of *latex:
>   =Latex reported missing or unavailable character(s).
> =See log file for details.
> Latexmk: List of undefined refs and citations:
>   Missing character: There is no ঘ (U+0998) in font
> [lmroman10-regular]:+tlig;!Missing character: There is no ো (U+09CB) in
> font [lmroman10-regular]:+tlig;!Missing character: There is no ষ (U+09B7)
> in font [lmroman10-regular]:+tlig;!Missing character: There is no া
> (U+09BE) in font [lmroman10-regular]:+tlig;!Missing character: There is no
> ল (U+09B2) in font [lmroman10-regular]:+tlig;!Missing character: There is
> no া (U+09BE) in font [lmroman10-regular]:+tlig;!Missing character: There
> is no ম (U+09AE) in font [lmroman10-regular]:+tlig;!Missing character:
> There is no ঙ (U+0999) in font [lmroman10-regular]:+tlig;!Missing
> character: There is no  (U+09CD) in font [lmroman10-regular]:+tlig;!Missing
> character: There is no গ (U+0997) in font
> [lmroman10-regular]:+tlig;!Missing character: There is no  (U+09CD) in font
> [lmroman10-regular]:+tlig;!Missing character: There is no য (U+09AF) in
> font [lmroman10-regular]:+tlig;!Missing character: There is no া (U+09BE)
> in font [lmroman10-regular]:+tlig;!Missing character: There is no য
> (U+09AF) in font [lmroman10-regular]:+tlig;!Missing character: There is no
>  (U+09BC) in font [lmroman10-regular]:+tlig;!] [2] [3
>   Missing character: There is no ঘ (U+0998) in font
> [lmroman10-regular]:+tlig;!Missing character: There is no ো (U+09CB) in
> font [lmroman10-regular]:+tlig;!Missing character: There is no ষ (U+09B7)
> in font [lmroman10-regular]:+tlig;!Missing character: There is no প
> (U+09AA) in font [lmroman10-regular]:+tlig;!Missing character: There is no
> ত (U+09A4) in font [lmroman10-regular]:+tlig;!Missing character: There is
> no  (U+09C1) in font [lmroman10-regular]:+tlig;!Missing character: There is
> no আ (U+0986) in font [lmroman10-regular]:+tlig;!Missing character: There
> is no ঘ (U+0998) in font [lmroman10-regular]:+tlig;!Missing character:
> There is no ো (U+09CB) in font [lmroman10-regular]:+tlig;!Missing
> character: There is no ষ (U+09B7) in font
> [lmroman10-regular]:+tlig;!Missing character: There is no প (U+09AA) in
> font [lmroman10-regular]:+tlig;!Missing character: There is no ত (U+09A4)
> in font [lmroman10-regular]:+tlig;!Missing character: There is no  (U+09C1)
> in font [lmroman10-regular]:+tlig;!Missing character: There is no আ
> (U+0986) in font [lmroman10-regular]:+tlig;!] [4] [5]
>




> Best regards,
>
> Juan Manuel
>
>

-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Juan Manuel Macías]

Zenny writes:

> Exactly done as you advised, but no pdf is produced even after waiting
> for ~10minutes (attached screenshot)

Let's try the following:

1. Export your document to a 'your-document.tex' file: C-c C-e l l

2. Open a terminal in your directory and run:

latexmk -f -pdf -lualatex -interaction=nonstopmode your-document.tex

(a pdf would have to be created after compilation. If there are any
errors, please copy your-document.log here).

Best regards,

Juan Manuel 

Re: Bug with "BEAMER_OPT: shrink" and links

[Fraga, Eric]

Hi Guillaume,

On Thursday, 21 Sep 2023 at 19:41, Guillaume MULLER wrote:
> Here is a small test.org file that uses shrink to reduce the size of the 
> slides:

[...]

> If you run 'org-beamer-export-to-pdf' on this file, you'll get a PDF
> where the clickable area for the link is most of the time way out of
> the text for the link...

Confirmed: same issue for me.

However, having looked at the LaTeX generated, I do not believe this is
a bug in org; rather, it is likely an issue with beamer so you may need
to bring this up on one of the LaTeX lists/groups.

-- 
: Eric S Fraga, with org release_9.6.7-661-g34ee6f in Emacs 30.0.50

Re: Sanskrit/Devanagari fonts not exported to org-pdf output

[Zenny]

On Thu, Sep 21, 2023 at 11:19 PM Juan Manuel Macías 
wrote:

> Zenny writes:
>
> > I also tried with:
> >
> > (setq org-latex-pdf-process
> >   (if (executable-find "latexmk")
> >   '("latexmk -interaction nonstopmode -output-directory %o
> > %f")
> >  "bibtex %b"
> >  '("%latex -interaction nonstopmode -output-directory %o %f"
> >   "%latex -interaction nonstopmode -output-directory %o %f"
> >   "%latex -interaction nonstopmode -output-directory %o %f"))
>
> I think the expression is bad formed; In addition, latexmk is already
> responsible for executing bibtex or biber and other processes that
> require more than one compilation. The right thing would be:
>
> (setq org-latex-pdf-process (if (executable-find "latexmk")
> '("latexmk -f -pdf -%latex
> -interaction=nonstopmode -output-directory=%o %f")
>   '("%latex -interaction nonstopmode
> -output-directory %o %f"
> "%latex -interaction nonstopmode
> -output-directory %o %f"
> "%latex -interaction nonstopmode
> -output-directory %o %f")))
>
> (or just remove the customization of that variable from your init).
>
> And then put in your document:
>
> #+LATEX_COMPILER: lualatex (or pdflatex or xelatex)
>

Exactly done as you advised, but no pdf is produced even after waiting for
~10minutes (attached screenshot)


>
> This keyword modifies the value of org-latex-compiler in the document.
> If you are going to use lualatex more often, you can put in your init:
>
> (setq org-latex-compiler "lualatex")
>

Thanks for your input.

>
> Best regards,
>
> Juan Manuel
>
> --
> Juan Manuel Macías
>
> https://juanmanuelmacias.com
>
> https://lunotipia.juanmanuelmacias.com
>
> https://gnutas.juanmanuelmacias.com
>
>

-- 
Cheers,
/z

-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it.  If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.