* Re: Choosing a LaTeX Compiler (my predilection for LuaTeX)
@ 2021-04-07 17:26 9% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-04-07 17:26 UTC (permalink / raw)
To: physiculus; +Cc: orgmode
Hello,
physiculus writes:
> Hello again,
>
> thanks for the snippet, but unfortunately it doesn't work :-(
>
> Now it doesn't stop with error, it happens nothing.
> here is my config.
>
> Variable:
> org-preview-latex-default-process is a variable defined in ‘org.el’.
> Its value is ‘luasvg’
> Original value was ‘dvipng’
It's weird, it should work :-( ... I assume you have dvisvgm installed
in your TeX Live installation, is that right? (You can excute something
like 'dvisvgm --help' in your terminal)
What is your SO?
Anyway, you can try the imagemagick option:
(setq luamagick
'(luamagick
:programs ("lualatex" "convert")
:description "pdf > png"
:message "you need to install lualatex and imagemagick."
:use-xcolor t
:image-input-type "pdf"
:image-output-type "png"
:image-size-adjust (1.0 . 1.0)
:latex-compiler ("lualatex -interaction nonstopmode -output-directory %o %f")
:image-converter ("convert -density %D -trim -antialias %f -quality 100 %O")))
(add-to-list 'org-preview-latex-process-alist luamagick)
(setq org-preview-latex-default-process 'luamagick)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: org-mode export to (latex) PDF
@ 2021-07-15 19:40 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-07-15 19:40 UTC (permalink / raw)
To: Maxim Nikulin; +Cc: orgmode
Maxim Nikulin writes:
> In CSS it is possible to specify a list of fonts and a glyph is taken
> from the first font where it is present. Despite particular fonts have
> limited coverage, I see wide range of Unicode characters on web pages,
> that is why I am almost sure that system font libraries combine fonts.
In LuaTeX you can associate a font family to a range or a group of
characters. In a book I typesetted some time ago I used the Cardo font
to represent the characters for Private Use Area.
\newfontfamily\cardo{Cardo} % a fontspec command
\def\puatext#1{{\cardo #1}}
\begin{luacode*}
function my_pua (text)
texto = unicode.utf8.gsub ( text, "([\u{e000}-\u{f8ff}])", "\\puatext{%1}" )
return text
end
\end{luacode*}
\newcommand\activatepuatext{\directlua{luatexbase.add_to_callback
( "process_input_buffer" , my_pua , "my_pua" )}}
\AtBeginDocument{\activatepuatext}
(I add a simple substitution to the callback `process_imput_buffer'
[see: http://wiki.luatex.org/index.php/Callbacks], but these kinds of
overrides can also be do from Org using a custom filter).
Regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: [tip for EXWM users] An alternative method for isolate trees
@ 2021-03-01 16:42 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-03-01 16:42 UTC (permalink / raw)
To: Julian M. Burgos; +Cc: orgmode
Hi Julian,
"Julian M. Burgos" <julian.burgos@hafogvatn.is> writes:
> This does not seem to be a limitation from emacs, as it is possible to
> open multiple indirect buffers from a base buffer, using for example
> clone-indirect-buffer. So it should be possible to make a function
> combining "clone-indirect-buffer" and "org-narrow-to-subtree" perhaps?
> I am thinking so this option is available not only to EXWM users.
I think that combining clone-indirect-buffer and org-narrow-to-subtree
would work well. Another way to isolate several trees at once is by
using the excellent package org-sidebar
(https://github.com/alphapapa/org-sidebar). In fact, I borrowed from
this package the idea of renaming the new buffers with the string :: (if
I open helm and start typing ::, it shows me the list of isolated trees,
so it's very useful to have a dedicated string). Although my method for
isolating each tree is more pedestrian :-). And it only makes sense in
EXWM...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: Syntax Proposal: Multi-line Table Cells/Text Wrapping
@ 2021-03-19 15:07 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-03-19 15:07 UTC (permalink / raw)
To: tomas; +Cc: orgmode
tomas@tuxteam.de writes:
> [...] My point was that it probably makes sense to separate concerns
> here.
Yes, that separation is essential. I agree.
> That's right. OTOH, people will try to stretch it in every conceivable
> direction. That's in a way Org's biggest strength (and at the same time
> its biggest weakness :)
Great truth! I always try to take things to the extreme :-D, and I
continue thinking that Org is (among many other things) an excellent
'interface' for LaTeX (maybe the best). But I have to admit that a table
with a lot of complexity is a special case when maybe you have to write
LaTeX code, and get lost between all those & and backslashes, at least
if the goal is the typographic refinement. The greatest power of Org
resides in his lightness and in its chameleon versatility, but his worst
temptation may be to become in a (poor) LaTeX 'translation'.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: Smart quotes not working correctly with single quotes
@ 2021-05-28 10:10 9% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-05-28 10:10 UTC (permalink / raw)
To: Andreas Gösele; +Cc: orgmode
Hi Andreas,
I don't know if this is a bug, but I would say that in principle it's
the expected result. Single quotes are understood here as inner quotes
or second-level quotation marks, therefore they are only activated
nested in text with first level quotes: " ... '...' ... "
lorem "ipsum 'dolor sit' amet"
For LaTeX output, however, the csquotes package is a more powerful
option to control the correct quotation marks for each language. For
example:
#+LaTeX_Header: \usepackage[german,english]{babel}
#+LaTeX_Header: \usepackage[babel=true,autostyle=true,german=quotes]{csquotes}
#+LaTeX_Header: \MakeOuterQuote{"}
#+LaTeX_Header: \MakeInnerQuote{´}
#+LaTeX: \selectlanguage{german}\EnableQuotes
It's a ´test´. "Please".
lorem "ipsum ´dolor´ sit" amet
Best regards,
Juan Manuel
Andreas Gösele writes:
> Hi,
>
> even using "smart quotes", single quotes are not correctly exported into
> html, odt or latex.
>
> I have as document:
>
> | #+LANGUAGE: de
> | #+OPTIONS: ':t
> | #+OPTIONS: toc:nil
> | It's a 'test'. "Please".
>
> If I export it to html I get:
>
> | It’s a ’test’. „Please“.
>
> I should get:
>
> | It’s a ‚test‘. „Please“.
>
> If I export to latex I get:
>
> | It's a 'test'. "`Please"'.
>
> I should get:
>
> | It's a \glq{}test\grq{}. "`Please"'.
>
> If I export to odt I get:
>
> | It’s a ’test’. „Please“.
>
> I should get:
>
> | It’s a ‚test‘. „Please“.
>
> (The odt example outputs use utf8, I hope it gets transmitted.)
>
> So in all three cases apostrophes and double quotes are correctly
> exported, but not single quotes. Similar problem if I use "#+LANGUAGE:
> en".
>
> I have org-mode 9.3 with emacs 27.1.
>
> What could I do to get single quotes to be exported correctly?
>
> Thanks a lot!
>
> Andreas
>
^ permalink raw reply [relevance 9%]
* Experimental public branch for inline special blocks
@ 2024-03-01 20:34 9% Juan Manuel Macías
0 siblings, 2 replies; 200+ results
From: Juan Manuel Macías @ 2024-03-01 20:34 UTC (permalink / raw)
To: orgmode
Hi,
Finally, I have made public on GitLab my experimental branch for the new
(possible) inline-special-block element:
<https://gitlab.com/maciaschain/org-mode.git>
The code incorporates fixes and modifications and I have also added some
ideas from Maxim Nikulin. The LaTeX and HTML backends are complete,
although of course it can still be perfected. Recapitulating the
necessary information:
The new element can be nested and supports other elements such as links,
macros, emphasis marks, etc.
The basic syntax:
┌────
│ &foo{lorem ipsum dolor}
└────
produces in LaTeX:
┌────
│ \foo{lorem ipsum dolor}
└────
and in HTML:
┌────
│ <span class="foo">lorem ipsum dolor</span>
└────
There is also an anonymous variant:
┌────
│ &_{lorem ipsum dolor}
└────
Optional attributes in square brackets are supported. There are a series
of 'universal' attributes, common to each backend. At the moment:
`:lang', `:color' and `:smallcaps'. Example:
┌────
│ &foo[:color red :smallcaps t :lang it]{lorem ipsum dolor}
└────
Specific to the LaTeX backend we have the `:prelatex' and `:postlatex'
attributes (which introduce arbitrary code before and after the content)
and `:latex-command', which overrides the exported command.
`:latex-command nocommand' does not export a command flag. Examples:
┌────
│ &foo[:prelatex [bar] :postlatex {baz} :lang it :latex-command blah]{lorem ipsum dolor}
└────
==>
┌────
│ \foreignlanguage{italian}{\blah[bar]{lorem ipsum dolor}{baz}}
└────
┌────
│ &_[:prelatex \foo{bar} :color red]{lorem ipsum dolor}
└────
==>
┌────
│ {\color{red}\foo{bar}lorem ipsum dolor}
└────
Likewise, for HTML we have the `:html-tag' and `:html-class' attributes
(which override the tags and the class name) and another one, more
generic, `:html', which introduces arbitrary code, such as
`style="..."'.
We can group lists of attributes as aliases. The syntax waould be:
┌────
│ &alias!{text}
└────
and we can also combine aliases with more single attributes:
┌────
│ &alias![more-attributes]{text}
└────
An example: let's imagine that we want a specific block for short quotes
in Latin and italics (it is normative in some typographical traditions
that quotes in classical Latin are put in italics instead of quotation
marks):
┌────
│ #+options: inline-special-block-aliases:(("latin" :lang "la" :latex-command "textit" :html-tag "em"))
│
│ Caesar's famous quote: &latin!{Alea iacta est}
│
│ Caesar's famous quote: &latin![:smallcaps t :color blue]{Alea iacta est}
└────
==> LaTeX:
┌────
│ Caesar's famous quote: \foreignlanguage{latin}{\textit{Alea iacta est}}
│
│ Caesar's famous quote: {\scshape{}\color{blue}\foreignlanguage{latin}{\textit{Alea iacta est}}}
└────
== HTML:
┌────
│ Caesar's famous quote: <em lang="la" class="latin">Alea iacta est</em>
│
│ Caesar's famous quote: <em style="color:blue;font-variant:small-caps;" lang="la" class="latin">Alea iacta est</em>
└────
Best regards,
Juan Manuel
--
Juan Manuel Macías -- Composición tipográfica, tratamiento de datos, diseño editorial y ortotipografía
^ permalink raw reply [relevance 9%]
* Re: [Patch] to correctly sort the items with emphasis marks in a list
@ 2021-04-10 0:01 9% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-04-10 0:01 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: orgmode
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
Hellow Nicolas:
Nicolas Goaziou writes:
> Thank you.
>
> Could you apply the same fix to the `org-verbatim-re' match above, and
> provide an appropriate commit message?
Done! I've attached the corrected patch. Sorry for the flaws in me
previous patch: I'm a bit of a novice at submitting patches...
Best regards,
Juan Manuel
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Remove-spurious-spaces-in-org-sort-remove-invisible.patch --]
[-- Type: text/x-patch, Size: 1172 bytes --]
From ab104bb079e3e32d622a6ff53824b5047dc25c14 Mon Sep 17 00:00:00 2001
From: Juan Manuel Macias <maciaschain@posteo.net>
Date: Fri, 2 Apr 2021 21:20:17 +0200
Subject: [PATCH] Remove spurious spaces in org-sort-remove-invisible
Some spurious spaces in org-sort-remove-invisible is causing
org-sort-list not to sort correctly (alphabetically) the items that
contain emphasis marks in a plain list
---
lisp/org.el | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lisp/org.el b/lisp/org.el
index 675a614e2..74e2afac9 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -8113,9 +8113,9 @@ Optional argument WITH-CASE means sort case-sensitively."
"Remove invisible part of links and emphasis markers from string S."
(remove-text-properties 0 (length s) org-rm-props s)
(replace-regexp-in-string
- org-verbatim-re (lambda (m) (format "%s " (match-string 4 m)))
+ org-verbatim-re (lambda (m) (format "%s" (match-string 4 m)))
(replace-regexp-in-string
- org-emph-re (lambda (m) (format " %s " (match-string 4 m)))
+ org-emph-re (lambda (m) (format "%s" (match-string 4 m)))
(org-link-display-format s)
t t) t t))
--
2.26.0
^ permalink raw reply related [relevance 9%]
* Re: how to export an org file, to 2 different locations (in to different formats)
@ 2022-05-27 18:42 9% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2022-05-27 18:42 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Hi Uwe,
Uwe Brauer writes:
> Hi
>
> Currently I use
> #+EXPORT_FILE_NAME: /home/oub/Desktop/some-stuff.html
>
> To export my org file in html format to that location.
>
> But I would also like to export it as a latex file to a different
> location, without modifying the above line, or to be more precise to add
> a different location, like
>
> 1. if export to latex use that folder
>
> 2. If export to html use this folder
>
> Anybody know about such a functionality?
>
> Thanks and regards
>
> Uwe Brauer
One (pedestrian) way to achieve it, with this function:
(defun my-org/export-to-path (backend export-path extension)
(org-element-map (org-element-parse-buffer) 'keyword
(lambda (k)
(when (string= (org-element-property :key k) "EXPORT_FILE_NAME")
(let ((value (org-element-property :value k)))
(org-export-to-file backend
(format
"%s%s.%s"
export-path
value extension)))))))
And then you could evaluate it inside a block in your document, with the
chosen arguments. For example:
#+EXPORT_FILE_NAME: myfile
#+begin_src emacs-lisp :exports none :eval never-export :results silent
(my-org/export-to-path 'html "~/Desktop/" "html")
#+end_src
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: no inline images anymore after reinstall
@ 2021-06-16 12:51 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-16 12:51 UTC (permalink / raw)
To: Prof. Dr. Johanna May; +Cc: orgmode
Hi Johanna,
I don't have much knowledge of Python, but I have done this, in case it
helps you locate the problem:
- I have tried to evaluate your block (previously I have installed in my
Arch system python-matplotlib). Output:
#+RESULTS: fig-zeitverlaufspgendrehstrom
[[file:]]
but
- I have noticed that if you comment on these two lines:
# plt.rcParams.update({'font.size':fontsize})
# rcParams.update({'figure.autolayout': True})
output:
#+RESULTS: fig-zeitverlaufspgendrehstrom
[[file:/tmp/babel-yXFqLG/figurepLRhLV.png]]
(Python console was returning these two errors before commenting
the lines:
NameError: name 'fontsize' is not defined
NameError: name 'rcParams' is not defined)
Best regards,
Juan Manuel
Prof. Dr. Johanna May writes:
> Hi guys,
>
> I've been trying on the web and in "known as good" config files to solve
> this but cannot seem to find the solution:
>
> After reinstalling linux (openSuse leap 15.3) and finding out that
> unfortunately the distro is too new, so 27.1 does not yet get offered
> and switching back to 25.3 most of the stuff that I need works again.
>
> Except for including python output diagrams in org-babel. I put the
> diagram code at the very bottom since it takes up some space. At the very end
> you also see the output: it is not a file, it is just a link called
> [[file:]]. That cannot be right and then, of course, there are no inline
> images displayed and not exported either. It is remarkable though, that
> latex gets the link to the file, but just does not seem to show it
> right. This might point to a latex problem, but the inline images aren't
> shown in org-babel. Therefore I'm trying to find a solution here.
>
> In my dotemacs I included what I thought relevant to get it working, but
> it doesn't (below).
>
> I would be very glad about a hint where to look for a solution. Maybe
> some package-install (but which). Or some other configuration ... Or
> maybe I'm still lacking an important distro package that just does not
> get output on any error buffer?
>
> Thank you very much, any help is appreciated
>
> Johanna May
>
> --- some of my dotemacs lines ---
> ;; === org-babel - Code einbinden ===
> ;; ### Darstellung ###
> (setq org-startup-with-inline-images t)
> (setq org-confirm-babel-evaluate nil)
> (setq org-src-fontify-natively t)
> (setq org-src-tab-acts-natively t)
> (setq org-hide-emphasis-markers t)
>
> ;; ### Statistik mit R ESS ###
> (require 'ess-site)
>
> ;; ### org-babel Sprachen ###
> (require 'ob-python)
> (setq org-babel-python-command "python3")
> ;;(setq python-shell-interpreter "python3")
> (org-babel-do-load-languages
> 'org-babel-load-languages
> '((emacs-lisp . t)
> (python . t)
> (ipython . t)
> (shell . t)
> (js . t)
> (latex . t)
> (org . t)
> (octave . t)
> (R . t)
> (plantuml . t)
> (dot . t)
> (gnuplot . t)
> (ruby . t)
> (screen . nil)
> (ledger . t)
> (C . t)
> (sql . t)
> (ditaa . t)))
>
> ;; ### Einrückungen beachten (z. B. python) ###
> (setq org-edit-src-content-indentation 0)
> (setq org-src-tab-acts-natively t)
> (setq org-src-preserve-indentation t)
>
> ;; ### python-Coding ###
> (require 'epc)
> (require 'company)
> (add-hook 'after-init-hook 'global-company-mode)
> (global-font-lock-mode t)
> (setq font-lock-maximum-decoration t)
> (setq-default indent-tabs-mode nil) ;; nicht Tabs sondern 4 Leerzeichen
> (setq default-tab-width 4)
> (add-hook 'python-mode-hook 'anaconda-mode)
> (add-hook 'python-mode-hook 'eldoc-mode)
> (eval-after-load "company"
> '(progn
> (add-to-list 'company-backends 'company-anaconda)))
> (add-hook 'python-mode-hook 'anaconda-mode)
>
> ;; ### Bilder aus python inline anzeigen ###
> (add-hook 'org-babel-after-execute-hook 'org-display-inline-images 'append)
> (add-hook 'org-mode-hook 'org-display-inline-images)
> --- snip ---
>
>
> ---diagram code in org---
>
> #+name: fig-zeitverlaufspgendrehstrom
> #+begin_src python :results file :session :var matplot_lib_filename=(org-babel-temp-file "figure" ".png"),fontsize=fs :exports results
>
> import matplotlib.pyplot as plt
> plt.style.use('classic')
> import numpy as np
> from matplotlib.ticker import FuncFormatter, MultipleLocator
> plt.style.use('classic')
>
> plt.rcParams.update({'font.size':fontsize})
> rcParams.update({'figure.autolayout': True})
>
> fig=plt.figure(figsize=(6,3))
>
> x=np.linspace(0,5*np.pi,1000)
> udach=230*np.sqrt(2)
> phi1=0
> phi2=-np.pi*2/3
> phi3=-np.pi*4/3
> u1=udach*np.cos(x+phi1)
> u2=udach*np.cos(x+phi2)
> u3=udach*np.cos(x+phi3)
>
> plt.plot(x,u1,label='$u_1(t)$')
> plt.plot(x,u2,label='$u_2(t)$')
> plt.plot(x,u3,label='$u_3(t)$')
> plt.xlabel('$t$')
> plt.ylabel('$u$')
> plt.xticks([])
> plt.yticks([])
> plt.legend(fontsize='small',bbox_to_anchor=(0,1.02,1.02,0),loc=3,ncol=3,mode="expand",borderaxespad=0.)
> plt.grid(True)
> plt.axhline(0,color='black',lw=1)
>
> #plt.tight_layout()
> plt.savefig(matplot_lib_filename,bbox_inches='tight')
> matplot_lib_filename
> #+end_src
>
> #+CAPTION: Zeitverlauf symmetrischer Spannungen
> #+LABEL: fig-zeitverlaufspgendrehstrom
>
> #+ATTR_LATEX: :width \textwidth :height \textheight :options angle=0,keepaspectratio :float nil
>
> #+RESULTS: fig-zeitverlaufspgendrehstrom
> [[file:]]
>
> ---snip ---
>
^ permalink raw reply [relevance 9%]
* Re: Smart quotes for Greek (questions for a possible patch)
@ 2021-08-31 11:11 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-08-31 11:11 UTC (permalink / raw)
To: Protesilaos Stavrou, mvar; +Cc: orgmode
Hello Protesilaos and Michalis,
Thank you very much, Protesilaos, for the valuable information. It can
be confirmed, then, that the quotation marks rules for current Greek are
identical to the rules for Spanish, so it will be enough to copy the
existing configuration for Spanish in `org-export-smart-quotes-alist'.
It seems that the character U+201F as the first second level quotes
(instead of U+201C), which Yannis Haralambous comments in the article
cited in my first message, although historically attested, has been
abandoned...
Soon I will propose here a patch to support small quotes to
Greek.
Best regards,
Juan Manuel
Protesilaos Stavrou writes:
> Hello Michalis, Juan Manuel,
>
> [ I had no access to a computer and could not get to you sooner. Expect
> timely replies from now on. ]
>
> The first level quotes are indeed «». For the other two, I have to rely
> on what I have encountered before, namely, that the second level is
> denoted with double curly quotes “” and third with single curly quotes
> ‘’.
>
> I have come across those in EU documents. There is a style guide for
> the European Institutions.[1][2][3]
>
> I do not know latex notation to help you with the technicalities.
> Here are the unicode points:
>
> | « | U+00AB |
> | » | U+00BB |
> | “ | U+201C |
> | ” | U+201D |
> | ‘ | U+2018 |
> | ’ | U+2019 |
>
> All the best,
> Protesilaos
>
> [1] Quotes: <http://publications.europa.eu/code/el/el-4100107el.htm>.
> [2] General info: <http://publications.europa.eu/code/el/el-4100000.htm>.
> [3] Main portal: <http://publications.europa.eu/code/el/el-000100.htm>.
^ permalink raw reply [relevance 9%]
* org-attach-git don't automatically commit changes
@ 2021-01-29 16:03 9% Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-01-29 16:03 UTC (permalink / raw)
To: orgmode
Hi,
I don't know if this is a bug or if I am doing something wrong...
According to the manual:
#+begin_quote
If the directory attached to an outline node is a Git
repository, Org can be configured to automatically commit changes to
that repository when it sees them.
To make Org mode take care of versioning of attachments for you, add the
following to your Emacs config:
(require 'org-attach-git)
#+end_quote
I don't see that org-attach "automatically commit changes when it sees
them". Only when I run in the attached directory `M-:
(org-attach-git-commit) RET' it works fine.
`org-attach-after-change-hook' is set to `(org-attach-git-commit)'.
Regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* A quick LaTeX reference guide in Org
@ 2021-10-24 14:23 9% Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-10-24 14:23 UTC (permalink / raw)
To: orgmode
Hi,
The TeXstudio editor includes a comprehensive LaTeX reference guide in
HTML
(https://github.com/texstudio-org/texstudio/blob/master/utilities/latexhelp.html).
I have converted it to Org with Pandoc (and then cleaned it up and fixed
some broken links). It can be downloaded here:
https://cloud.disroot.org/s/krGSf7TmFZRiyZL
I think it may be useful for a quick LaTeX query. You could even use
org-ql and define a function like this:
(require 'org-ql)
(defun my-latex-apropos ()
(interactive)
(let ((regexp (if (not (current-word t t))
(read-from-minibuffer "Find (regexp): ")
(read-from-minibuffer "Find: " (current-word t t)))))
(org-ql-search
"/path-to/latexreference.org"
`(regexp ,regexp))))
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: PDF export, table of contents and internal links
@ 2022-06-29 19:56 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-06-29 19:56 UTC (permalink / raw)
To: Sébastien Gendre; +Cc: orgmode
Hi, Sébastien,
Sébastien Gendre writes:
> To generate the table of contents, I have to compile my .tex file into
> PDF 2 times. The first time, I got no toc. The second time the toc was
> here.
I would say It's a normal LaTeX thing. Sometimes LaTeX needs more than
one compilation to finish processing things like TOC or
cross-references, because it writes to auxiliary files if there has been
any change in those elements. What I suggest is that you use latexmk as
the default 'org-latex-pdf-process'. latexmk is a script that takes care
of intelligently compiling everything, as many times as necessary.
I have in my init:
(setq org-latex-pdf-process
'("latexmk -lualatex -output-directory=%o -e '$lualatex=q/lualatex
%%O -shell-escape %%S/' %f"))
(I use LuaTeX instead of pdfTeX).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* [Patch] Pre-/postpend arbitrary LaTeX code to a section
@ 2022-09-18 12:27 9% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-09-18 12:27 UTC (permalink / raw)
To: orgmode
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
Hi all,
I don't know if the following scenario usually appears in the workflow
of other Org users as well. Otherwise, I think this patch could be
ignored.
In my workflow I often need to pre- or postpend some LaTeX code
immediately before or after a section. Consider the following example:
------------------
* A section
Lorem ipsum
#+latex: \foo
* Another section
Lorem ipsum
-----------------
The \foo command affects the second section, but for Org it belongs to
the content of the first section. If I comment this section out or mark
it as non-exportable, then the LaTeX code has no effect. I think a
simple solution could be to have the PRESEC AND POSTSEC properties to
prepend or postpend arbitrary code to a section. These properties could be
extended with PRESEC+ and POSTSEC+. An example of use:
* Section
:PROPERTIES:
:presec: \begingroup\foo
:postsec: \endgroup
:END:
...
Best regards,
Juan Manuel
--
--
------------------------------------------------------
Juan Manuel Macías
https://juanmanuelmacias.com
https://lunotipia.juanmanuelmacias.com
https://gnutas.juanmanuelmacias.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-lisp-ox-latex.el-Add-properties-for-arbitrary-LaTeX-.patch --]
[-- Type: text/x-patch, Size: 2844 bytes --]
From 56924d69a2090dfeedf4b35ca33e10a48cbc42b5 Mon Sep 17 00:00:00 2001
From: Juan Manuel Macias <maciaschain@posteo.net>
Date: Sun, 18 Sep 2022 13:56:05 +0200
Subject: [PATCH] lisp/ox-latex.el: Add properties for arbitrary LaTeX code.
* (org-latex-headline): The `PRESEC' and `POSTSEC' properties prepend
and postpend arbitrary LaTeX code to a section, respectively.
---
lisp/ox-latex.el | 42 ++++++++++++++++++++++++++----------------
1 file changed, 26 insertions(+), 16 deletions(-)
diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index 1eb70ab20..a8c9aecd2 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -2322,22 +2322,32 @@ holding contextual information."
(and (string-match-p "\\<headlines\\>" v)
(string-match-p "\\<local\\>" v)
(format "\\stopcontents[level-%d]" level)))))
- info t)))))
- (if (and opt-title
- (not (equal opt-title full-text))
- (string-match "\\`\\\\\\(.+?\\){" section-fmt))
- (format (replace-match "\\1[%s]" nil nil section-fmt 1)
- ;; Replace square brackets with parenthesis
- ;; since square brackets are not supported in
- ;; optional arguments.
- (replace-regexp-in-string
- "\\[" "(" (replace-regexp-in-string "\\]" ")" opt-title))
- full-text
- (concat headline-label pre-blanks contents))
- ;; Impossible to add an alternative heading. Fallback to
- ;; regular sectioning format string.
- (format section-fmt full-text
- (concat headline-label pre-blanks contents))))))))
+ info t))))
+ ;; `PRESEC' and `POSTSEC' properties for arbitrary LaTeX code.
+ (pre-sec (let ((beg (org-element-property :begin headline)))
+ (goto-char beg)
+ (org-entry-get nil "PRESEC")))
+ (post-sec (let ((beg (org-element-property :begin headline)))
+ (goto-char beg)
+ (org-entry-get nil "POSTSEC"))))
+ (concat
+ (when pre-sec (format "%s\n\n" pre-sec))
+ (if (and opt-title
+ (not (equal opt-title full-text))
+ (string-match "\\`\\\\\\(.+?\\){" section-fmt))
+ (format (replace-match "\\1[%s]" nil nil section-fmt 1)
+ ;; Replace square brackets with parenthesis
+ ;; since square brackets are not supported in
+ ;; optional arguments.
+ (replace-regexp-in-string
+ "\\[" "(" (replace-regexp-in-string "\\]" ")" opt-title))
+ full-text
+ (concat headline-label pre-blanks contents))
+ ;; Impossible to add an alternative heading. Fallback to
+ ;; regular sectioning format string.
+ (format section-fmt full-text
+ (concat headline-label pre-blanks contents)))
+ (when post-sec (format "%s\n\n" post-sec))))))))
(defun org-latex-format-headline-default-function
(todo _todo-type priority text tags _info)
--
2.37.3
^ permalink raw reply related [relevance 9%]
* Re: org-fstree.el overview over directories (but no comments are possible)
@ 2022-10-30 15:40 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-10-30 15:40 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Uwe Brauer writes:
> Thanks I will give it a try, meanwhile I am trying filetree (in Melpa)
> that allows you to add notes to files, but it seems you have to open the
> files in order to add the notes, which is not what I am looking for
Interesting package, I didn't know about it... Have you ever tried it? I
just installed it, but M-x filetree-load-cmd-menu returns a 'Wrong type
argument: number-or-marker-p, list'. When I run toggle-debug-on-error It
seems it's a transient related problem...
hmm, I think the notes functionality that this package includes is more
in the league of org-remark or org-noter, i.e. to add notes to the file
content, but not a comment to the file itself, which I think is more
what you search. But I am not sure.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: [PATCH] org.el: use only link descriptions in indirect buffer names
@ 2021-05-23 11:25 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-05-23 11:25 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Ihor Radchenko writes:
> You can simply do (org-link-display-format (org-get-heading 'no-tags))
>
> Best,
> Ihor
Oh!! I see that with my code I just reinvented the wheel :-D:
---
org-link-display-format is a compiled Lisp function in ‘ol.el’.
(org-link-display-format S)
Replace links in string S with their description.
If there is no description, use the link target.
---
Thank you very much for the suggestion, Ihor!
(new patch attached)
Best regards,
Juan Manuel
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org-el-use-only-link-descriptions-in-indirect-buffer.patch --]
[-- Type: text/x-patch, Size: 953 bytes --]
From b859f45abaa94e546e625b7b8c9f47ed64d6b4b4 Mon Sep 17 00:00:00 2001
From: Juan Manuel Macias <maciaschain@posteo.net>
Date: Sat, 22 May 2021 15:33:15 +0200
Subject: [PATCH] org.el: use only link descriptions in indirect buffer names
* lisp/org.el (org-tree-to-indirect-buffer): If the variable `heading'
contains a link with a description, it is replaced by the description string.
---
lisp/org.el | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/lisp/org.el b/lisp/org.el
index 1bd9e02eb..ca87cac67 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -6895,8 +6895,7 @@ frame is not changed."
(while (> (setq level (org-outline-level)) arg)
(org-up-heading-safe)))
(setq beg (point)
- heading (org-get-heading 'no-tags))
+ heading (org-link-display-format (org-get-heading 'no-tags)))
(org-end-of-subtree t t)
(when (org-at-heading-p) (backward-char 1))
(setq end (point)))
--
2.26.0
^ permalink raw reply related [relevance 9%]
* Re: Syntax Proposal: Multi-line Table Cells/Text Wrapping
@ 2021-03-21 8:43 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-03-21 8:43 UTC (permalink / raw)
To: Samuel Wales; +Cc: orgmode
Hi Samuel,
Samuel Wales <samologist@gmail.com> writes:
> i like that. such an org edit special type feature could efven in
> principle work for a column or a row all at once.
I like the idea of being able to edit rows or columns as well...
As I mentioned in a previous message, I made this rudimentary proof of
concept (only with cells):
https://lunotipia.juanmanuelmacias.com/edit-cell-sample-2021-03-19_09.29.17.mp4
The idea is that the content of the cell would be 'filled' while it is in
the edit buffer and, back to the cell, it would be a single line again.
Certain marks (in my sample it is a simple macro (nl = latex \newline)
would cause a line break in the edit buffer, to facilitate editing.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: Depreciating TeX-style LaTeX fragments
@ 2022-01-16 13:26 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-01-16 13:26 UTC (permalink / raw)
To: Colin Baxter, Timothy, Sébastien Miquel; +Cc: orgmode
Colin Baxter writes:
> Ah, LaTeX3 - whatever happened to that?
If you're a LaTeX user, you're already using LaTeX3 to a very high
extent, even if you don't see it. The current idea is not to replace
LaTeX2e with LaTeX3 as a new version, but to gradually incorporate
elements of LaTeX3 into the LaTeX kernel, like the new syntax, xparse,
etc. LaTeX3 is already present in many aspects of LaTeX, and that is an
undeniable advance. If anyone is interested in the state of the art,
this short talk by Frank Mittelbach at TUG 2020 is very illustrative:
https://invidious.snopyta.org/watch?v=zNci4lcb8Vo
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: Org-syntax: Intra-word markup
@ 2021-12-03 15:01 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-12-03 15:01 UTC (permalink / raw)
To: Max Nikulin; +Cc: orgmode
Hi Maxim,
Max Nikulin writes:
> More explicit markup leaves less room for ambiguities, and I like the
> idea due to this reason. On the other hand it diverges from principle
> of lightweight markup. The almost only special character in TeX is
> "\", HTML has three ones "&<>" with simple escape rules. Org uses many
> special characters to avoid verbosity and requires some tricks to
> escape them. Markers like "\{" make Org more verbose but do not make
> it more strict, a lot of things still rely on heuristics.
Excellent explanation. Thanks for the clarification.
> I have an idea what can be done when some special markup is required
> that is not fit into current syntax. Unfortunately some new constructs
> should be introduced anyway: inline objects and multiline elements
> that represent simplified result of parsed Org structures:
>
> ((italic "intra") "word")
>
> wrapped with some markup. It should satisfy any special needs (and
> even should allow to create invalid impossible constructs). Maybe idea
> of combination of lightweight markup and low-level blocks better suits
> for some other project with more expressive internal representation.
> In Org it may become the most hated feature.
I really would like a solution in this direction. In LaTeX there is a
command called \protect (which has nothing to do with this topic and is
used for other things, but I like the 'protection' concept); we could
perhaps think of a type of mark to protect the 'usual' marks when syntax
consistency is compromised in some way by the context. Maybe something
like enclosing the normal marks between two double single quotes ''...''
---or a single set of single quotes before the leading marker--- as I
proposed in another thread:
#+begin_example
''*protected emphasis*''
#+end_example
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: [PATCH] org-attach: Attach current Gnus article parts
@ 2022-05-08 13:23 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-05-08 13:23 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko writes:
> I think that supporting only Gnus is too specific. Not all the people
> use Gnus as mail reader. And the extra menu option you propose will only
> eat up space for people not using Gnus.
>
> I'd prefer a more generic approach working in any kind of email reader,
> be it rmail, gnus, mu4e, notmuch, or wunderlust. The approach can
> probably making use of message-mode or MML libraries from Emacs core.
Well, as I said, I have chosen Gnus because it is part of GNU Emacs. In
any case, if anyone wants to write a patch with a more general solution,
I'd encourage them. I think that would be an interesting feature for
org-attach. I only use Gnus and unfortunately I'm not familiar with
other mail reader libraries (I could try to do something more "agnostic"
from message-mode, when I have some more time...).
What I don't quite understand is why it wouldn't be appropriate to add a
new entry with the new feature to the org-attach menu.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: http: links in the manual
@ 2022-08-21 9:55 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-08-21 9:55 UTC (permalink / raw)
To: Max Nikulin; +Cc: orgmode
Max Nikulin writes:
> One may got no response trying to fix a link.
>
> Max Nikulin to emacs-orgmode. [PATCH] org-manual.org: Update links to
> MathJax docs. Sun, 3 Oct 2021 23:17:46 +0700.
> https://list.orgmode.org/sjcl3b$gsr$1@ciao.gmane.io
>
> In the particular case of docs.mathjax.org I am unsure if mild
> preference of http: over https: is not a mistake in the server
> configuration. I do not mind "https:" there, any variant is better
> than the old broken link.
Maybe, instead of repairing the links manually, we could think of some
code that would do this work periodically, and also check the health of
the links, running a url request on each link and returning a list of
broken links. I don't know if it is possible to do something like that
in Elisp, as I don't have much experience with web and link issues. I
think there are also external tools, like Selenium Web Driver, but my
experience with it is very limited (I use Selenium from time to time
when I want to take a screenshot of a web page).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: [possible patch] Remove the '\\[0pt]' string from the last line of a verse block in LaTeX export
@ 2024-01-21 19:25 9% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2024-01-21 19:25 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode, Max Nikulin
Ihor Radchenko writes:
> Upon looking closer into selective removal, it turned out to be more
> tricky than I thought. I'm afraid that using \\[0pt] only in some places
> may become a bit of headache to maintain - we may accidentally break
> certain regexp replacements in `org-latex-verse-block'. In particular,
> when verse contents is not straightforward and uses \\[0pt].
>
> Given that `org-latex-line-break-safe' also introduced the problem with
> verse blocks, I decided that it is better to remove it at the end.
LaTeX code generated without org-latex-line-break-safe is much cleaner.
The decision to make this variable obsolete seems correct to me, if
there is already a better and more discreet solution. I don't know if it
will cause many problems with custom settings and filters written in
relation to this variable, as Maxim commented in a previous email... I
hope not. I have a couple of filters written already, but I don't think
it will take much work for me to readjust them.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 9%]
* Re: publishing: no default publishing function, or symbol is not defined
@ 2021-06-25 8:38 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-25 8:38 UTC (permalink / raw)
To: Christopher W. Ryan; +Cc: orgmode
Hi Christopher, sorry for the slow reply
Christopher W. Ryan writes:
> Any advice for how to get *both* theindex.html and my main document in
> html? So far I can only get one or the other, depending on whether I
> include a non-nil value for a :makeindex option.
I don't understand the question. With the option `:makeindex t' a
document `theindex.inc' is created/updated every time you call
`org-publish-project', and also a document `theindex.org', which
contains the directive `#+INCLUDE: theindex.inc'. This is the document
which is exported to html as an index, along with the rest of the org
documents that you have inside the folder specified in the
`:base-directory' option.
For more info, you can evaluate (info (org) Generating an index)
What is your org-publish configuration?
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Exporting Org file to Html with collapsable headings
@ 2022-01-21 12:23 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-01-21 12:23 UTC (permalink / raw)
To: ZIPING CHEN; +Cc: orgmode
ZIPING CHEN writes:
> I am working on a large org file with exceptional number of
> subheadings. For example, I may have org headings inside headings up
> to 20 or 30 layers deep.
>
> I may have many things like this in the middle of the file.
> ************************** a new heading.
>
> When I export the file to html, I like to export in such a way that
> the org headings become collapsable headline in html (toggle switch).
> I spend some time search the web, and find a theme called bigblow
> which does something close to what I want, but not exactly. It provide
> limited layer of toggle switch only. I wish to turn all layers of
> headings in org file into collapsable headline to html.
>
> Does anybody know a way I can accomplish this?
I think that you need to add javascript and enclose the collapsible
content in a div. If you google for 'html collapsible sections' there is
quite a bit of information on how to achieve this from the html side.
Here, for example:
https://levelup.gitconnected.com/collapsible-sections-with-or-without-javascript-3fd871955a9d
On the other hand, although not exactly related to what you are looking
for, you may be interested in taking a look at 'organize'. I have not
tried it, and as far as i know, it has its limitations:
https://github.com/200ok-ch/organice
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Question Regarding Creating HTML Style Buttons With Org Mode
@ 2022-02-17 22:10 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2022-02-17 22:10 UTC (permalink / raw)
To: Samuel Banya; +Cc: orgmode
Hi Samuel:
Samuel Banya writes:
> Is it possible to create HTML style buttons using Org Mode itself?
One possibility is to use a custom link. For example:
#+begin_src emacs-lisp
(org-link-set-parameters "button"
:face '(:foreground "green" :underline t)
:export (lambda (path desc backend)
(when (eq backend 'html)
(format "<form><button class=\"mybutton\" formaction=\"%s\">%s</button></form>" path desc))))
#+end_src
#+HTML_HEAD: <style> .mybutton{background-color:#4CAF50;border:none;color:white;padding:15px32px;text-align:center;text-decoration:none;display:inline-block;font-size:18px;margin:4px2px;cursor:pointer;</style>
[[button:some target][This is a button]]
NB: I have borrowed the style from here: https://www.w3schools.com/csS/css3_buttons.asp
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: interleaving comment between rows of a table?
@ 2022-03-07 15:54 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-03-07 15:54 UTC (permalink / raw)
To: Greg Minshall; +Cc: orgmode
Hi Greg,
Greg Minshall writes:
> i don't remember anybody asking about this.
>
> i'd sometimes find it useful to be able to interleave comments -- using
> (almost) whatever syntax -- between rows in an org-mode table.
> (normally, this would be to provide context/rationale for the subsequent
> row(s).)
I find the annotate package useful for inserting comments and
annotations in "difficult" places. I find annotations in the margin (as
overlays) intrusive, so I have set this variable, so that the
annotations appear only in the echo area and as a tooltip:
(setq annotate-use-echo-area t)
See this screenshot: https://i.imgur.com/koKYL0K.png
Other possible settings for annotate:
(set-face-attribute 'annotate-highlight nil :foreground "chocolate" :background nil :underline nil)
(set-face-attribute 'annotate-highlight-secondary nil :foreground "chocolate" :background nil :underline nil)
(setq annotate-file "path/to/my/annotate/file")
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [possible patch] Basic fontspec code for LuaLaTeX and XelaTeX (was "LaTeX export: when is it more useful...")
@ 2022-07-11 15:00 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-07-11 15:00 UTC (permalink / raw)
To: Timothy; +Cc: Maxim Nikulin, Ihor Radchenko, orgmode
Timothy writes:
> As an illustrative example, if I include this in one of my documents and create
> a PDF:
> ┌────
> │ #+options: fontset:biolinum
> └────
>
> Then I’ll get text with:
> ⁃ libertine roman as the serif font
> ⁃ biolinum as the serif, and default, font
> ⁃ source code pro as the mono font
> ⁃ newtxmath as the maths font
>
> Similarly I can do `fontset:noto' and you can guess what that does.
I think it's a very good idea to be able to add the options using
#+options:..., forgive the redundancy :-)
When you talk about fontset, I understand that you mean lists of
families with their options that you have previously defined, is that
right?
In any case, I think it would also be nice if the user could add only
one family for roman, sans, mono or math, if he/she prefers it that way.
Something like:
#+options: rmfont:Minion Pro
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [possible patch] Remove the '\\[0pt]' string from the last line of a verse block in LaTeX export
@ 2024-01-13 16:05 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2024-01-13 16:05 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko writes:
>> Can anyone think of a possible scenario where removing the '\\[0pt]' in
>> the last line would cause a problem? If not, I might send a patch in the
>> next few days. (I'm afraid that going back to abusing
>> replace-regexp-in-string. I can't think of any other more elegant
>> solution...).
>
> In such scenario, we may technically violate what users ask us to do:
>
> #+begin_verse
> I really want newline here\\
> #+end_verse
I'm not sure if users asked for that specifically.
You want a new line when there is a new line.
This makes sense:
#+begin_verse
I really want newline here\\
blah...
#+end_verse
This does not:
#+begin_verse
I really want newline here\\
#+end_verse
For LaTeX it is the same as this:
#+begin_verse
I really want newline here
#+end_verse
But this specifically alters the expected result in LaTeX, modifying the
space after the environment:
#+begin_verse
I really want newline here\\[0pt]
#+end_verse
What is the cause? I don't know. But it happens.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: how to get multi-line author in ODT export?
@ 2021-08-26 16:05 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-08-26 16:05 UTC (permalink / raw)
To: Eric S Fraga; +Cc: orgmode
Hi Eric,
I think the problem is in this two lines of `org-odt-template', that
creates the meta.xml file inside the odt file:
(format "<dc:creator>%s</dc:creator>\n" author)
(format "<meta:initial-creator>%s</meta:initial-creator>\n" author)
Perhaps, modifying them like this:
(format "<dc:creator><![CDATA[%s]]></dc:creator>\n" (replace-regexp-in-string "\\\\\\\\" "\n" author))
(format "<meta:initial-creator><![CDATA[%s]]></meta:initial-creator>\n" (replace-regexp-in-string "\\\\\\\\" "\n" author))
We could do this in our documents:
#+AUTHOR: Han Solo \\ Chewbacca
(little tested)
Best regards,
Juan Manuel
Eric S Fraga writes:
> So, as usual, I answer my own question, sort of.
>
> The problem is that org exports the author text enclosed within a
> special directives, specifically:
>
> (format "<text:initial-creator>%s</text:initial-creator>" author))
>
> New line directives are not allowed within this declaration, it
> seems. Removing (manually) the initial-creator directive then works.
>
> So, my question would be: is this text:initial-creator tagging
> necessary? If not, can we remove it? The OpenDocument schema is vague
> about whether this is necessary. If we cannot remove it, i.e if
> initial-creator is required in the document, could it be put in
> separately (as a meta:initial-creator tag) so that the author field can
> be more general?
>
> I am *not* an ODT expert of any sort. But it is my route to Word
> documents when the need arises (which is luckily seldom).
>
> Anyway, no panic: I can simply manually edit the odt file just before
> the final processing...
>
> Thank you,
> eric
^ permalink raw reply [relevance 10%]
* Re: Playing down the text in org-mode
@ 2022-01-13 21:39 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-01-13 21:39 UTC (permalink / raw)
To: fatiparty; +Cc: orgmode
fatiparty@tutanota.com writes:
> If I do something in emacs-lisp I would still need some form of
> containment characters.
I think a custom link would suffice for text within the paragraph. A
quick example:
#+begin_src emacs-lisp
(defface smaller
'((t :foreground "#8D8D84" :height 0.9))
"")
(org-link-set-parameters "smaller"
:face 'smaller
:export (lambda (path desc format)
(cond
((eq format 'latex)
(format "{\\small %s}" desc)))))
#+end_src
This text is important, [[smaller:x][but this one is not so important]]
A screenshot:
https://i.imgur.com/11KbJHQ.png
if you want finer tuning and more control over the format, John's
scimax-editmarks package seems like a very interesting option (although
I think Org should remain as format-agnostic as possible...)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: word counts and org-mode drawers
@ 2021-02-01 23:29 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-02-01 23:29 UTC (permalink / raw)
To: Sharon Kimble; +Cc: orgmode
Hi,
Sharon Kimble <boudiccas@skimble.plus.com> writes:
> How can I exempt an org-mode drawer, and its contents, from word counts
> please. I am using 'wc-mode' but I can't see how to do it.
It is not a solution with wc-mode, but maybe this simple function, based on
`count-words', can serve you. It counts the words in the buffer
excluding all drawers and their contents:
#+begin_src emacs-lisp
(defun my-count-words-in-org-buffer ()
(interactive)
(let ((words 0))
(save-excursion
(save-restriction
(narrow-to-region (point-min) (point-max))
(goto-char (point-min))
(while (forward-word-strictly 1)
(if (org-at-drawer-p)
(re-search-forward ":END:")
(setq words (1+ words))))))
(message "Org buffer has %d word%s."
words (if (= words 1) "" "s"))))
#+end_src
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Syntax Proposal: Multi-line Table Cells/Text Wrapping
@ 2021-03-18 22:41 10% ` Juan Manuel Macías
0 siblings, 2 replies; 200+ results
From: Juan Manuel Macías @ 2021-03-18 22:41 UTC (permalink / raw)
To: Tim Cross; +Cc: orgmode
Tim Cross <theophilusx@gmail.com> writes:
> From watching these discussions in the past, I think the big stumbling
> block is how easily multi-row columns can be added and maintained in the
> various export formats. Some are easy, like HTML, but others are less
> so. In particular, I know from my many years working with Latex,
> multi-row columns are not straight-forward. There are lots of edge cases
> to deal with and it is hard to get a consistent result programatically.
>
> Proposals like this one can seem simple and straight-forward on the
> surface. However, implementation is another matter. All of the exporters
> will need to be updated to handle this new syntax and it will probably
> take a fair bit of work to handle it correctly in just plain org files
> (formatting, highlighting etc).
I don't know if anyone has come up with this other possibility: if the
problem is (usually) the inconvenience of editing cells with a lot of
text within an Org document (since when exporting to LaTeX for example,
it makes no difference whether the cell content is on a single line, if
the tabularx package is used properly), then the possibility of editing
a cell in a dedicated buffer would be very practical here. A kind of
`org-edit-special' for cells... That could be combined with
`org-table-toggle-column-width'.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [DISCUSSION] Re-design of inlinetasks
@ 2023-08-27 17:25 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2023-08-27 17:25 UTC (permalink / raw)
To: Ihor Radchenko
Cc: Bastien Guerry, Fraga, Eric, Samuel Wales, Max Nikulin,
emacs-orgmode@gnu.org
Ihor Radchenko writes:
> Although, the name "inlinetask" is actually awkward in such use case.
> Something like inlinesection would fit better. Or inlineheading.
Completely agree. I like inlinesection and inlineheading equally.
> And what about drawers? Don't they fit the idea of "detached" element?
But drawers would not serve as a "detached section"... Although they are
certainly very versatile. I usually use drawers to export as small
"containers". And when I don't export them, they are very useful for
temporarily saving all kinds of "things". In Spanish we have the term
"cajón de sastre" (lit.: "a tailor drawer") to refer to something where
you can store everything :-)
As for the inlinetask (or whatever they may be called in the future),
the fact that they are a kind of hybrid between a section (unrelated to
the level hierarchy) and a drawer seems very interesting to me. Apart
from the scenario of the anonymous sections that I mentioned before, I
can think of a few more. For example, something like this:
*************** WORKING Complete this :noexport:
DEADLINE: <2023-08-27 dom>
Content
*************** END
And the combination of org-store-link with org-transclusion can also be
interesting.
Or, for example this other example, which is not possible now, but with
some modification in org-mime-org-subtree-htmlize I think it is:
*************** TODO Email this
DEADLINE: <2023-08-27 dom>
:PROPERTIES:
:mail_to: mail address
:mail_subject: mail subject
:END:
Content
*************** END
Well, it's some scattered ideas. In general I think that "inlinesection/-heading"
is an element that could be very productive in certain cases, since it
allows to "locally" suspend the (necessary) rigidity of the tree hierarchy.
--
Juan Manuel Macías
https://juanmanuelmacias.com
https://lunotipia.juanmanuelmacias.com
https://gnutas.juanmanuelmacias.com
^ permalink raw reply [relevance 10%]
* Re: Smart quotes not working correctly with single quotes
@ 2021-05-28 20:19 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-05-28 20:19 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: orgmode
Hi Nicholas,
Nicolas Goaziou writes:
> Genuine question: what language uses two different styles of outer
> (level 1) quotes? And in what context?
I answer in the case of Spanish. In Spanish the level 1 quotes are «»
(french quotes). The level 2 are “...” (english quotes). Only in some
cases, and according to some writers and manuals, single quotation marks
‘...’ are correct as 1 level quotes (left single quotation mark ...
right single quotation mark), in short segments, generally when you want
to indicate the translation of a term. i.e.:
car (‘coche’)
Anyway, in Spanish it is not correct to use second level quotes “...” as
first-level quotes. I do not know if it is correct in German.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [proof of concept] inline language blocks
@ 2024-02-29 12:50 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2024-02-29 12:50 UTC (permalink / raw)
To: Max Nikulin; +Cc: emacs-orgmode
Max Nikulin writes:
>> Anyway, I think your example only makes sense in HTML, or at least I
>> can't make sense of it in LaTeX. Why would anyone want &foo{text} to be
>> passed to LaTeX as \bar{text}, instead of just &bar{text}? In HTML it
>> does seem sensible to me that someone would want to change the tags.
>> Maybe with a :html-tag, or something like that.
>
> Consider a document aimed to be exported to different formats. It is
> unlikely that names of commands, elements, classes, etc. match for all
> of them.
It makes sense, although I have never encountered a case like this.
Usually (and returning to the example of the large special blocks), if
in org I put something like:
#+begin_foo
...
#+end_foo
I try to ensure that there is a "foo" environment in LaTeX, a "foo" class
in html or a "foo" style in odt (now I don't remember if the odt exporter
produces paragraph styles from special blocks. I don't think so).
In any case, on second thought, maybe someone wants to reuse a LaTeX
preamble, css style sheets or any odt templates. I see no problem, then,
in there being attributes like :latex-command, :html-tag, :odt-style :html-attribute,
etc., which override the default values.
>> As for :latex-command, if I understand it correctly, I don't quite see
>> how useful this could be:
>> &foo[:latex-command bar]{text} == LaTeX ==> \bar{text}
>> when it is simpler to put:
>> &bar{text}
>
> Command may require additional arguments and it should be convenient
> to define shortcuts to the same command with different arguments:
>
> &la{text} => \foreignlanguage{latin}{text}
> &es{text} => \foreinglanguage{spanish}{text}
With the current implementation:
#+options: inline-special-block-aliases:(("bar" :prelatex [bar]) ("baz" :prelatex [baz]))
&foo[@bar@]{lorem ipsum} ==> \foo[bar]{lorem ipsum}
&foo[@baz@]{lorem ipsum} ==> \foo[baz]{lorem ipsum}
Your example is less verbose, but with this implementation you can do combinations, it's
more granular, I think:
&foo[@bar@ :smallcaps t]{lorem ipsum} ==> {\scshape\foo[bar]{lorem ipsum}}
&foo[@baz@ :lang it]{lorem ipsum} ==> \foo[baz]{\foreignlanguage{italian}{lorem ipsum}}
I think this is quite flexible and leaves a great deal of freedom to the user.
>> The same thing happens with the anonymous variant:
>> &_[:latex-command foo]{text} == LaTeX ==> \foo{text}
>> which is identical to putting &foo{text}
>> The anonymous variant would be equivalent in LaTeX to a
>> \begingroup...\endgroup, or rather to {...}. One could add all the
>> commands one wants within the group simply with :prelatex:
>> &_[:prelatex \foo\bar\vaz\blah{}]{text}
>> ==> {\foo\bar\vaz\blah{}text}
>
> The idea is to not add \begingroup and \endgroup if LaTeX command is
> specified (or to control it by a dedicated attribute). Again, consider
> a document suitable for multiple export formats.
Indeed, if the :latex-command attr is implemented should work in both
variants. In such a way, perhaps:
&_[:latex-command foo]{lorem} ==> \foo{lorem}
> I think, flexibility in respect to underlying
> commands/classes/elements allows to minimize changes in documents
> later. Sometimes it is necessary to switch to another LaTeX package,
> CSS framework, etc. It allows usage semantic names within Org
> documents despite they may be exported to the same command.
>
>> In any case, I think that my implementation leaves open the possibility
>> of extending it with everything you mentioned, or anything else.
>
> The question is proper balance of built-in features, flexibility,
> implementation complexity. It would be unfortunate if most of users
> will have to create custom backends even for basic documents.
We can continue the discussion when I publish my experimental branch and
share the link. I'm a little late because I want to make some
corrections to the code first.
--
Juan Manuel Macías -- Composición tipográfica, tratamiento de datos, diseño editorial y ortotipografía
^ permalink raw reply [relevance 10%]
* Re: An attempt to convert Elfeed entries (with parameters) to Org trees
@ 2021-06-24 8:02 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-24 8:02 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Hi Ihor,
Ihor Radchenko writes:
> What about duplicates? If you insert all the feeds from the last few
> months and then update the same headline weeks later, there will overlap
> between elfeed entries.
When I update a headline, all previous feeds are removed, so there is no
possibility of duplicates. As I said, I find this system very useful to
have an overview within Org of the latest updates to certain feeds, such
as new packages uploaded to CTAN. I also have an org-capture template
only for new CTAN packages, in case I see any interesting packages.
I also have a section on CTAN news in my blog about typography and TeX
(in Spanish), and I update it using that method.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [tip] Export and open a PDF in Android via Termux
@ 2022-05-16 16:05 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-05-16 16:05 UTC (permalink / raw)
To: Max Nikulin; +Cc: Ihor Radchenko, Eric S. Fraga, orgmode
Max Nikulin writes:
> Does termux have a notion of mailcap, e.g. mime-support package or
> something similar? I have a hope that
>
> application/pdf; termux-open %s
>
> in /etc/mailcap or in ~/.mailcap might be enough instead of explicit
> configuration of particular packages.
I've been playing with Termux for a short time and what you're
suggesting hadn't occurred to me. Indeed, it works fine with a
~/.mailcap file! I have done a test with an attachment in Gnus:
https://imgur.com/a/g1Auvxp
Termux is quite interesting (and addictive :-)). Now I am playing with
Termux-api to send notifications from Emacs/Gnus to Android (with
gnus-desktop-notifier and the termux-notification command). And also to
send sms from Emacs and bbdb...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [PATCH] A proposal to add LaTeX attributes to verse blocks
@ 2021-05-01 11:46 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-05-01 11:46 UTC (permalink / raw)
To: Bastien; +Cc: orgmode
Hi Bastien,
Thank you very much again for your kind suggestions.
Bastien writes:
> I'm copying Eric, a poweruser of the LaTeX backend, so that he can
> perhaps comment on the general usefulness of this addition.
I think these additions (line numbers, optical centering of the poem,
etc.) can be useful (IMHO) for the correct representation of poetry
(generally in Humanities), since the verse.sty package is a sort of
'unofficial' replacement for the standard LaTeX verse environment, which
has certain limitations.
> The patch lacks a commit message - see this explanations:
> https://orgmode.org/worg/org-contribute.html#commit-messages
Sorry again for not including a commit message. If the patch it is
finally accepted, I can submit a new version that includes a commit
message (and a few minor fixes I made to the code).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Remove all Org metadata with header argument `:comments org'
@ 2021-06-03 14:54 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-03 14:54 UTC (permalink / raw)
To: orgmode
I am writing an *.el file from an *.org file (and then I run
org-babel-tangle). With the header argument `:comments org' not only the
text in my org file is converted to comments (my desired goal) but also
the drawers, keywords and other Org metadata. Since I don't see that all
that stuff is necessary in a source file, wouldn't it be better to get
rid of it during the tangle process, leaving only pure content as
comment strings? Maybe converting the Org file content to plain text
with ox-ascii, or something like that?
What do you think?
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* `:export' attribute?: Re: Experimental public branch for inline special blocks
@ 2024-03-10 2:08 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2024-03-10 2:08 UTC (permalink / raw)
To: orgmode
I'm thinking about adding a new global attribute, `:export', that
would granularly control whether or not to export the object and how to
export it.
Possible values: "noexport", "contents" (it would export only the content)
or the backends to which you want to export, separated by spaces. Each
backend should be followed by a "+" sign (= export all) or "*" (export
content only). For example:
@foo[:color red :export latex+ odt* html*]{lorem ipsum dolor}
This means that "lorem ipsum dolor" would be exported with color format
to LaTeX, but only the content would be exported to odt and html.
Wdyt?
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* [PATCH] [BUG] Bad fontification in full displayed links
@ 2021-07-09 9:15 10% Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-07-09 9:15 UTC (permalink / raw)
To: orgmode
[-- Attachment #1: Type: text/plain, Size: 178 bytes --]
Hi,
To reproduce the bug:
1. Put some link: [[target][description]]
2. Run `org-toggle-link-display'
As a possible fix I'm attaching this patch.
Best regards,
Juan Manuel
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org.el-prevent-partial-fontification-link-display-full.patch --]
[-- Type: text/x-patch, Size: 1252 bytes --]
From caf32a7e1fb1b4bddfa011520f5403d5b6b19ddd Mon Sep 17 00:00:00 2001
From: Juan Manuel Macias <maciaschain@posteo.net>
Date: Tue, 8 Jun 2021 01:55:02 +0200
Subject: [PATCH] org.el: prevent partial fontification when a link is
displayed full
* lisp/org.el (org-activate-links): apply `face-property' variable in
other cases when handle invisible parts in bracket links
---
lisp/org.el | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/lisp/org.el b/lisp/org.el
index 1bd9e02eb..b55d8798a 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -5224,9 +5224,11 @@ This includes angle, plain, and bracket links."
,(or (org-link-get-parameter type :display)
'org-link))
properties)))
+ (add-face-text-property start visible-start face-property)
(add-text-properties start visible-start hidden)
- (add-face-text-property visible-start visible-end face-property)
+ (add-face-text-property visible-start visible-end face-property)
(add-text-properties visible-start visible-end properties)
+ (add-face-text-property visible-end end face-property)
(add-text-properties visible-end end hidden)
(org-rear-nonsticky-at visible-start)
(org-rear-nonsticky-at visible-end)))
--
2.31.1
^ permalink raw reply related [relevance 10%]
* Re: [patch] Fix inner smart quotes in French
@ 2023-08-10 21:50 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2023-08-10 21:50 UTC (permalink / raw)
To: Bastien; +Cc: Max Nikulin, orgmode
Bastien writes:
> Yes, this is also what the French national printing press ("Imprimerie
> nationale"), which is quite authoritative in this matter, recommends.
>
> Note that the Full recommendation of the Imprimerie nationale is to
> repeat second-level quotation marks at the beginning and of each line
> when the text spans over several lines, like this:
>
> Then X reported : « This is what Y said : « Here is
> « a quotation with a paragraph spaning over several
> « lines, with each line starting with a quotation mark
> « until the end of the quotation. »
>
> (The unique » at the end is intentional, the rule is to not repeat.)
I've been looking at the babel-french documentation (LaTeX)
(http://mirrors.ctan.org/macros/latex/contrib/babel-contrib/french/frenchb.pdf),
which claims to be based on "Lexique des règles typographiques en usage
à l’Imprimerie Nationale, troisième édition (1994)"; p. 3 is about
quotation marks and the different options:
-----
with all engines: the inner quotation is surrounded by double quotes
(“texte”) unless option InnerGuillSingle=true, then a) the inner
quotation is printed as ‹ texte › and b) if the inner quotation spreads
over more than one paragraph, every paragraph included in the inner
quotation starts with a ‹ or a › or nothing, depending on option
EveryParGuill=open (default) or =close or =none.
with LuaTeX based engines, it is possible to add a French opening or
closing guillemet (« or ») at the beginning of every line of the inner
quotation using option EveryLineGuill=open or =close; note that with any
of these options, the inner quotation is surrounded by French guillemets
(« and ») regardless option InnerGuillSingle; the default is
EveryLineGuill=none so that \frquote{} behaves as with non-LuaTeX
engines.
-----
I have tried this example with quotes per line:
https://i.imgur.com/od4HwUs.png
In any case (apart from LaTeX), it is clear that I was wrong when I said
that the inner quotes that my patch 'corrects' were 'incorrect'. What I
don't know is why babel-french defaults to the « “inner” » style. Is it
the most used currently in France? If the « « inner » » style is more
canonical, I don't mind having my patch 'fix' reverted.
--
Juan Manuel Macías
https://juanmanuelmacias.com
https://lunotipia.juanmanuelmacias.com
https://gnutas.juanmanuelmacias.com
^ permalink raw reply [relevance 10%]
* Re: ConTeXt exporter for Org Mode
@ 2021-08-04 19:43 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-08-04 19:43 UTC (permalink / raw)
To: Jason Ross; +Cc: orgmode
Hi Jason,
Jason Ross writes:
> Hello,
>
> I have developed a ConTeXt exporter for Org Mode. It is available at
> https://github.com/Jason-S-Ross/ox-context
>
> The exporter provides custom environments for each document element
> in an effort to make customization easier, in contrast to the Pandoc
> exporter which uses built-in environments for document elements.
>
> I welcome any feedback.
Congratulations on your excellent work. I am not a daily ConTeXt user, and I'm
afraid I can't help much. But I think a native exporter to ConTeXt
could be an important addition to Org. It could be interesting for users
who want to discover this powerful alternative to LaTeX (within the TeX
ecosystem), as well as for users who want high-quality pdf output without
the need for get caught up in the complexity of LaTeX packages, since
ConTeXt has a more monolithic conception than LaTeX.
Very interesting and promising, in any case.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* helm-org-names: browse the names of code blocks, tables and figures
@ 2022-03-11 22:24 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-03-11 22:24 UTC (permalink / raw)
To: orgmode
Hi all,
I've written this little package to browse with helm through the names
of code blocks, tables and figures in a document. A series of actions
can be executed on the candidate (go to object, edit a code block,
insert a link, etc.). In the list of figures that is displayed in Helm,
each figure name is accompanied by a thumbnail of the image.
A screenshot: https://i.imgur.com/DVIQv8x.png
The GitLab repo:
https://gitlab.com/maciaschain/helm-org-names
I'm afraid the package is still a bit raw, but I think it's usable :-).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* 'false' list item
@ 2021-02-15 17:37 10% Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-02-15 17:37 UTC (permalink / raw)
To: orgmode
Hi,
If a line in a paragraph starts with a digit (or letter) + period +
space, Org misinterprets that as a list item. I almost always notice
this only when I export my document, which is a nuisance.
I wonder if there is any standard solution to that, or if I'm missing
something... All that occurred to me is this "preventive" solution,
using `highlight-regexp':
#+begin_src emacs-lisp
(defface my-lists-item-box
'((t :weight bold :foreground "white" :background "orange"))
"")
(defun my-org-item-highlight ()
(highlight-regexp org-list-full-item-re 'my-lists-item-box))
(add-hook 'org-mode-hook 'my-org-item-highlight)
#+end_src
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [PATCH] Possibility of using alternative separators in macros
@ 2021-05-15 21:05 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-05-15 21:05 UTC (permalink / raw)
To: Bastien; +Cc: orgmode, Eric S Fraga
Hi Bastien,
Bastien writes:
> I'm skeptical too, so perhaps the best thing to do is to see if you
> need it or not, and if proven useful after a while, repost a patch?
I totally agree. I will try these modifications for a while, if they are
really useful. Anyway, as Nicolas commented in a previous post, it seems
that the natural habitat of macros consists of short lengths of text. I
am exploring now other interesting alternatives (ie.
org-link-set-parameters).
(On the other hand, maybe better than an alternate separator, some kind of
warning for unescaped commas might be more useful, as Maxim commented
here: https://orgmode.org/list/s7gfc6@ciao.gmane.io/)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: 'false' list item
@ 2021-02-21 19:33 10% ` Juan Manuel Macías
1 sibling, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-02-21 19:33 UTC (permalink / raw)
To: Kyle Meyer; +Cc: orgmode
Kyle Meyer <kyle@kyleam.com> writes:
> It seems that your approach would do a good job of helping you catch
> cases that you don't want to be treated as lists. I'm not aware of any
> related functionality in Org, so I don't think you're missing something
> there.
>
> Once you know that there is a particular spot that you want to prevent
> from being interpreted as a list, you could add a zero-width space in
> front of it:
>
> (info "(org)Escape Character")
>
> I'm not sure if that's the sort of solution you're asking for, though.
Thanks for your advice, Kyle. Adding the U+200B char. works fine to
avoid false positives. Anyway, like Tim Cross says, that situation
maybe should be considered as a bug. I think the ideal behavior would
be for Org to consider a list only when there is a blank line above.
But, well thought out, I am afraid that it would not prevent false
positives, as one may want perfectly write a list at the beginning of
the document, or start a plain paragraph with (for example) a digit + a
period + a space...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Question Regarding Creating HTML Style Buttons With Org Mode
@ 2022-02-18 20:38 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-02-18 20:38 UTC (permalink / raw)
To: Samuel Banya; +Cc: orgmode
Samuel Banya writes:
> I tried to use this idea, but I'm not sure how to set the 'target' in
> your example:
> [[button:some target][This is a button]]
>
> For example, I tried this:
> [[button:http://www.sambanya.com/artgallery.html][Art Gallery Page
> Link]]
>
> But received this error:
> user-error: Unable to resolve link:
> "button:http://www.sambanya.com/artgallery.html"
Hi Samuel,
It's strange... I have tried your link, and it works fine for me. I have
made this video capture:
https://cloud.disroot.org/s/SaHR7jenTWxFWZt
If you evaluate the `org-ling-set-parameters' expression that I gave
you, you should get when exporting to html:
<p>
<form><button class="mybutton" formaction="http://www.sambanya.com/artgallery.html">Art Gallery Page Link</button></form>
</p>
What version of org are you using?
(I don't have much knowledge of html or css, in any case. Just for the
basics).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: About 'inline special blocks'
@ 2022-05-25 13:55 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-05-25 13:55 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko writes:
> I think that we might simply allow to define complex configuration
> before the containing paragraph. Something like:
>
> #+attr_latex[name]: <complex config goes here>
> Vestibulum convallis, lorem blockname_[<<name>>]{text} a tempus semper, dui
> dui euismod elit, vitae placerat urna tortor vitae lacus.
>
> "<<name>>" will be treated as "<complex config goes here>" during
> export/parsing.
I really like this idea of taking the complex configuration (in case it
is needed) out of the paragraph. I vote for a procedure of this style.
That rows in favor of legibility and lightness. Of course, the blocks
that need an /ad hoc/ configuration represent, in my opinion, an extreme
use case; and, as I mentioned before, I think that it should be avoided
as much as possible. I also fully agree with Tim's comments on this.
Ideally, any format settings for LaTeX, odt, html, etc. must be done
globally, outside the body.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Org and Hyperbole
@ 2022-06-20 14:03 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-06-20 14:03 UTC (permalink / raw)
To: orgmode
Hi,
I've been intrigued with GNU Hyperbole for a while. I'm reading the
documentation and trying it out a bit. It seems that its button system
is very powerful. But Org links are also powerful (and exportable), and
can be extended outside of Org docs. It seems that hyperbole offers some
cool stuff that Org also has. And other things that are not in Org. I
find some parts a bit confusing. I wonder if anyone is using hyperbole
with Org and can put here some minimal workflow example where both
complement each other in some way. Just in case I'm missing something
useful...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Taking notes of videos in Emacs
@ 2022-07-09 11:37 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-07-09 11:37 UTC (permalink / raw)
To: Gerardo Moro; +Cc: orgmode
Hi, Gerardo,
Gerardo Moro writes:
> As for your own package, Juan Manuel, I understand the main purpose is
> to take screenshots of movies. Am I correct?
> Thanks!
Yes, it is a series of homemade hacks (if i called it "package" I would
sound too presumptuous lol), just to be able to take screenshots and add
them to an org document, along with a timestamp. I wrote it because I
use EMMS and not mpv.el, and also I don't need most of the features of
org-media-note.
If you don't use EMMS and are looking for something more complete that
includes screenshots, notes and many more features, then org-media-note
is definitely the ideal choice.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [correction]
@ 2022-10-31 16:23 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2022-10-31 16:23 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Uwe Brauer writes:
> %% does not work for auctex, so I think I try @@, I hope it does not collide with anything fancy......
You can also set a text string, like _ftags_, and to hide it when you're
in Dired, add a function to the dired-mode-hook that displays an overlay
instead of that string, with some fancy unicode symbol separated by
spaces. Something like this:
(defun overlay-dired-filetags ()
(save-excursion
(goto-char (point-min))
(while
(re-search-forward "\\(_ftag_\\)" nil t)
(let
((ov (make-overlay (match-beginning 1) (match-end 1)))
(tag (propertize " ⚜ " 'face 'bold)))
(overlay-put ov 'overlay-tag t)
(overlay-put ov 'display tag)))))
However, in large directories I don't know how that would affect
performance.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc)
@ 2024-02-01 17:44 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2024-02-01 17:44 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: Max Nikulin, emacs-orgmode
Ihor Radchenko writes:
> Max Nikulin <manikulin@gmail.com> writes:
>
>> On 26/01/2024 19:53, Ihor Radchenko wrote:
>>> So, I am leaning towards reverting that commit - that will allow things
>>> like
>>>
>>> #+TITLE: This is a test title[fn::This is test]
>>
>> I hope, document metadata will be generated with stripped footnotes.
>
> This is a good point.
>
> For now, [fn::This is test], when passed to exporters, is simply treated
> as plain text.
>
> If we change the parser nesting rules, Org will pass footnote-reference
> objects instead.
>
> Then, in a number of parsers, if something like
> (org-export-data (plist-get info :title) info) or
> (org-export-data author info)
> is used, footnotes may break export because metadata fields often have
> special rules about markup that is allowed inside.
>
> In particular, ox-odt will be broken; ox-latex will be broken.
>
> Of course, we can adjust built-in backends to take into account the new
> parsing rules, but we have no control over the third-party backends.
>
> On the other hand, when user exports something like
>
> #+AUTHOR: John Doe[fn::935 Pennsylvania Avenue, NW Washington, D.C. 20535-0001]
> it is probably not exported as expected anyway.
How about using dedicated keywords? Something like:
#+FN_AUTHOR: footnote text
#+FN_TITLE: footnote text
I give these two examples because they are the two places where a
footnote of this type is expected. I know: it's ugly and corseted (what
to do if a title has more than one footnote or an "inner" footnote?).
But I suppose it would be safe for a basic case, since it would only be
necessary to modify org-latex-template, org-odt-template, etc., without
risk of unexpected results.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [PATCH] ox-latex.el: Unify in one single list Babel and Polyglossia languages alists
@ 2022-07-21 15:39 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-07-21 15:39 UTC (permalink / raw)
To: Max Nikulin; +Cc: orgmode, Ihor Radchenko
Max Nikulin writes:
> The commented out command is a kind a hack, but I consider it as
> acceptable for advanced users who have custom classes or who need to
> compile document without babel (or polyglossia) for some reason.
Yes, I think the ability to control this per document is also necessary.
I would vote for a custom variable, at the global level (I agree with
the options you suggest) and at the document level, to economize,
perhaps this would be enough to avoid the code of both babel and
polyglossia:
#+latex_header: NOLANG
(BTW, in the current version of my patch I'm afraid the commit message
is malformed, and there's an asterisk where it shouldn't be, apologies).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Information about all LaTeX packages in an Org document
@ 2022-10-10 15:19 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-10-10 15:19 UTC (permalink / raw)
To: orgmode
Hi all,
For my personal use I have created an Org document with the
bibliographic information of all the LaTeX packages currently in CTAN. I
have imported the data using org-bibtex-import-from-file. And I have
applied some further edits. The original data source is at:
https://www.ctan.org/pkg/ctan-bibdata
I think that in Org format this will be useful for me to access the
fields (properties) or manipulate them in various ways. In case someone
finds it useful too, it can be downloaded from here:
https://cloud.disroot.org/s/Qc9NLgPjXRJ29ya
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [PATCH] [BUG] Bad fontification in full displayed links
@ 2021-07-10 12:12 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-07-10 12:12 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
[-- Attachment #1: Type: text/plain, Size: 286 bytes --]
Hi Ihor,
Ihor Radchenko writes:
> Why not just (add-face-text-property start end face-property)?
You are right, I think that solution is much simpler. I attach a
new patch and I have included your name in the commit message, for the
suggestion. Thanks!
Best regards,
Juan Manuel
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org.el-prevent-partial-fontification-when-a-link-is-.patch --]
[-- Type: text/x-patch, Size: 1114 bytes --]
From 0e31ba4ce76e436712285b163b8595b0a973da94 Mon Sep 17 00:00:00 2001
From: Juan Manuel Macias <maciaschain@posteo.net>
Date: Sat, 10 Jul 2021 13:53:44 +0200
Subject: [PATCH] org.el: prevent partial fontification when a link is
displayed full
* lisp/org.el (org-activate-links): apply `face-property' variable in
other cases when handle invisible parts in bracket
links: `(add-face-text-property start end face-property)' suggestion
from Ihor Radchenko
---
lisp/org.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/org.el b/lisp/org.el
index ffcc5945d..eca12a5e7 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -5228,7 +5228,7 @@ This includes angle, plain, and bracket links."
'org-link))
properties)))
(add-text-properties start visible-start hidden)
- (add-face-text-property visible-start visible-end face-property)
+ (add-face-text-property start end face-property)
(add-text-properties visible-start visible-end properties)
(add-text-properties visible-end end hidden)
(org-rear-nonsticky-at visible-start)
--
2.32.0
^ permalink raw reply related [relevance 10%]
* Re: [PATCH] A proposal to add LaTeX attributes to verse blocks
@ 2021-01-03 13:07 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-01-03 13:07 UTC (permalink / raw)
To: TEC; +Cc: orgmode
Hi Timothy,
TEC <tecosaur@gmail.com> writes:
> Hi Juan,
>
> Thanks for your patch.
>
> This looks like a fairly sensible addition. Two comments from me:
>
> 1. I'm not sure that "options" is a good name for arbitrary LaTeX which
> is included inside the verse block. Perhaps something like "insert"
> or "include", etc. may be a better fit.
> 2. It's considered generally nice to document features like this :) The
> two documents which I'd think to note this in are ORG-NEWS and the
> manual (docs/manual.org).
Thank you very much for your response and your comments.
I agree to name "Insert, include, etc." the attribute to include
arbitrary LaTeX code, better than "options".
Of course, I can add the necessary documentation to the files you tell
me. As I am new to submitting patches, I don't really know how to
proceed: do I have to send you the new version of the patch, with the
documentation? Should I send a new email with all of it to this list?
Best regards,
Juan Manuel
> All the best,
>
> Timothy.
>
^ permalink raw reply [relevance 10%]
* Re: literate programming, development log -- ideas? (ominbus reply)
@ 2021-06-11 14:30 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-11 14:30 UTC (permalink / raw)
To: Samuel Banya; +Cc: orgmode
Samuel Banya writes:
> I'm okay with git repos for dot files or some kind of programming
> project but yeah, I've been debating something else for an org based
> repo cause I too have almost had my 'life.org' be completely destroyed
> with a merge event.
I have all my everyday Org documents in a Nextcloud folder, but only
because I work between the desktop PC and the laptop. I sync using a
script with nextcloud-cmd, not via the Nextcloud app, which I find it
somewhat intrusive. And with another script I do every week a backup of
that folder to a git repo. But this repo is secondary and is only for
keep some backups (I also keep a weekly backup of Elpa folders ---last
versions--- there, in case some update breaks something).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: leading superscript on a line for ODT export
@ 2022-03-16 13:12 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-03-16 13:12 UTC (permalink / raw)
To: Eric S Fraga; +Cc: orgmode
Eric S Fraga writes:
> Yes, I guess this is the best way to do this. Thank you in particular
> for the xml code for odt which would have taken me some time to figure
> out!
When I need to find out some xml markup in odt or docx I open the
document from Dired with view-mode, and run C-c C-c
(doc-view-toggle-display) to access the .xml files (these documents are
nothing more than zipped folders with xml files inside). This is also
useful for making (small) modifications to an odt or docx document. So,
yeah, in Emacs we can edit a Word or Libreoffice document :-D.
A screenshot: https://i.imgur.com/XRcGwse.png
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [BUG] Underlined text in parentheses is not exported correctly
@ 2021-12-31 11:31 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-12-31 11:31 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko writes:
> I am not sure if it is an actual issue.
>
> Note that (_u can be interpreted as a subscript.
> Org prioritises subscript over underline.
>
> Looking at the code:
>
> (?_ (or (and (memq 'subscript restriction)
> (org-element-subscript-parser))
> (and (memq 'underline restriction)
> (org-element-underline-parser))))
>
> The priority appears to be intentional.
I see. But then the compatibility with the rest of the emphasis is
broken. I mean, the user would expect things like (_underline_) will be
exported as (\uline{underline}), in the same way that (/emphasis/) is
exported as (\emph{emphasis}). I would say there is a slight
inconsistency in the syntax here.
Anyway, in my case I have solved it by always forcing the
super/sub-scripts with brackets overriding `org-element-subscript-parser'
(I never use them without brackets), as I mentioned in my previous
message.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Format babel code block for export?
@ 2021-06-02 9:42 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-02 9:42 UTC (permalink / raw)
To: Galaxy Being; +Cc: orgmode
Hi Lawrence,
You can use multiple blocks and noweb reference syntax
(https://orgmode.org/manual/Noweb-Reference-Syntax.html):
#+NAME:block1
#+begin_src haskell :results silent :exports none
:{
#+end_src
#+NAME:block2
#+begin_src haskell :results silent :exports none
maximum'' :: (Ord a) => [a] -> a
maximum'' = foldl1 (\x acc -> if x > acc then x else acc)
#+end_src
#+NAME:block3
#+begin_src haskell :results silent :exports none
:}
#+end_src
# for export
#+begin_src haskell :noweb yes :exports code
<<block2>>
#+end_src
# for evaluation
#+begin_src haskell :noweb yes :results silent :exports none
<<block1>>
<<block2>>
<<block3>>
#+end_src
Best regards,
Juan Manuel
Galaxy Being <borgauf@gmail.com> writes:
> I have this
>
> #+begin_src haskell :results silent :exports code
> :{
> maximum'' :: (Ord a) => [a] -> a
> maximum'' = foldl1 (\x acc -> if x > acc then x else acc)
> :}
> #+end_src
>
> but on export to HTML (or LaTex) I'd like to suppress the :{ and :} to
> just show the code
>
> maximum'' :: (Ord a) => [a] -> a
> maximum'' = foldl1 (\x acc -> if x > acc then x else acc)
>
> Also, this
>
> #+begin_src haskell :results verbatim :exports both
> maximum'' [1,3,5,2,4]
> #+end_src
>
> I'd like to export the code part with a > REPL prompt included, e.g.,
>
>> maximum'' [1,3,5,2,4]
>
> I once saw some similar tricks, but I've searched and searched and
> can't find them again. There's probably other html export formatting
> I'd like too, but if anyone can point me to that mystery doc I'd
> appreciate it.
>
> ⨽
> Lawrence Bottorff
> Grand Marais, MN, USA
> borgauf@gmail.com
>
^ permalink raw reply [relevance 10%]
* Re: whitespace in org source files
@ 2021-11-13 12:57 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-11-13 12:57 UTC (permalink / raw)
To: excalamus; +Cc: Tim Cross, orgmode
Hi,
excalamus--- via "General discussions about Org-mode." writes:
> I've not used the email contribution style before and have had
> whitespace issues in the past with GitHub PRs. I typically run
> whitespace-cleanup with the before-save-hook which changes tabs to
> spaces.
I agree with Tim that running whitespace-cleanup is usually a bad idea
within a Git repository. I also have, like you, whitespace-cleanup
hooked to before-save-hook, like a relic of my first Emacs setups. In
case it helps, I have added to my init this function:
(defun my-whitespace-cleanup-no-git ()
(let ((buf (buffer-file-name)))
(when (not (vc-git-responsible-p buf))
(whitespace-cleanup))))
and then:
(add-hook 'before-save-hook 'my-whitespace-cleanup-no-git)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Are 'placement' and 'float' "obsolete terms" in inline images export
@ 2023-10-23 19:00 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2023-10-23 19:00 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko writes:
>> My suggestion is to add a :environment attribute next to another
>> :environment-options attr (or something like that, to introduce any
>> arbitrary LaTeX code). A LaTeX image can be enclosed in many environment
>> types, float or non-float.
>
> As I said above, I feel that :environment term will be overloaded then.
> What about :wrap?
I like :wrap. What's more, remembering that old thread where
some questions about code before/after the image were discussed,
what if the expected value of :wrap were a kind of template? This would
allow code to be placed before and/or after (not just an environment)
the image, always within the float environment, if it exists. Something
like this:
#+ATTR_LaTeX: :float nil :wrap \begin{minipage}[b]{10pc}\small\n%s\n\end{minipage}
#+CAPTION: caption
[[file:foo.png]]
Thus :caption with value nil does not add any higher float environment
and would enclose (always within the template) the value of #+CAPTION as
\captionof{figure}{caption}. Of course, with a float environment
declared, :wrap can still be used. An internal environment is unlikely
(I can't think of any use case right now), but you can add arbitrary
code like \captionsetup{} or \ContinuedFloat, which should always go
inside the float environment.
The result of the previous example could also be obtained with:
#+ATTR_LaTeX: :float minipage :placement [b]{10pc} :caption \captionof{figure}{caption}
[[file:foo.png]]
I don't know if it would be appropriate to explain in the Manual that
doing so would not be... "correct"? I don't know if there is any term in
programming to designate these situations which, without being bugs, are
functionalities not consciously sought...
>> ... However, :float can still be useful for
>> certain combinations. For example, a minipage environment cannot include
>> a caption (it produces an error of the type "LaTeX Error: \caption
>> outside float").
>
> Do we know in advance which environments support \caption and which not?
> I feel that we may handle this programmatically without creating an array
> of almost-identical attributes.
I like the idea, but unfortunately, apart from the known float
environments, there are those that a user can define using the \newfloat
command from the float package.
--
Juan Manuel Macías
https://juanmanuelmacias.com
https://lunotipia.juanmanuelmacias.com
https://gnutas.juanmanuelmacias.com
^ permalink raw reply [relevance 10%]
* Re: [DISCUSSION] Re-design of inlinetasks
@ 2023-08-26 19:19 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2023-08-26 19:19 UTC (permalink / raw)
To: Ihor Radchenko
Cc: Bastien Guerry, Fraga, Eric, Samuel Wales, Max Nikulin,
emacs-orgmode@gnu.org
Ihor Radchenko writes:
> In other words, it is not the section itself, but other
> headline/inlinetask features, like todo keywords, tags, planning. Right?
No, it is the section itself (or the concept of "section", with its toys
in Org, of course) that is important to me in this case. I am not
emphasizing so much how or in which way an element can be exported, but
what (semantic) role that element plays in the logical structure of an
Org document. To get a little philosophical, the Org document (where I
work and write) would be the idea, and the export to any format a
possible concrete realization. I mean, I find it comfortable and
productive to view an Org document as agnostic of any format. This use
of inlinetasks that I'm discussing here occurred to me a long time ago
because if I stop to think about an untitled, detached section of the
level hierarchy, this Org element is a perfect candidate. It is true
that you can use a special block, or another element (org is very
versatile, and supports role swapping between elements), but if I have
to think of a logical candidate, inlinetasks are the closest to that
concept. If inlinetasks didn't exist, I'd probably use special blocks
for that purpose. When I'm writing inside Org I'm not thinking about the
export (at least not simultaneously), that is, about the format; I think
more of the structure of the document, as something abstract.
--
Juan Manuel Macías
https://juanmanuelmacias.com
https://lunotipia.juanmanuelmacias.com
https://gnutas.juanmanuelmacias.com
^ permalink raw reply [relevance 10%]
* Re: [patch] Fixes and improvements in org-latex-language-alist
@ 2023-09-12 18:12 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2023-09-12 18:12 UTC (permalink / raw)
To: Max Nikulin; +Cc: emacs-orgmode, Ihor Radchenko
Max Nikulin writes:
>>> Every piece of code accessing this public constant must implement
>>> fallback from e.g. "de-ch" (or de_CH) to "de". Or to "en" for an
>>> unsupported language.
>> Not necessarily. I mostly thought about some unconventional code
>> that
>> uses the constant for some reason unexpected to us. We do not want to
>> break that.
>
> My point is that direct usage of `org-latex-language-alist' should be
> discouraged.
I understand that org-latex-language-alist is a temporary patch waiting
for something better, and is very dependent on
org-latex-guess-babel-language and
org-latex-guess-polyglossia-language[1], two functions that (IMHO)
should be made obsolete in the future. Keep in mind that the old
org-latex-babel-language-alist was more focused on the old babel ldf
files, which is a limited number of languages. Polyglossia also has a
rather limited number of supported languages. The ini files system is
more extensive and more flexible. One can even define new "virtual"
languages using \babelprovide, or write new custom ini files. With this
scenario a closed list like org-latex-language-alist doesn't make much
sense. I actually think that there would be no need for any ad hoc list
of this type for latex, and everything should be delegated to a global
language name translation system like the one Ihor is developing. I
think that would be the first stone to build native Org multilingual
support.
[1] I think also that in this function there was an unhappy decision:
using a syntax that is not from polyglossia but from babel leaves the
user with little freedom of action, since polyglossia has more 'keyval'
options, not only language variants. For example, this (real polyglossia
code):
\usepackage{polyglossia}
\setmainlanguage{spanish}
\setotherlanguage[numerals=arabic]{chinese}
cannot be translated from (fake polyglossia code):
#+language: es
#+LaTeX_Header: \usepackage[chinese,AUTO]{polyglossia}
--
Juan Manuel Macías
https://juanmanuelmacias.com
https://lunotipia.juanmanuelmacias.com
https://gnutas.juanmanuelmacias.com
^ permalink raw reply [relevance 10%]
* Re: return column from table as a column
@ 2021-08-13 17:12 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-08-13 17:12 UTC (permalink / raw)
To: Roger Mason; +Cc: orgmode
Hello Roger,
Roger Mason writes:
> Thank you, I think I may be able to get this to work.
You're welcome. Just a minor fix: although the code works fine,
naturally the asterisk in `let' was unnecessary. This is a new version
with the code explained, in case you find it useful:
#+begin_src emacs-lisp :var data=s1 col=3
(let* (
;; return a list from elemens in column number `col'
(list-from-column (mapcar (lambda (r) (format "%s" (nth col r))) data))
;; make a list of lists = a new table that contains one single column
(new-table (mapcar 'list list-from-column)))
new-table)
#+end_src
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [patch] ox-latex.el: fix blank lines behavior in verse block
@ 2023-08-10 10:39 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2023-08-10 10:39 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko writes:
> Well. Technically, we already warn users that the blank lines are
> preserved in the verse blocks:
>
> 12.1 Paragraphs
> ===============
>
> Paragraphs are separated by at least one empty line. If you need to
> enforce a line break within a paragraph, use ‘\\’ at the end of a line.
>
> To preserve the line breaks, indentation and blank lines in a region,
> but otherwise use normal formatting, you can use this construct, which
> can also be used to format poetry.
>
>
> #+BEGIN_VERSE
> Great clouds overhead
> Tiny black birds rise and fall
> Snow covers Emacs
>
> ---AlexSchroeder
> #+END_VERSE
>
> So, I now think that while extra cleanups might be OK for ox-latex, we
> may not want to ignore empty lines universally in all the verse blocks.
hmm, I don't know if phrased like that (as read in the documentation)
it's clear enough that the empty lines before and after the content are
also preserved. I would understand not, but it could also be a habit that
I inherited from LaTeX: I usually leave a blank line between the
#+begin/#+end directives and the content because it makes it easier for
me to read. I don't know if it is a widespread habit among other
users...
Anyway, I don't mind leaving things as they are in the other backends,
but in the case of LaTeX, with my patch modifications, it would be
necessary to remove the blank lines before and after the content.
Otherwise it would produce something like:
\begin{verse}
\\[0pt]
\\[0pt]
\\[0pt]
\\[0pt]
\\[0pt]
lorem ipsum dolor
\end{verse}
which would return the error "There's no line here to end".
Also, the LaTeX 'verse' environment has its own syntax for vertical
spaces. It is not necessary to put an explicit \vspace just to separate
stanzas.
... In any case, the fact that the verse block can also be used to
literally export line breaks and horizontal/vertical spaces is
interesting. Something occurred to me that I don't know if it's a bit
foolhardy: how about a LaTeX attribute ':literal t'? If used, it would
not export to a verse environment (specialized in poetry) but to normal
text, without environment, but with line breaks and horizontal and
vertical spacing preserved... wdyt?
--
Juan Manuel Macías
https://juanmanuelmacias.com
https://lunotipia.juanmanuelmacias.com
https://gnutas.juanmanuelmacias.com
^ permalink raw reply [relevance 10%]
* Re: LaTeX export: when is it more useful to use LuaTeX instead of pdfTeX?
@ 2022-07-10 19:31 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-07-10 19:31 UTC (permalink / raw)
To: Tim Cross
Cc: Maxim Nikulin, Matt Huszagh, Thomas S. Dye, Dominik Schrempf,
Ihor Radchenko, Greg Minshall, orgmode
Tim Cross writes:
> Thanks Juan. It will be fairly trivial to compile the information you
> have provided into a basic org document which I can then add to org. If
> on the other hand you would prefer to write it up, all I need is an org
> document which is based on the (current) org 'worg' template, which is
> very simple i.e.
>
> #+:begin_src org
>
> #+TITLE: [No title for now, please update]
> #+AUTHOR: Worg people
>
> #+OPTIONS: H:3 num:nil toc:t \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
> #+STARTUP: align fold nodlcheck hidestars oddeven lognotestate
>
> #+SEQ_TODO: TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
>
> #+TAGS: Write(w) Update(u) Fix(f) Check(c)
> #+LANGUAGE: en
>
> #+PRIORITIES: A C B
> #+CATEGORY: worg
>
> #+HTML_LINK_UP: index.html
> #+HTML_LINK_HOME: https://orgmode.org/worg/
>
> # This file is released by its authors and contributors under the GNU
> # Free Documentation license v1.3 or later, code examples are released
> # under the GNU General Public License v3 or later.
>
> # This file is the default header for new Org files in Worg. Feel free
> # to tailor it to your needs.
>
> #+end_src
Thanks so much for all the pointers, Tim.
I can collect and clean up (and possibly expand) all the information
I've put in this thread and make an Org document with this template. I
agree with Ihor that the template would be a great addition to Org-Mode.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [proof of concept] inline language blocks
@ 2024-02-21 23:02 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2024-02-21 23:02 UTC (permalink / raw)
To: Samuel Wales; +Cc: Ihor Radchenko, orgmode
Samuel Wales writes:
> for language feature, there are various options here which range from e.g.
> :fr{some text in French}
>
> being expressed as
>
> $[lang :fr "bonjour"]
>
To expand a little more... Another problem I see in your example is
nesting. In my proposal, the blocks can be nested:
:fr{text in French and :it{text in Italian}}
But I would find this difficult to read:
$[lang :fr "text in French and $[lang :it "text in italian"]"]
On the other hand, the structure that I have chosen is in part inspired
by the inline code block, which is the only case of "inline block" that
we have in Org.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: org-attach a directory?
@ 2021-06-10 14:01 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-10 14:01 UTC (permalink / raw)
To: Christian Barthel, John Kitchin, Ihor Radchenko; +Cc: orgmode
This only works when you create the attach folder manually, but not when
you want org-attach to generate the attach directory for the current
node.
If I have to stay with a workaround that covers many scenarios, I would
stay with Ihor's snippet, which seems to me simpler than the patch that
I suggested before, and you don't need to define new attach
commands/methods. I would vote for a patch in that direction (Ihor's
code).
Best regards,
Juan Manuel
Christian Barthel writes:
> On Thu, Jun 10 2021, Ypo wrote:
>
>> C-c C-a
>>
>> s
>>
>> (not "S" like in the video, but "s")
>
> Thanks, that is an interesting workaround:
> Setting the directory twice and using the copy/delete action
> accordingly.
>
> Does anyone know if there is a workaround to attach a file and
> delete the old one (or move the file) or do I need to write a
> small elisp function for that?
^ permalink raw reply [relevance 10%]
* Re: Error opening an .org file
@ 2022-10-27 17:21 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-10-27 17:21 UTC (permalink / raw)
To: Renato Pontefice; +Cc: emacs-orgmode
Renato Pontefice writes:
> I’ve edited and commented all the lines of it. And The error
> persist. So (was you told)maybe the error is not of init.el
> But I’m unable to run emacs from termnal.
> How can I do?
> I’m in Mac osx 12.6.1 where do I can find emacs?
Renato, I'm not a Mac user, but I imagine it will be like any other
Unix: you have to launch a terminal from your desktop (i guess there
will be in macos an app called "terminal" or something like that), and
once inside the terminal, just type:
emacs --debug-init
and press enter. Emacs (GUI) will open and you should pay attention to
the error messages that Emacs will show you. That will give you a clue
as to where the error is in your Emacs startup.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Org and multimedia (tips?)
@ 2022-03-19 11:13 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-03-19 11:13 UTC (permalink / raw)
To: Max Nikulin; +Cc: orgmode
Max Nikulin writes:
> org-web-tools is an interesting project, but if you have access to
> files it should be easier to extract all meta information directly
> using e.g.
>
> exiftool -json file.mp3
>
> or another tool suitable to particular format. It seems emms has
> interface to various tools.
>
> P.S. You may try to adapt common LISP implementation of ID3 parser
> https://gigamonkeys.com/book/practical-an-id3-parser.html
Maxim, thanks a lot for the ideas. I take note. The reason for using
org-web-tools is that the web page that GNUMP3d serves is extremely
simple, with an alphabetical list of artists, titles, and links to the
.m3u to stream. The list is easily reusable in Org. In the end I managed
to write a function to create in each node a property drawer with
album title, date and artist, accessing each m3u and obtaining the
information with ffprobe (screenshot: https://i.imgur.com/1ALe4Ah.png).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Org + git branches for derived files
@ 2021-08-13 20:53 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-08-13 20:53 UTC (permalink / raw)
To: Ken Mankoff; +Cc: orgmode
Hi Ken,
Ken Mankoff writes:
> I'd like to keep derivative products (the LaTeX output, the final PDF,
> etc.) available in Git, but not commit those changes each time I
> change the Org file. Perhaps git-annex as appropriate for this, but
> seems over-kill.
>
> Is there some way to mostly-seamlessly commit the LaTeX and/or PDF
> and/or other files to their own git branches but in a way that
> overwrites the history of that branch, so that a small Org file that
> generates a big binary PDF does not pollute the git tree?
There are probably better solutions, but maybe this could help you:
use org-publish (which also works when the output is LaTeX/PDF, and
not only with HTML). See https://orgmode.org/manual/Publishing.html
You should have to define a new publishing project and declare a
directory for the PDFs derivatives, applying a value to
:publishing-directory, and configure in this directory a second git
repository, only for PDFs. The value of :publishing-function keyword
should be `org-latex-publish-to-pdf'.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* [PATCH] ox.el: fix spanish translation for `footnotes'
@ 2021-08-03 10:47 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-08-03 10:47 UTC (permalink / raw)
To: orgmode
[-- Attachment #1: Type: text/plain, Size: 267 bytes --]
Hi,
The Spanish translation for "Footnotes" in `org-export-dictionary' is
"Nota al pie de página" ("Nota"[="Note"], in the singular form). I think
it would be more correct "Notas", in the plural form. Attached a small
patch.
Best regards,
Juan Manuel
[-- Attachment #2: 0001-ox.el-fix-spanish-translation-for-footnotes.patch --]
[-- Type: text/x-patch, Size: 1063 bytes --]
From 4109c6f2bc38d56b0a67c482afc3feeddfcf3084 Mon Sep 17 00:00:00 2001
From: Juan Manuel Macias <maciaschain@posteo.net>
Date: Tue, 3 Aug 2021 12:31:02 +0200
Subject: [PATCH] ox.el: fix spanish translation for `footnotes'
* lisp/ox.el (org-export-dictionary): tiny fix in spanish translation (plural instead of singular)
---
lisp/ox.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/ox.el b/lisp/ox.el
index 16b87a7ed..418c680b0 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -5928,7 +5928,7 @@ them."
("da" :default "Fodnoter")
("de" :html "Fußnoten" :default "Fußnoten")
("eo" :default "Piednotoj")
- ("es" :ascii "Nota al pie de pagina" :html "Nota al pie de página" :default "Nota al pie de página")
+ ("es" :ascii "Notas al pie de pagina" :html "Notas al pie de página" :default "Notas al pie de página")
("et" :html "Allmärkused" :utf-8 "Allmärkused")
("fi" :default "Alaviitteet")
("fr" :default "Notes de bas de page")
--
2.32.0
^ permalink raw reply related [relevance 10%]
* Re: [correction]
@ 2022-11-01 13:52 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-11-01 13:52 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Uwe Brauer writes:
> One, hopefully, last thing in helm-mini, how can I select and visit a
> certain file? I looked around but C-j says view file (recent) but I
> cannot edit that file....
The selected candidates in helm have one main action, which in
helm-locate and so on is usually to visit the buffer or file. The action
is associated with enter or C-m. But you can modify the helm-map to your
liking.
And, in addition to the main action, you have a menu of (very useful)
secondary actions, which you can access by pressing tab on the selected
candidate. Each helm source has its own secondary actions. And you can
also define more actions and add them.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: #+include and org-export-before-processing-hook
@ 2020-12-13 17:26 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2020-12-13 17:26 UTC (permalink / raw)
To: Eric S Fraga; +Cc: orgmode
Hello,
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Hello,
>
> I have a particular function that I want to invoke when exporting an org
> file. This works just fine, adding this function to the
> org-export-before-processing-hook, for simple org files. However, if I
> have an org file which uses #+include: to include other org files, it
> seems like the processing doesn't happen on included files.
I have the same problem with a function that I wrote to not export
certain footnotes, and to date I have not been able to fix it. According
to the `org-export-before-processing-hook' docstring:
" *This is run before include keywords and macros are expanded*
and Babel code blocks executed, on a copy of the original buffer
being exported. Visibility and narrowing are preserved. Point
is at the beginning of the buffer.
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [patch] ox-latex.el: fix blank lines behavior in verse block
@ 2023-08-15 11:50 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2023-08-15 11:50 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko writes:
> Thanks!
> I tested the patch with
>
> #+attr_latex: :literal t
>
> #+begin_verse
>
> This is just a test.
> ASF.
>
> #+end_verse
>
>
> and then with
>
> #+attr_latex: :literal t
>
> #+begin_verse
>
> This is just a test.
>
> ASF.
>
> #+end_verse
>
> The output is not different, which it should be, AFAIU. Am I missing something?
I have tried your examples and I think both give the expected result.
Look at this screenshot:
https://i.imgur.com/ofl8Z9f.png
Note one important thing: the only horizontal spaces that are exported
"literally" (ie with \hspace...) are the ones at the beginning of the
line. This is the same as the old behavior, and works with both :literal
and the verse environment. Spaces between words are not exported. Well,
they are exported, but not as \hspace, so LaTeX resolves one or more
space to a single space. It could be an interesting feature that spaces
between words are also preserved, but none of the other backends do
that... Actually the :literal attribute has effect only on blank lines.
(Anyway, I think that without exporting the spaces between words, the
:literal attribute is a bit incomplete. But if those spaces are
exported, it would break compatibility with the other backends. The
horizontal space before the line makes sense for verses, because these
can often be indented arbitrarily in a poem. The other possibility is
that the :literal attribute also exports to a verse environment. In that
case, it would not break compatibility [the verse block in LaTeX would
just have two "modes": one more coherent with the syntax of the verse
environment and another one more similar to the behavior of the rest of
the backends and the "old" verse block behavior in LaTeX export]).
--
Juan Manuel Macías
https://juanmanuelmacias.com
https://lunotipia.juanmanuelmacias.com
https://gnutas.juanmanuelmacias.com
^ permalink raw reply [relevance 10%]
* Re: [proof of concept] inline language blocks
@ 2024-02-21 10:57 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2024-02-21 10:57 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko writes:
> Juan Manuel Macías <maciaschain@posteo.net> writes:
>
>> I'm dedicating a local branch to developing this proof of concept and
>> testing it in my workflow, so far with good results. The basic idea is
>> to provide Org with multilingual features and various methods for
>> selecting languages.
>>
>> The inline-language-block is intended for small segments of text in a
>> language other than the main language. They can span several lines but
>> not more than a paragraph. They can be used for in-line textual quotes,
>> glosses, etc. They are constructions equivalent to, for example, LaTeX
>> \foreignlanguage{french}{text} or HTML <span lang=fr>text</span>.
>>
>> I have thought of a syntax that is as least intrusive as possible, so as
>> not to make reading uncomfortable. I have tried the following:
>>
>> :fr{some text in French} :it{some text in Italian} :la{some text in Latin}
>>
>> You can also use a literal term instead of a language code:
>>
>> :klingon!{some text in Klingon}
>>
>> The blocks can be nested:
>>
>> :klingon!{Some text in Klingon with :it{some text in Italian}}
>>
>> And they may include other elements:
>>
>> :el{Some text in Greek with a {{{macro}}} and a [[link]]}
>
> This is a good idea, although it would be better to make this new markup
> element within the framework of more general inline special block we
> discussed in the past: https://list.orgmode.org/orgmode/87a6b8pbhg.fsf@posteo.net/
Fun fact: the local branch is called inline-special-block, because I
originally had that idea in mind when I created it. Then, halfway
through, I doubted whether it wouldn't be better to have a specific
inline language selector, whose use would be as direct as an emphasis
mark. So in the branch there is also a "proto"-inline-special-block with
similar syntax: &foo{}.
I opted for the -language-block version because, as I said, its use is
very 'direct' and covers a common need to segment multilingual text
within the paragraph.
I think at the time we also discussed whether or not it would be a good
idea to provide the inline special blocks with options and attributes,
like their older brothers. And how to do it. My biggest concern here is
the (let's say) latexification of the paragraph. I mean, one of the
great things about Org versus heavier markup like LaTeX is that when org
wants to be verbose it uses dedicated lines, but usually keeps the
paragraphs clean and readable. I think that any element inside the
paragraph should tend to be as "transparent" as simple emphasis marks.
I remember that there was also discussion about puting the options
outside the paragraph, using some type of identifier. It doesn't seem
like a bad idea to me, but I think it adds an extra complication for the
user. It would be very tedious for me to write like this (even more
tedious than writing in LaTeX).
Best regards,
--
Juan Manuel Macías
^ permalink raw reply [relevance 10%]
* Re: [Patch] to correctly sort the items with emphasis marks in a list
@ 2021-04-13 14:16 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-13 14:16 UTC (permalink / raw)
To: Samuel Wales; +Cc: orgmode
Hi Samuel,
Samuel Wales writes:
> probably not a relevant non-confirmation but in recent maint, my config:
>
> - a
> - /a/
> - b
Thanks for trying. I've uploaded this screencast with a minimal Emacs on
a virtual machine:
https://gnutas.juanmanuelmacias.com/images/org-sort-issue-2021-04-13_15.44.52.mp4
and, as you can see, in my case `org-sort-list' can not sort the list
correctly. Maybe it's something related to locales (??), but the only
thing that I can confirm is that if I remove those spaces in
`org-sort-remove-invisible', the list is then sorted correctly.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [possible patch] Remove the '\\[0pt]' string from the last line of a verse block in LaTeX export
@ 2024-01-19 17:28 10% ` Juan Manuel Macías
1 sibling, 1 reply; 200+ results
From: Juan Manuel Macías @ 2024-01-19 17:28 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode, Max Nikulin
Ihor Radchenko writes:
> This turned out to be a lot easier than I thought.
> See the attached patch.
>
>>> \command
>>> [unrelated text]
>>>
>>> If there are, we may actually want to consider pandoc's approach
>>> seriously.
>>
>> In principle, any environment that takes an optional argument in a
>> "dangerous" position. Just do a simple test. Something like this:
>>
>> #+begin_figure
>> [lorem] ipsum
>> #+end_figure
>>
>> will throw an error like ''LaTeX Error: Unknown float option...''
>>
>> Of course, putting an empty line after #+begin... usually solves it. But
>> the user may not know it.
>>
>> There are also a number of commands with an optional argument. For
>> example \pagebreak. Something like this will give an error:
>>
>> lorem @@latex:\pagebreak@@ [ipsum]
>>
>> \item is another typical example, but in this case org adds \relax.
>
> With the patch, I am getting the following:
>
> * This is test
> lorem @@latex:\pagebreak@@ [ipsum]
>
> #+begin_figure
> [lorem] figure
> #+end_figure
>
> | [foo] | 2 |
> | [bar] | 3 |
>
> - [bax]
> - [aur]
>
> exports to
>
> lorem \pagebreak {[}ipsum]
>
> \begin{figure}
> {[}lorem] figure
> \end{figure}
>
> \begin{center}
> \begin{tabular}{lr}
> {[}foo] & 2\\[0pt]
> {[}bar] & 3\\[0pt]
> \end{tabular}
> \end{center}
>
> \begin{itemize}
> \item {[}bax]
> \item {[}aur]
> \end{itemize}
Great! Simple and effective. And more surgical than pandoc's global
solution. But now a question arises... Your code clearly solves the
problem that led to the declaration of org-latex-line-break-safe,
without foreseeing any unwanted effects, since it is the solution that
is usually recommended from LaTeX. So, if this code is included in Org,
what is the future of org-latex-line-break-safe?
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* An academic journal entirely made in Org-Mode
@ 2024-01-29 20:03 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2024-01-29 20:03 UTC (permalink / raw)
To: orgmode
Hi,
In last December, issue 23 of the "Revista de Estudios Latinos" (Journal
of Latin Studies) was published, sponsored by the Spanish Society of
Latin Studies. It is designed and produced by me using Org-Mode,
Org-Publish and LuaTeX. If anyone is interested in the code I used for
specific aspects of the publication, I can share it here :-).
Link to the journal in PDF version:
https://recyt.fecyt.es/index.php/rel/issue/view/4327/948
And a screenshot of the making-off:
https://i.imgur.com/lkwIOGA.png
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* An academic journal made entirely in Org-Mode
@ 2024-01-29 20:05 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2024-01-29 20:05 UTC (permalink / raw)
To: orgmode
Hi,
In last December, issue 23 of the "Revista de Estudios Latinos" (Journal
of Latin Studies) was published, sponsored by the Spanish Society of
Latin Studies. It is designed and produced by me using Org-Mode,
Org-Publish and LuaTeX. If anyone is interested in the code I used for
specific aspects of the publication, I can share it here :-).
Link to the journal in PDF version:
https://recyt.fecyt.es/index.php/rel/issue/view/4327/948
And a screenshot of the making-off:
https://i.imgur.com/lkwIOGA.png
Best regards,
Juan Manuel
--
^ permalink raw reply [relevance 10%]
* Re: [Tip] Popup-menu with several actions for a link
@ 2023-08-20 10:13 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2023-08-20 10:13 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko writes:
>> ... Also, I don't usually use the mouse
>> much (actually I only use it in Gimp and the like) and the combination
>> of popup.el with hyperbole is more comfortable and keyboard-centric for
>> me.
>
> By default, context menu is bound to S-<F10>. Who cares about mouse XD
Oh I see. Very interesting. But I have seen that, at least by default,
there is no autocomplete feature. What I like about popup.el is, in
addition to autocompletion, the ability to easily create menus for
anything. Some time ago I defined a popup-menu[1] that shows me all the
header levels from where I am to the first one, defaulting to the
current level. It helps me situate myself in deep levels (other options
like imenu or org-sidebar give me too much information and I get lost).
I'm going to investigate if something similar can be done with
context-menu-mode...
Thank you for all the info!
[1] https://i.imgur.com/KoAZtIz.png
┌────
│ (defun my-org-where-i-am-popup ()
│ (interactive)
│ (setq org-heading-titles-list nil)
│ (org-with-wide-buffer
│ (save-excursion
│ (save-restriction
│ (org-back-to-heading t)
│ (if (eq (org-element-property :level (org-element-at-point)) 1)
│ (message "First level")
│ (push (cons (org-link-display-format
│ (nth 4 (org-heading-components)))
│ (point))
│ org-heading-titles-list)
│ (while
│ (ignore-errors (outline-up-heading 1 t))
│ (push (cons (org-link-display-format
│ (nth 4 (org-heading-components)))
│ (point))
│ org-heading-titles-list))))))
│ (org-with-wide-buffer
│ (save-excursion
│ (save-restriction
│ (goto-char
│ (popup-menu* (mapcar
│ (lambda (x)
│ (popup-make-item (car x) :value (cdr x)))
│ org-heading-titles-list)
│ :isearch t
│ :initial-index (length org-heading-titles-list)))
│ (org-tree-to-indirect-buffer)))))
└────
--
Juan Manuel Macías
https://juanmanuelmacias.com
https://lunotipia.juanmanuelmacias.com
https://gnutas.juanmanuelmacias.com
^ permalink raw reply [relevance 10%]
* Re: insert automatically a reference to a section header and a link
@ 2021-11-17 15:42 10% ` Juan Manuel Macías
1 sibling, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-11-17 15:42 UTC (permalink / raw)
To: Stefan Nobis; +Cc: Uwe Brauer, orgmode
Stefan Nobis writes:
> Hmmm... for me, the default way to link to headings is just fine, I
> seldom need more control over the generated labels:
>
> #+begin_src org
> ,* Intro
>
> Lorem ipsum dolor sit amet...
>
> ,* Another section
>
> As seen in [[*Intro]] there is not much to say.
> #+end_src
Completely agree. I also tend to use `org-super-link'
(https://github.com/toshism/org-super-links). It can be run with
helm-org-ql, so if there are a lot of headings in the document, I just
have to navigate through them using helm-org-ql, and insert a link at
point to the chosen candidate. And in the destination header a back link
is also inserted.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* false-list-item-mode?
@ 2021-02-23 18:23 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-02-23 18:23 UTC (permalink / raw)
To: orgmode
Hi,
This is not a solution to what was commented in this recent thread
(https://lists.gnu.org/archive/html/emacs-orgmode/2021-02/msg00239.html)
on the false list item issue. But, in case anyone finds it useful, I
happened to sketch this minor mode to highlight, while typing, *only*
(+/-) those lines in a paragraph that start with a 'false' list item.
The code is in this GitLab snippet:
https://gitlab.com/-/snippets/2081294
And here a short screenshot:
https://gnutas.juanmanuelmacias.com/images/false-list-item-mode-test.mp4
Feedback Welcome!
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Pandoc and nested emhases
@ 2022-02-18 12:31 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-02-18 12:31 UTC (permalink / raw)
To: Max Nikulin; +Cc: orgmode
Hi Maxim,
Max Nikulin writes:
> So formally this feature of pandoc is a bug (due to different kind of
> parser). It is the reason why a corpus of tests should exist in a
> format that can be easily imported from various programming languages.
Your conclusions seem logical to me. It may sound a bit surrealistic to
think that Pandoc is doing it wrong precisely for doing it "right", but...
if from Org's point of view this is not something specified in its
syntax, then here Pandoc makes a mistake parsing Org's syntax. All this
is very curious, indeed. I confess that before I did not see the need for
those corpus of tests very clearly, but this case has opened my mind.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [Patch] to correctly sort the items with emphasis marks in a list
@ 2021-04-10 11:41 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-10 11:41 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: orgmode
Hello Nicolas,
Nicolas Goaziou writes:
> Do you have a simple test case to reproduce the problem? Currently
> sorting the following trivial lists causes no issue:
>
> - b
> - *a*
>
> and
>
> - *b*
> - a
Consider this (unordered) list:
- a
- b
- /v/
- /a/
The current result is wrong:
- /a/
- /v/
- a
- b
With the spaces removed in `org-sort-remove-invisible', this would be the
expected result[1]:
- a
- /a/
- b
- /v/
[1] According to the National Information Standards Organization:
"Different typefaces (italic, boldface, blackletter, etc.) do not affect
the arrangement of letters." (see p. 3 on:
https://www.niso.org/sites/default/files/2017-08/tr03.pdf)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [tip] Insert arbitrary LaTeX code at the beginning of any float environment
@ 2022-05-09 14:01 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-05-09 14:01 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: Eric S Fraga, orgmode
Ihor Radchenko writes:
> I'd be happy to see a built-in solution for this.
> I feel that the ability to insert arbitrary LaTeX code near the
> begin/end of environment would be generally a useful feature to have in
> ox-latex. It could be done via #+attr_latex: :pre/:post
>
> Moreover, it would be useful to be able to wrap the whole chunk into
> custom environment:
> #+attr_latex: :wrap [options]environmant
>
> WDYT?
I think they are both great ideas, especially the second one. Although
---as Eric says--- we can always use special blocks, a :wrap attribute
would drastically lighten the readability of the document, and could be
very useful in those complex constructions where we need to enclose a
table or a figure in another environment (for example, with the
threeparttable package and others like it).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [proof of concept] inline language blocks
@ 2024-02-29 10:41 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2024-02-29 10:41 UTC (permalink / raw)
To: Max Nikulin; +Cc: emacs-orgmode
Max Nikulin writes:
>> the user should expect something like &foo{...} to produce \foo{...} or
>> <span class=foo>...</span>, etc. The only difference is that there would
>> be an anonymous variant &_{...}.
>
> I do not try to dispute \foo and class="foo" as default behavior. I
> suggest to implement possibility to override default behavior of
> &foo{text} to \bar{text} and <bar>text</bar>. The same is applicable
> for anonymous objects
>
> &_[:latex_command bar :html_element bar]{text}
Maxim, I insist that I follow the logic of the "large" special blocks.
Anyway, I think your example only makes sense in HTML, or at least I
can't make sense of it in LaTeX. Why would anyone want &foo{text} to be
passed to LaTeX as \bar{text}, instead of just &bar{text}? In HTML it
does seem sensible to me that someone would want to change the tags.
Maybe with a :html-tag, or something like that.
As for :latex-command, if I understand it correctly, I don't quite see
how useful this could be:
&foo[:latex-command bar]{text} == LaTeX ==> \bar{text}
when it is simpler to put:
&bar{text}
The same thing happens with the anonymous variant:
&_[:latex-command foo]{text} == LaTeX ==> \foo{text}
which is identical to putting &foo{text}
The anonymous variant would be equivalent in LaTeX to a
\begingroup...\endgroup, or rather to {...}. One could add all the
commands one wants within the group simply with :prelatex:
&_[:prelatex \foo\bar\vaz\blah{}]{text}
==> {\foo\bar\vaz\blah{}text}
I'm not opposed to your ideas, I just can't find a use case for it. In
LaTeX, I mean. In the case of HTML I find it useful, indeed, to have
more control over the tags: <foo></foo>, <bar></bar>, etc.
In any case, I think that my implementation leaves open the possibility
of extending it with everything you mentioned, or anything else.
--
Juan Manuel Macías -- Composición tipográfica, tratamiento de datos, diseño editorial y ortotipografía
^ permalink raw reply [relevance 10%]
* Re: [External] : Re: missing a character / font in agenda?
@ 2022-07-13 10:01 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-07-13 10:01 UTC (permalink / raw)
To: Stefan Kangas; +Cc: Daniel Ortmann, orgmode, Ihor Radchenko, Greg Minshall
Stefan Kangas writes:
> If that is true (I don't know) then maybe we should just use a more
> ubiquitous glyph?
I have done a quick test with some fonts that are ---I believe--- quite
popular. This character is missing from DejaVu Sans Mono, Iosevka,
Source Pro, Fira Code and Hack. JuliaMono does include it:
https://i.imgur.com/O3urnxa.png
I think LEFTWARDS ARROW / #2190 of the 'arrows' Unicode block is much
more common:
https://i.imgur.com/h0NQXvG.png
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Org to ConTeXt exporter?
@ 2020-12-28 15:38 10% ` Juan Manuel Macías
1 sibling, 0 replies; 200+ results
From: Juan Manuel Macías @ 2020-12-28 15:38 UTC (permalink / raw)
To: Marcin Borkowski; +Cc: orgmode
Hello, Marcin,
Marcin Borkowski <mbork@mbork.pl> writes:
> Creating an exporter from scratch is probably easier than you think.
> A few years ago I planned a tutorial about this, but another job
> happened, then covid happened etc. Now that I finished some big project
> taking me a lot of time, I might be tempted to revisit that. Would
> there be demand for a DYI Org-exporter-from-scratch tutorial?
Thank you for your answer. Actually a tutorial on how to create an
exporter from scratch (I think) would be really interesting. Some time
ago I was tempted to start writing an exporter for ConTeXt, studying the
code of the other exporters, but for time and work reasons I left the
project abandoned.
If you finally write that tutorial, I could also translate it into
Spanish to spread it out among Spanish-speaking Org users.
Regards,
Juan Manuel
> Best,
^ permalink raw reply [relevance 10%]
* Re: [BUG] Conflict between org-emphasis and org-latex
@ 2021-09-26 12:57 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-09-26 12:57 UTC (permalink / raw)
To: Léo Ackermann; +Cc: orgmode
Hi Léo,
Léo Ackermann writes:
> Hi!
> I noticed that in org@888aaa97c0ce331097787333d0d712dd6e4d078f, the
> following happens:
> When writing `Consider $a^{*}$ and $b^{*}$` in an org-mode buffer, the
> two stars match together, causing "and" to appear in bold case.
>
> Any idea to fix this unwanted behavior ?
You can insert a zero width space character (U+200B), to prevent that
segment is fontified as emphasis [see the Manual in the section `Escape
Character']. It is enough with insert the character after one of the
asterisks: M-x insert-char RET 200b RET. I also recommend that you look
at this section on Timothy's blog `This Month in Org':
https://blog.tecosaur.com/tmio/2021-05-31-async.html#easy-zero-width
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Org as a workspace (an impromptu reflection)
@ 2022-05-03 23:41 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-05-03 23:41 UTC (permalink / raw)
To: Nick Dokos; +Cc: orgmode
Nick Dokos writes:
> From my vantage point (of ignorance about it :-) ), this sounds like
> org-roam to me: https://www.orgroam.com/
I've read here and there interesting things about org-roam, but I admit
I've never had the courage to try it. Partly due to lack of time and
partly because with my current Org setup I am reasonably satisfied. In
any case, everything I described I get with (if the expression is
allowed) 'org-vanilla' :-) (+ a number of must-have packages, such as
org-ql/helm-org-ql, org-super-links, org-transclusion, and more).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: example paper written in org completely
@ 2021-06-17 12:51 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-17 12:51 UTC (permalink / raw)
To: Eric S Fraga; +Cc: orgmode
Hi Eric,
Eric S Fraga writes:
> Dear all,
>
> for those that may be interested, my latest paper (well, preprint at
> this stage) is available if you are looking for an example of a
> numerical work where the paper is completely written in org, including
> data analysis and visualisation. See signature for link.
>
> The arxiv deposit includes the complete org file as an ancillary file.
Congratulations. Thanks for sharing your work.
By the way, I think it would be nice to create on the Worg website a
section called "Org Showcase" or similar, just like there is a "Tex
Showcase" on the Tex User Group website: http://tug.org/texshowcase/,
with samples of published books, articles or web pages, all written in
Org, to demonstrate the productivity of Org Mode.
What do you think?
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: I can't set dabbrev to respect the writen case
@ 2022-05-15 13:58 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-05-15 13:58 UTC (permalink / raw)
To: Ypo; +Cc: orgmode
Ypo writes:
> These are my variables, it keeps changing what I have already written:
>
> '(case-replace nil)
>
> '(dabbrev-case-distinction t)
> '(dabbrev-case-fold-search t)
> '(dabbrev-case-replace t)
> '(dabbrev-upcase-means-case-search nil)
With those values it works for me as expected. Maybe it's a problem with
your configuration. Try starting emacs with 'emacs -q' and evaluate the
variables with:
M-x eval-expression
(setq dabbrev-case-distinction t
dabbrev-case-fold-search t
dabbrev-case-replace t
abbrev-upcase-means-case-search nil)
RET
I hardly use dabbrev and I'm afraid I can't give you any more tips.
Try asking <emacs-devel@gnu.org> as well.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword
@ 2023-09-16 18:00 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2023-09-16 18:00 UTC (permalink / raw)
To: orgmode
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
Rationale for this patch: in certain cases, in a LaTeX document, it is
necessary to add code before the class declaration (\documentclass...).
For example, commands like \PassOptionsToPackage, \DocumentMetadata{ },
etc.; or certain packages that should be loaded first using
\RequirePackage{}; and other miscellaneous cases[1]. I think that by
defining a new keyword `latex_pre_header', which behaves the same as
latex_header but concatenated before the class, these situations can be
resolved from Org.
[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{...
--
Juan Manuel Macías
https://juanmanuelmacias.com
https://lunotipia.juanmanuelmacias.com
https://gnutas.juanmanuelmacias.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-lisp-ox-latex.el-latex-Add-LATEX_PRE_HEADER-keyword.patch --]
[-- Type: text/x-patch, Size: 1944 bytes --]
From ac6b743a4489f7bc8ab1cdae7ffd3b36e5f3c1d2 Mon Sep 17 00:00:00 2001
From: Juan Manuel Macias <maciaschain@posteo.net>
Date: Sat, 16 Sep 2023 19:22:39 +0200
Subject: [PATCH] lisp/ox-latex.el (latex): Add `LATEX_PRE_HEADER' keyword
* (org-latex-make-preamble): In some cases it is necessary to add code
before the `\documentclass' line. `LATEX_PRE_HEADER' behaves the same as
`LATEX_HEADER', except that it is concatenated before the class.
---
lisp/ox-latex.el | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index 14105c7cc..5e97b8b3d 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -124,6 +124,7 @@
(:latex-class-options "LATEX_CLASS_OPTIONS" nil nil t)
(:latex-header "LATEX_HEADER" nil nil newline)
(:latex-header-extra "LATEX_HEADER_EXTRA" nil nil newline)
+ (:latex-pre-header "LATEX_PRE_HEADER" nil nil newline)
(:description "DESCRIPTION" nil nil parse)
(:keywords "KEYWORDS" nil nil parse)
(:subtitle "SUBTITLE" nil nil parse)
@@ -1984,13 +1985,18 @@ specified in `org-latex-default-packages-alist' or
(replace-regexp-in-string
"^[ \t]*\\\\documentclass\\(\\(\\[[^]]*\\]\\)?\\)"
class-options header t nil 1))))
- (user-error "Unknown LaTeX class `%s'" class))))
+ (user-error "Unknown LaTeX class `%s'" class)))
+ (pre-header (mapconcat
+ #'org-element-normalize-string
+ (list (plist-get info :latex-pre-header) ""))))
(org-latex-guess-polyglossia-language
(org-latex-guess-babel-language
(org-latex-guess-inputenc
(org-element-normalize-string
(org-splice-latex-header
- class-template
+ (if pre-header
+ (format "%s\n%s" pre-header class-template)
+ class-template)
(org-latex--remove-packages org-latex-default-packages-alist info)
(org-latex--remove-packages org-latex-packages-alist info)
snippet?
--
2.42.0
^ permalink raw reply related [relevance 10%]
* Re: org-attach-git don't automatically commit changes
@ 2021-01-31 13:16 10% ` Juan Manuel Macías
2021-01-31 11:41 10% ` Juan Manuel Macías
1 sibling, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-01-31 13:16 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko <yantar92@gmail.com> writes:
> The other thing is that `org-attach-id-dir' makes much less sense from
> the time :DIR: property was introduced. So, I believe that
> org-attach-git should be updated. Probably, handling attachment dirs as
> individual git repos can be one of the ways to upgrade the current
> version. I guess, patches welcome.
Do you think a possible patch could simply consist of replacing (as I
have done) `(expand-file-name org-attach-id-dir)' by `(org-attach-dir)'
in `org-attach-git-commit'? This would allow you to handle attachment
dirs as individual git repos, regardless of :ID: or :DIR: properties,
since "[(org-attach-dir)] Return the directory associated with the
current outline node. First check for DIR property, then ID property
[...]".
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Failure to resolve internal links on ox-html export?
@ 2021-06-18 20:37 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-18 20:37 UTC (permalink / raw)
To: Tim Visher; +Cc: orgmode
Hi Tim,
Tim Visher writes:
> What I really want is something that keeps the link text but drops the
> link, essentially converting it into plain text (or stylized text if
> the link text is in markup).
According to the `org-export-with-broken-links' docstring:
-----------------------------------
[...] If it is set to ‘mark’, broken links are marked as such in the
output, with a string like
[BROKEN LINK: path]
where PATH is the un-resolvable reference.
This option can also be set with the OPTIONS keyword, e.g.,
"broken-links:mark".
-----------------------------------
It's not exactly what you're looking for, but it can help you find a
solution.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Export Org mode files to (gag, barf) MS Office?
@ 2021-06-26 15:15 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-26 15:15 UTC (permalink / raw)
To: Brandon Taylor; +Cc: orgmode
Hello,
Brandon Taylor writes:
> I know we’re not supposed to really even TALK about proprietary
> software in FOSS communities like this one, but I can’t help but
> wonder if someone might consider making (an) Emacs plugin(s) that
> allow(s) a user to export Org mode files to Microsoft Office file
> formats such as .docx, .xlsx and the like? Or is/are there already (a)
> plugin(s) in the MELPA that can do this?
You may be interested in the variable `org-odt-preferred-output-format'.
According to the docstring:
"[...] Automatically post-process to this format after exporting to
"odt". Command ‘org-odt-export-to-odt’ exports first to "odt" format and
then uses ‘org-odt-convert-process’ to convert the resulting document to
this format. During customization of this variable, the list of valid
values are populated based on ‘org-odt-convert-capabilities’.[...]"
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Org as a book publisher
[not found] ` <87ft16hn62.fsf@emailmessageidheader.nil>
@ 2021-03-07 20:20 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-03-07 20:20 UTC (permalink / raw)
To: Bob Newell; +Cc: orgmode
Hi Bob, thank you for your comment.
Bob Newell <bobnewell@bobnewell.net> writes:
> Aloha,
>
> Thank you for your interesting and useful post.
>
> I must really look into your examples and process. I have
> published quite a number of books with LaTeX but my process
> has been to write in org-mode, then export, and do all the
> design and typesetting directly in LaTeX. I end up with a good
> result but I would really rather work more in org-mode.
>
> Layouts require a lot of fine-tuning, particularly complex
> layouts with multiple columns. If some or most of that could
> be accomplished in org-mode, it would be a great benefit.
Multiple column layout, for example, can be achieved from Org with a
special block (and loading the multicol package). For example:
#+LaTeX_Header: \usepackage{multicol}
#+ATTR_LaTeX: :options {2}
#+begin_multicols
...
#+end_multicols
As I mentioned in a previous message, I have to organize and clean all
the code in those two books of my samples, and upload it to GitLab, in
case it could be useful to someone...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: how to export an org file, to 2 different locations (in to different formats)
@ 2022-05-28 9:06 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-05-28 9:06 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Uwe Brauer writes:
> I have also to confess, that I usually am I bit hesitant to use
> defadvice since it changes the vanilla function, and might cause
> problems, but maybe this is just me.
You are absolutely right, and I confess that I would have the same
precautions :-). Also, the defadvice code is very poorly tested, and is
likely to cause some collateral kills... If you need it for specific use
cases, you can try evaluating it only for specific sessions, instead of
leaving it in your init file. Or make a mode that turns it on or off.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Experimental public branch for inline special blocks
@ 2024-04-10 23:00 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2024-04-10 23:00 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: Max Nikulin, emacs-orgmode
Ihor Radchenko writes:
> Max Nikulin <manikulin@gmail.com> writes:
>
>> On 09/04/2024 15:52, Ihor Radchenko wrote:
>>> Aside: It looks like your public branch is not up-to-date as the time
>>> of writing this email - I do not see commits changing the syntax to
>>> @foo{...} and @@{...} yet,
>>
>> Do you have in your local copy the following?
>> ...
>
> I do now. Apparently, I somehow reviewed an earlier local copy of the
> branch.
Hi, Ihor. Thanks for all your comments. I will try to answer each of the
questions you have raised. Let's see if I can find a space next week...
The latest added to the branch are Maxim's proposals (and code) for
backend control. See this thread:
https://list.orgmode.org/?t=20240321102752
And this other thread, continuation of the previous one:
https://list.orgmode.org/877ciavnwo.fsf_-_@posteo.net/
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [tip for EXWM users] An alternative method for isolate trees
@ 2021-03-01 14:10 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-03-01 14:10 UTC (permalink / raw)
To: Julian M. Burgos; +Cc: orgmode
Hi Julian, thanks for your comment.
"Julian M. Burgos" <julian.burgos@hafogvatn.is> writes:
> Thank you, although I tested your functions and compared with the
> original org-tree-to-indirect-buffer, the only difference I see is
> that your function creates a new exwm workspace. The original function
> already creates indirect buffers with their own names (using a slash
> instead of the double colons). Or I am missing something?
org-tree-to-indirect-buffer creates a new buffer, but (as far as I know)
does not allow accumulating buffers. In other words, you cannot have
several isolated trees at the time. In this method it just occurred to
me to configure org-indirect-buffer-display as new-frame and take
advantage of EXWM frame management.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: A quick LaTeX reference guide in Org
@ 2021-10-25 14:10 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-10-25 14:10 UTC (permalink / raw)
To: Eric S Fraga; +Cc: orgmode
Eric S Fraga writes:
> It's in CTAN, the official (?) LaTeX repository.
I just saw it now there. CTAN is an infinite bazaar :-)
By the way, in CTAN there is also the /TeX for the Impatient/ book (I
love that title), which is a very good manual for programming at low
level in TeX/plainTeX: https://www.ctan.org/pkg/impatient (it's more
concise than Knuth's /TeX book/, which I bought on paper a long time
ago, for 'historical' reasons...)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [Patch] ob-tangle.el: New value 'ascii' for the header argument ':comments'
@ 2022-06-13 10:22 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-06-13 10:22 UTC (permalink / raw)
To: Rudolf Adamkovič; +Cc: orgmode
Hi, Rudolph,
Rudolf Adamkovič writes:
> Oh, I see. Thank you for the explanation. I can see myself using such
> new tangle comments all the time! But then, I use UTF-8 and not the
> standard 7-bit ASCII for my Org documents. Hence, I would want to see
> ':comments plain' or ':comments plain-text' instead.
What you comment makes sense, because `ascii' can lead to confusion. I
chose the term `ascii' because the backend used to convert the text is
called `ascii', although if I evaluate something like
(org-export-string-as "αβγδ" 'ascii t)
the result is utf8.
I think it might be a good idea to use `plain' for the value name, as
you say, instead of `ascii'...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [correction]
@ 2022-10-30 19:51 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2022-10-30 19:51 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Uwe Brauer writes:
> But not not -- which is the
> (setq filetags-delimiter-between-filename-and-tags " -- ")
>
> orginal setting, hm, not sure why this is so
I think locate can't look for things like " -- "; Also, it's too
generic. It is safer to use alphanumeric characters. For example, if you
prefer something shorter, you can do:
(setq filetags-delimiter-between-filename-and-tags " @@ ")
That should be found by locate.
Regarding the updatedb issue, it seems that in Ubuntu you have to do it
manually. You would have to edit the crontab file. See:
https://askubuntu.com/questions/203597/how-do-i-run-updatedb-everyday
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [possible patch] Remove the '\\[0pt]' string from the last line of a verse block in LaTeX export
@ 2024-01-20 10:57 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2024-01-20 10:57 UTC (permalink / raw)
To: Max Nikulin; +Cc: Ihor Radchenko, orgmode
Max Nikulin writes:
> On 18/01/2024 20:05, Ihor Radchenko wrote:
>> With the patch, I am getting the following:[...]
>> \begin{center}
>> \begin{tabular}{lr}
>> {[}foo] & 2\\[0pt]
>> {[}bar] & 3\\[0pt]
>> \end{tabular}
>> \end{center}
>
> It means that [0pt] is not necessary any more. However users will have
> adjust their filters once more. I have no idea if many of them will
> complain concerning {[} where it is not really required.
> (/[omitted]/).
>
> To have an additional excuse, it is better to add a note that it is
> inspired by pandoc strategy.
I agree with the note. Perhaps both strategies could coexist: by
default, Ihor's code; and org-latex-line-break-safe with value "\\\\".
And, after some time, the latter could become obsolete, unless a new
''raison d'etre'' is found for it...
In any case, I would no longer see it necessary to modify
org-latex-verse-block anymore.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Org to ConTeXt exporter?
@ 2020-12-28 13:38 10% Juan Manuel Macías
0 siblings, 2 replies; 200+ results
From: Juan Manuel Macías @ 2020-12-28 13:38 UTC (permalink / raw)
To: orgmode
Hi,
Just out of curiosity, I am wondering if there are plans to create an
Org to ConTeXt exporter in the future, or if there is already some work
in progress on this front.
I have to say that among TeX formats I tend to prefer LaTeX to ConTeXt;
but ConTeXt has very interesting features (grid typesetting, for
example) that LaTeX lacks (for now) and has a more monolithic structure,
that is, it does not need to be extended through packages as in LaTeX.
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: error org export to pdf when latex letter class has been added to org-latex-classes
@ 2022-09-13 20:15 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-09-13 20:15 UTC (permalink / raw)
To: M. Pger; +Cc: orgmode
M. Pger writes:
> Thank you for your answer.
>
>> Are you including citations in your letter?
>
> No, that's also why it is puzzling. You should be able to reproduce
> the issue by creating a really minimalist init file including the
> following:
>
> ```
> (with-eval-after-load 'ox-latex
> (add-to-list 'org-latex-classes '("letter" "\\documentclass{letter}"))
> )
>
> (setq org-latex-pdf-process (list "latexmk -shell-escape -f -pdf %f"))
> ```
>
> As mentioned in my previous mail, the error also appears when using `pdflatex` instead of `latexmk`.
Hmm, it's weird. With your configuration I cannot reproduce the problem.
Anyway, I have Org configured so that it doesn't load any package in the
preamble.
And if you directly compile the .tex file generated by org during
export, does it also give you an error? Could you please paste the
preamble of that tex file here, up to the \begin{document}?
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Footnote definition within a verse block has spurious line breaks when exported to LaTeX
@ 2020-12-05 13:47 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2020-12-05 13:47 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: orgmode
Hello,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> This is hopefully fixed in master branch. Let me knows if it works for
> you.
Thank you, Nicolas. I've tried it and it works perfectly. I see that
\footnotemark\footnotetext is used now, same as in tables. I
think it's a great solution.
Best,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Bug: Footnotes on Headers and LaTeX export [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]
@ 2020-12-09 15:06 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2020-12-09 15:06 UTC (permalink / raw)
To: Charis Michelakis; +Cc: orgmode
Hello,
Charis Michelakis <ch.p.mxs@gmail.com> writes:
> There is a potential bug regarging how footnotes on headers are
> converted to LaTeX.
>
> Consider the following org file:
> ------start-of-file-----------
>
> #+AUTHOR: Me
> #+LATEX_HEADER: \usepackage{titlesec}
>
> * Header1[fn:1]
>
> * Footnotes
>
> [fn:1]Lorem ipsum
It is a LaTeX problem, as the footnote command is a 'fragile' command and should not
be put in a section. Try this:
* Header1[fn:1]
:PROPERTIES:
:ALT_TITLE: Header1
:END:
* Footnotes
[fn:1]Lorem ipsum
in latex it is exported as
\section[Header1]{Header1\footnote{Lorem ipsum}}
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: *strong* markup not honored at boundary of macro input during HTML export
@ 2020-12-23 15:22 10% ` Juan Manuel Macías
[not found] ` <7e5e7cbe-31d6-2d9e-e450-9c1b54dba95e@gmail.com>
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2020-12-23 15:22 UTC (permalink / raw)
To: m27315; +Cc: orgmode
Hello, a possible dirty solution could be defining the macro with two
Unicode zero-width spaces (u+200b):
#+MACRO: quote (eval (concat "@@html:<span class=\"quote\">“@@" "\u200B" $1 "\u200B" "@@html:”</span>@@"))
Regards,
Juan Manuel
m27315 <m27315@gmail.com> writes:
> Resending as plain-text ... If somebody could point me in the direction of
> the code that might be responsible for this, I'll try to take a look.
>
> ....
>
> If the following org file is exported as HTML, any *strong* markup for words
> at the beginning or the end of the input string are ignored. (I have
> included several slight variations to help testing.)
>
> #+TITLE: Test MACRO with *strong* Markup Input
> #+OPTIONS: date:nil timestamp:nil num:nil stat:t title:t toc:nil
>
> #+MACRO: quote @@html:<span class="quote">“@@$1@@html:”</span>@@
>
> * Test macro with non-marked text:
> Demonstrating that, {{{quote(This is a vanilla quote without markup)}}},
> Abraham Lincoln.
>
> {{{quote(This is a similar control quote without markup)}}}, George
> Washington said.
>
> * Test macro with leading *strongly* marked text:
> Wilson quipped, {{{quote(*Not all* quotes are important!)}}}.
>
> {{{quote(*But this* is a very important quote)}}}, Thomas Jefferson replied.
>
> * Test macro with trailing *strongly* marked text:
> Retorted Yoda, {{{quote(Critical if not uncertain\, all *my quotes are*)}}}.
>
> {{{quote(I am certain they are *all uncertain*)}}}, Anakin sneered.
>
> * Test macro with leading, middle, and trailing marked text:
> Darth Vader threatened, {{{quote(*All* of *my quotes* are *heeded
> carefully!*)}}}.
>
> {{{quote(*Nobody* listens to *meesa* quotes. *Why?*)}}}, Jar-Jar whined.
>
> The condensed filtered HTML output is:
>
> ...
> <h2 id="org40a1103">Test macro with non-marked text:</h2>
> <p>Demonstrating that, <span class="quote">“This is a vanilla
> quote without markup”</span>, Abraham Lincoln.</p>
> <p><span class="quote">“This is a similar control quote without
> markup”</span>, George Washington said.</p>
>
> <h2 id="org962a914">Test macro with leading <b>strongly</b> marked
> text:</h2>
> <p>Wilson quipped, <span class="quote">“*Not all* quotes are
> important!”</span>.</p>
> <p><span class="quote">“*But this* is a very important
> quote”</span>, Thomas Jefferson replied.</p>
>
> <h2 id="org47bf84f">Test macro with trailing <b>strongly</b> marked
> text:</h2>
> <p>Retorted Yoda, <span class="quote">“Critical if not uncertain,
> all *my quotes are*”</span>.</p>
> <p><span class="quote">“I am certain they are *all
> uncertain*”</span>, Anakin sneered.</p>
>
> <h2 id="org08c1694">Test macro with leading, middle, and trailing marked
> text:</h2>
> <p>Darth Vader threatened, <span class="quote">“*All* of <b>my
> quotes</b> are *heeded carefully!*”</span>.</p>
> <p><span class="quote">“*Nobody* listens to <b>meesa</b> quotes.
> *Why?*”</span>, Jar-Jar whined.</p>
> ...
>
> Notice how the *strong* marks are only transformed into <b></b> tags inside
> a string, not at the boundaries.
>
> Can anybody confirm or explain what I am doing wrong?
>
> Thanks!
>
> Trevor
>
>
^ permalink raw reply [relevance 10%]
* Re: *strong* markup not honored at boundary of macro input during HTML export
[not found] ` <7e5e7cbe-31d6-2d9e-e450-9c1b54dba95e@gmail.com>
@ 2020-12-23 16:05 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2020-12-23 16:05 UTC (permalink / raw)
To: m27315; +Cc: orgmode
You're welcome. Some time ago I had a similar problem with a LaTeX
command with arguments that I wanted to include in a macro. Since the
character U+200b is a kind of "ghost space", it can act as an "invisible
barrier" between the emphasis marks and the characters that precede or
follow them. An emergency cure ;-)
Regards,
Juan Manuel
m27315 <m27315@gmail.com> writes:
> Worked like a charm. Thanks, Juan!
>
> On 2020-12-23 9:22 AM, Juan Manuel Macías wrote:
>> quote (eval (concat "@@html:<span class=\"quote\">“@@" "\u200B" $1 "\u200B" "@@html:”</span>@@"))
>
^ permalink raw reply [relevance 10%]
* Re: A way to avoid unwanted new lines when using paragraph quotes?
@ 2020-12-27 13:55 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2020-12-27 13:55 UTC (permalink / raw)
To: Kashyap Chamarthy; +Cc: orgmode
Hello,
Kashyap Chamarthy <kashyap.cv@gmail.com> writes:
> Is there a way to avoid the said new lines in the above mentioned
> examples? (NB: A space right _before_ the quote starts is okay.) Or
> alternatively, is there a way to consistently force a new line in the
> HTML export, after each of "Test 1", "Test 2", et al?
A solution could be to 'force' a homogeneous space between all the items
of the list by modifying the 'margin' property
(https://www.w3schools.com/cssref/pr_margin.asp).
For example:
#+HTML_HEAD: <style> li{margin: 15px;}</style>
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Bug: Tildes in URL impact visible link text [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]
@ 2020-12-27 18:12 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2020-12-27 18:12 UTC (permalink / raw)
To: Chris Hunt; +Cc: orgmode
Hello,
I think the problem comes because in that url the tilde does not have an
escape character. If it's just that case, you can try replacing each
tilde with %7E (see
https://www.w3schools.com/tags/ref_urlencode.asp). That way the
link description would have to be formatted correctly, without spurious
characters.
Regards
Juan Manuel
Chris Hunt <chrahunt@gmail.com> writes:
> I'm trying to create a link in an org file with this URL:
>
> https://console.aws.amazon.com/cloudwatch/home?region=us-east-1#metricsV2:graph=~(view~'timeSeries~stacked~false~metrics~(~(~'CWAgent~'backup_time~'host~'desktop~'metric_type~'timing))~region~'us-east-1);query=~'*7bCWAgent*2chost*2cmetric_type*7d
>
> and this description: "metrics".
>
> To do it, I followed these steps:
>
> 1. run `emacs -Q test.org`, where test.org is not an existing file
> 2. emacs GUI displays, type `M-x org-insert-link`
> 3. a "Link" prompt is displayed, paste the link and press return
> 4. a "Description" prompt is displayed, type "metrics" and press return
>
> At this point I expect to see only the text "metrics" in the buffer, with normal
> link decoration (underline and highlight).
>
> Instead, I see "~(~'CWAgent~metrics" with some mix of link decoration
> and some other style, as shown in the following image:
>
> https://i.imgur.com/vb9vE43.png
>
> The actual text from the file is
>
> [[https://console.aws.amazon.com/cloudwatch/home?region=us-east-1#metricsV2:graph=~(view~'timeSeries~stacked~false~metrics~(~(~'CWAgent~'backup_time~'host~'desktop~'metric_type~'timing))~region~'us-east-1);query=~'*7bCWAgent*2chost*2cmetric_type*7d][metrics]]
>
> This is emacs 27.1 from http://ppa.launchpad.net/kelleyk/emacs/ubuntu,
> with org version 9.3.
>
> Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version
> 3.22.30, cairo version 1.15.10)
> of 2020-09-19
> Package: Org mode version 9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)
>
> current state:
> ==============
> (setq
> org-src-mode-hook '(org-src-babel-configure-edit-buffer
> org-src-mode-configure-edit-buffer)
> org-link-shell-confirm-function 'yes-or-no-p
> org-metadown-hook '(org-babel-pop-to-session-maybe)
> org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
> org-mode-hook '(#[0 "\300\301\302\303\304$\207"
> [add-hook change-major-mode-hook org-show-all append local]
> 5]
> #[0 "\300\301\302\303\304$\207"
> [add-hook change-major-mode-hook org-babel-show-result-all
> append local]
> 5]
> org-babel-result-hide-spec org-babel-hide-all-hashes)
> org-archive-hook '(org-attach-archive-delete-maybe)
> org-confirm-elisp-link-function 'yes-or-no-p
> org-agenda-before-write-hook '(org-agenda-add-entry-text)
> org-metaup-hook '(org-babel-load-in-session-maybe)
> org-bibtex-headline-format-function #[257 "\300 \236A\207" [:title] 3
> "\n\n(fn ENTRY)"]
> org-babel-pre-tangle-hook '(save-buffer)
> org-tab-first-hook '(org-babel-hide-result-toggle-maybe
> org-babel-header-arg-expand)
> org-occur-hook '(org-first-headline-recenter)
> org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-show-empty-lines
> org-optimize-window-after-visibility-change)
> org-speed-command-hook '(org-speed-command-activate
> org-babel-speed-command-activate)
> org-confirm-shell-link-function 'yes-or-no-p
> org-link-parameters '(("attachment" :follow org-attach-open-link :export
> org-attach-export-link :complete
> org-attach-complete-link)
> ("id" :follow org-id-open)
> ("eww" :follow eww :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)
> ("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) ("file+sys")
> ("file+emacs") ("shell" :follow org-link--open-shell)
> ("news" :follow
> #[257 "\301\300\302 Q!\207" ["news" browse-url ":"] 5
> "\n\n(fn URL)"]
> )
> ("mailto" :follow
> #[257 "\301\300\302 Q!\207" ["mailto" browse-url ":"]
> 5 "\n\n(fn URL)"]
> )
> ("https" :follow
> #[257 "\301\300\302 Q!\207" ["https" browse-url ":"]
> 5 "\n\n(fn URL)"]
> )
> ("http" :follow
> #[257 "\301\300\302 Q!\207" ["http" browse-url ":"] 5
> "\n\n(fn URL)"]
> )
> ("ftp" :follow
> #[257 "\301\300\302 Q!\207" ["ftp" browse-url ":"] 5
> "\n\n(fn URL)"]
> )
> ("help" :follow org-link--open-help)
> ("file" :complete org-link-complete-file)
> ("elisp" :follow org-link--open-elisp)
> ("doi" :follow org-link--open-doi))
> org-link-elisp-confirm-function 'yes-or-no-p
> )
>
^ permalink raw reply [relevance 10%]
* Re: Bug: Tildes in URL impact visible link text [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]
@ 2020-12-27 21:33 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2020-12-27 21:33 UTC (permalink / raw)
To: tomas; +Cc: orgmode
Hello,
<tomas@tuxteam.de> writes:
> This would be a bug: tilde is an allowed URI character [1]
You're right. I have also noticed that if I write links like these:
[[*foo ~foo~ foo]][[foo]]
[[*foo =foo= foo]][[foo]]
There is an anomaly in the description similar to what Chris comments in
his email...
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Org to ConTeXt exporter?
@ 2020-12-28 18:03 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2020-12-28 18:03 UTC (permalink / raw)
To: Diego Zamboni; +Cc: orgmode
Hello, Diego,
Diego Zamboni <diego@zzamboni.org> writes:
> I have never used ConTeXt, but from what I've seen, despite its many
> differences, a lot is still similar to TeX/LaTeX (e.g. math). Given
> this, I think it might be easier to create a new derived exporter from
> ox-latex, and override the parts that differ, instead of creating a
> new one completely from scratch.
You are right, maybe it is better to start with ox-latex, since LaTeX
and ConTeXt are related.
> You can see an example in my own
> https://github.com/zzamboni/ox-leanpub/blob/master/ox-leanpub-markua.el,
> which uses ox-md as a backend for defining the new ox-markua exporter.
Thank you very much for the link. As soon as I have some time I will
study your code
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Inserting LaTex expressions using a filter fails
@ 2021-01-05 21:58 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-01-05 21:58 UTC (permalink / raw)
To: Mart van de Wege; +Cc: orgmode
Hello,
Mart van de Wege <mvdwege@gmail.com> writes:
> I'm trying to replace U+00BD in an org buffer with \sfrac{1}{2} during
> export to LaTex, and obviously I'm doing something wrong, or I don't
> understand the documentation.
>
> I use the following code to set up the filter:
>
> #+BIND: org-export-filter-item-functions (latex-replace-half)
> #+BEGIN_SRC emacs-lisp :exports results :results none
>
> (defun latex-replace-half (text backend info)
> (when (org-export-derived-backend-p backend 'latex)
> (replace-regexp-in-string "½" "\\sfrac{1}{2}" text)))
> #+END_SRC
You must add a double escape character to the backslash:
...
(replace-regexp-in-string "½" "\\\\sfrac{1}{2}" text)))
...
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Inserting LaTex expressions using a filter fails
@ 2021-01-06 11:51 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-01-06 11:51 UTC (permalink / raw)
To: Mart van de Wege; +Cc: orgmode
Mart van de Wege <mvdwege@gmail.com> writes:
> Thanks!
>
> But see my answer to Nick Dokos on the list, that does not do anything
> either.
Try putting this variable in your .emacs with non-nil value:
(setq org-export-allow-bind-keywords t)
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Inserting LaTex expressions using a filter fails
@ 2021-01-06 12:24 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-01-06 12:24 UTC (permalink / raw)
To: Mart van de Wege; +Cc: orgmode
Mart van de Wege <mvdwege@gmail.com> writes:
> Kind of weird it's not mentioned in the docs though (at least not in
> the same section as export filters); if you're going to tell people that
> you can bind local functions to an org file, then it might be nice to
> point out that you do need to turn that on.
You're right. I think an addition could be proposed in the
documentation: for example, a footnote in the section `Defining filters
for individual files', since by default the variable
`org-export-allow-bind-keywords' has value nil.
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Inserting LaTex expressions using a filter fails
@ 2021-01-06 15:58 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-01-06 15:58 UTC (permalink / raw)
To: Mart van de Wege; +Cc: orgmode
Mart van de Wege <mart@vdwege.eu> writes:
> You're right. I looked up the variable, and there is only one mention
> in the docs, and that is about binding emacs variables locally to the
> org file buffer.
>
> Can I just clone the repo and prepare a patch?
As far as I know, you can create a diff and propose the patch here in
the list, opening a new thread, that includes in the mail subject
something like "[patch] etc"
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Possibility to copy text outside EMACS and send it to orgmode document
@ 2021-01-06 16:31 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-01-06 16:31 UTC (permalink / raw)
To: Gerardo Moro; +Cc: orgmode
Gerardo Moro <gerardomoro37@gmail.com> writes:
> Basically that: as I copy (Control-C) text from the browser (Chrome),
> I would like those copied sentences to be sent to a ordered list in an
> OrgMode document:
>
> - copied text 1
> - copied text 2
> - etc.
>
> Any ideas? This would be very useful.
> Thanks!
I don't know if it is exactly what you are looking for, but maybe you
might be interested in this extension for chrome and firefox that uses
org-protocol:
https://github.com/sprig/org-capture-extension
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Org to ConTeXt exporter?
@ 2021-01-09 17:42 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-01-09 17:42 UTC (permalink / raw)
To: Jason Ross; +Cc: orgmode
Hello, Jason,
Jason Ross <jasonross1024@gmail.com> writes:
> I recently had the same thought and I've started working on one.
> You can see it here:
>
> https://github.com/Jason-S-Ross/ox-context/
>
> It's no substitute for the LaTeX exporter but it implements a lot
> of the basics. I'm deriving from the LaTeX exporter but I have
> to override most of the transcoders so it may be better to start
> from scratch.
>
> Disclaimer: I'm learning elisp as I go, so please excuse the
> rough edges.
That's great news! I've been testing it a bit and it works very good. Of
course, I encourage you to keep up this excellent work.
Regards,
Juan Manuel
>
> Jason Ross
>
--
^ permalink raw reply [relevance 10%]
* Re: Region-based meta-notes
@ 2021-01-19 22:39 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-01-19 22:39 UTC (permalink / raw)
To: Lawrence Bottorff; +Cc: orgmode
Hello,
Lawrence Bottorff <borgauf@gmail.com> writes:
> So yes, simply being able to select regions and make side notes about
> them could give you a very fine level of control over metadata in a
> file. Is there such a thing in the Emacs/org-mode world?
Take a look at the org-marginalia package:
https://github.com/nobiot/org-marginalia
Regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: org-attach-git don't automatically commit changes
2021-01-31 13:16 10% ` Juan Manuel Macías
@ 2021-01-31 11:41 10% ` Juan Manuel Macías
1 sibling, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-01-31 11:41 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko <yantar92@gmail.com> writes:
> I think you misunderstood how org-attach-git works.
>
> org-attach-git is:
>
> ;; An extension to org-attach. If `org-attach-id-dir' is initialized
> ;; as a Git repository, then org-attach-git will automatically commit
> ;; changes when it sees them. Requires git-annex.
>
> So, it is not designed to work when your actual attachment directory is
> a git repo, but rather when org-attach-id-dir is a git repo (initialised
> manually).
Thanks for the explanation: it is clear that I had misinterpreted
`org-attach-id-dir'. Now it makes sense that it didn't work for me.
Anyway, I think the manual at that point is somewhat ambiguous and it
should be more precise, IMHO.
> So, I believe that org-attach-git should be updated. Probably,
> handling attachment dirs as individual git repos can be one of the
> ways to upgrade the current version.
I agree, I think this possibility makes a lot more sense.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: org-attach-git don't automatically commit changes
@ 2021-01-31 14:36 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-01-31 14:36 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko <yantar92@gmail.com> writes:
> What is more tricky is making sure that workflow for people using the
> old behaviour is not broken. Just changing to (org-attach-dir) will
> break existing git repos in org-attach-id-dir. This should also not be
> too hard (say, we can introduce a custom variable defaulting to old
> behaviour), but exact details may need to be discussed.
I agree: I think a custom variable with the current behavior by default
would be fine.
> In any case, if you provide a patch, it will encourage the org
> maintainers to join this discussion and proceed with changes.
OK, this week I will try to propose a patch here, and bring it up for
(possible) discussion. Thanks for the suggestions.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: http links translated to html : target "_blank"
@ 2021-02-01 21:01 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-02-01 21:01 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Uwe Brauer <oub@mat.ucm.es> writes:
> That is odd (maybe my org version is a bit rusty (master june 2020)
It's strange...
It should work fine for you (as long as you set
`org-export-allow-bind-keywords' as non-nil)
You can also try `org-export-filter-link-functions' instead of
`...-final-output-functions'.
Anyway, if the `#+attr_latex' solution works for you, then all is fine.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [question] lisp code in :results header arg.?
@ 2021-02-16 18:25 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-02-16 18:25 UTC (permalink / raw)
To: Berry, Charles; +Cc: orgmode
"Berry, Charles" <ccberry@health.ucsd.edu> writes:
> I think you might do better to use noweb chunks, viz.
>
> #+name: pre-amble
> #+begin_src latex :exports none
>
> \usepackage{luacode}
> \usepackage{fontspec}
> \directlua
> {
> [...]
> }
> }
> \setmainfont{Linux Libertine O}
> [RawFeature={+ktest}]
> #+end_src
>
> #+begin_src latex :noweb yes :results drawer
> ,#+LaTeX_HEADER: <<pre-amble>>
> #+end_src
>
>
> Evaluating the latter chunk (assuming `org-babel-load-languages' has (latex . t)) gives what I suspect you want.
wow, it works great! Many thanks. I did not know this use of noweb ...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: 'false' list item
@ 2021-02-21 14:49 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-02-21 14:49 UTC (permalink / raw)
To: Tim Cross; +Cc: orgmode
Hi,
Tim Cross <theophilusx@gmail.com> writes:
> If a line starts with a number, period and space, but that line is
> within a paragraph (i.e. no blank line above), then I don't think it
> should be interpreted as an enumerated list item. If this is what the OP
> is referring to, I would argue it is a bug. If it is a 'paragraph'
> starting with a number, period and space, then being interpreted as a
> list item would be 'normal'.
The problem occurs on the lines within a paragraph (no blank line
above). I have uploaded this screenshot:
https://gnutas.juanmanuelmacias.com/images/false-list-item.webm
It also happens with a clean startup.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: 'false' list item
@ 2021-02-21 22:25 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-02-21 22:25 UTC (permalink / raw)
To: Samuel Wales; +Cc: orgmode
Samuel Wales <samologist@gmail.com> writes:
> perhaps if there is no blank line above or below, then it could be not a list.
I think this solution would be fine, although plain paragraphs starting
with digit/letter + period + space would be false positives. Anyway,
some kind of highlighting in the items, a defined face as in
markdown-mode (markdown-list-face), would be also helpful.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: printing org table landscape on complete page
@ 2021-02-28 20:53 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-02-28 20:53 UTC (permalink / raw)
To: Andrés Ramírez; +Cc: orgmode
Hi,
You can use:
#+ATTR_LaTeX: :float sideways
which is exported to LaTeX with the sidewaystable environment (rotating
package).
And for the table to fit vertically on the page:
#+LaTeX_Header: \usepackage{tabularx}
#+ATTR_LaTeX: :float sideways :environment tabularx :width \textheigtht
Regards,
Juan Manuel
Andrés Ramírez <rrandresf@gmail.com> writes:
> Hi.
>
> I want to print from emacs an org-table like this one:
>
> |-------------+-----------+----------+-----------+----------+---------|
> | DURATION | MONDAY | TUESDAY | WEDNESDAY | THURSDAY | FRIDAY |
> |-------------+-----------+----------+-----------+----------+---------|
> | 08:30-09:30 | CyT | RELIGION | GERMAN | ENGLISH | ENGLISH |
> |-------------+-----------+----------+-----------+----------+---------|
> | 09:50-10:50 | COMUNICAT | DPCC | COMUNICAT | COMUNIC | CyT |
> |-------------+-----------+----------+-----------+----------+---------|
> | 11:10-12:10 | COMPUTERS | CyT | E.FISICA | ART | GERMAN |
> |-------------+-----------+----------+-----------+----------+---------|
> | 12:30-13:30 | TUTORIA | MATH | MATH | CC.SS | MATH |
>
> on landscape on the content should enlarge to cover the full-page.
>
> Any ideas?
>
> Andrés Ramírez
>
^ permalink raw reply [relevance 10%]
* Re: Syntax Proposal: Multi-line Table Cells/Text Wrapping
@ 2021-03-18 15:15 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-03-18 15:15 UTC (permalink / raw)
To: Atlas Cove; +Cc: orgmode
Atlas Cove <Atlas48@gmx.com> writes:
> In effect, yes. I'm proposing it as a syntax addition to make it easier to read, export, and manage, larger tables.
> I'm unsure if this would fit within the scope of org, but [[https://github.com/RedBug312/markdown-it-multimd-table][other projects]],
> like [[https://fletcher.github.io/MultiMarkdown-6/MMD_Users_Guide.html#tables][MultiMarkdown]] have exactly what I want in terms of table use.
> Since I've already proposed a single, solitary addition to org, we won't discuss all of those nice features /just/ yet!
Thanks for your clarification. I strongly support your proposal.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Syntax Proposal: Multi-line Table Cells/Text Wrapping
@ 2021-03-19 8:44 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-03-19 8:44 UTC (permalink / raw)
To: tomas; +Cc: orgmode
Hi Tomas,
<tomas@tuxteam.de> writes:
> If the aim is "just rendering in Org" and "breaks have no special
> meaning" (so each render is allowed to re-flow), then your approach
> makes sense (I think Org table has something like that: you can
> set the column width and shrink/expand the column appropriately.
> Personally, I've found that somewhat awkward, so I don't use it,
> but OTOH I'm not a heavy table user: perhaps that's why).
I was writing yesterday some rudimentary code (just a proof of concept)
and I've made this screencast:
https://lunotipia.juanmanuelmacias.com/edit-cell-sample-2021-03-19_09.29.17.mp4
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Items with emphasis marks are not sorted properly in a list
@ 2021-03-22 21:59 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-03-22 21:59 UTC (permalink / raw)
To: orgmode
Hi,
Consider this list:
- vol.
- adj.
- /circa/
- /vid./
If I evaluate `(org-sort-list t ?a)', it seems that `org-sort-list'
doesn't sort correctly items that contain an emphasis mark:
- /circa/
- /vid./
- adj.
- vol.
I don't know if there is any solution to this, or if I'm doing something wrong...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: "Org" source blocks and minted
@ 2021-03-24 4:18 10% ` Juan Manuel Macías
1 sibling, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-03-24 4:18 UTC (permalink / raw)
To: Michael Gauland; +Cc: orgmode
Hi Mike,
Michael Gauland <mikelygee@gmail.com> writes:
> I want to include an "org" source block in a document as an example,
> and have it formatted with minted. Unfortunately, minted doesn't seem
> to recognize "org" as a language,and the block is missing in the
> resulting PDF. For the moment, I've changed this to a "text" source
> block, but it would be nice to have syntax highlighting in the export.
>
> Have any of you done this, or something similar?
>
> Kind regards,
> Mike
>
You can write your own pygments lexer:
https://pygments.org/docs/lexerdevelopment
But it seems that someone already did the work of writing a lexer for
Org Mode:
https://github.com/or/pygments-orgmode-lexer
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: "Org" source blocks and minted
@ 2021-03-26 11:55 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-03-26 11:55 UTC (permalink / raw)
To: Timothy; +Cc: orgmode
Hi Timothy,
I really like your approach. And it is org/emacscentric! Minted has
never quite convinced me, and gives me some trouble with certain
packages in LuaLaTeX that I have not been able to solve. Thank you for
this promising alternative.
Best regards,
Juan Manuel
Timothy <tecosaur@gmail.com> writes:
> Juan mentioned an Org lexer exists, but another approach that may be of
> interest is using Emacs' own font-lock. I wrote a package that's like
> HTMLize but works with LaTeX and currently have it sitting in my config.
>
> I plan on submitting a patch to Org at some point on this, but for now:
> - https://github.com/tecosaur/engrave-faces
> - https://tecosaur.github.io/emacs-config/config.html#pretty-code-blocks
>
> Sample output: all the code blocks in
> https://tecosaur.github.io/emacs-config/config.pdf
>
> Since this uses Emacs' font-lock, this means that you can use any
> language that you have a syntax-highlighting-mode for :)
^ permalink raw reply [relevance 10%]
* Re: About exporting
@ 2021-03-31 18:56 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-03-31 18:56 UTC (permalink / raw)
To: orgmode
Martin Steffen <msteffen@ifi.uio.no> writes:
> [...] And last not least; if I ``compile'' the document (firing off latex,
> bibtex, or index or whatever), the compilation runs in the background.
> As far as I do that in org (exporting to pdf), it blocks emacs. Not
> that it's a huge delay even, at least for smaller documents, I hate
> that an editor or some tool is slower than me, it gets on my nerves if
> the computer slows me down.
There is the async-export (C-a) option in org-export-dispatcher.
Anyway, I usually use the latexmk script a lot, even with Org
(combined with Org Publish: I export sub-documents to *tex from Org and
compile later with latexmk the master document. latexmk with the -pvc
options is wonderful.
I agree that AUCTeX is excellent; maybe (IMHO) the best LaTeX editor out
there.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Including Email Address in the Reply in Mailing-list
@ 2021-04-02 23:45 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-02 23:45 UTC (permalink / raw)
To: Tim Cross; +Cc: orgmode
Tim Cross writes:
> I have no issue with this suggestion and am happy to try and comply.
>
> The challenge for many will be that they either
>
> - need to remember to remove the email details manually (line/header
> automatically added by mail client) while sorting out either
>
> - how to modify mail client for all replies (may not be appropriate for
> non-ML replies), or
>
> - how to modify mail client for just ML replies
> [...]
For Gnus users, one possibility might be:
(defun my-gnus-reply-ml ()
(interactive)
(let*
((message-citation-line-format "%N writes:\n")
(message-citation-line-function 'message-insert-formatted-citation-line))
(gnus-article-reply-with-original)))
...And then assign any free key to gnus-article-mode-map
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: How to get a table into a variable in a shell code block?
@ 2021-04-03 19:01 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-03 19:01 UTC (permalink / raw)
To: Greg Minshall; +Cc: orgmode
Hi Greg and William,
Greg Minshall writes:
> William,
>
> try
>
> #+begin_src shell :results output :var n=numbers
> echo ${n[1]}
> #+end_src
>
> cheers, Greg
I don't know if I'm saying something wrong, but wouldn't it be better
this way?:
#+begin_src shell :results output :var n=numbers
echo ${n[@]}
#+end_src
echo ${n[1]} returns the second element (two) of the list (0, returns
one and 2 returns three)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: how to export (latex) a image without using figure
@ 2021-04-04 11:17 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-04 11:17 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Hi Uwe,
Try:
#+ATTR_LaTeX: :float nil
#+CAPTION: La función La función $x^2 e^{-\alpha x} = \frac{1}{\alpha}$, $\alpha=-\ln(1-p)$ con $p=0.01$ con $p=0.3$
[[./images/dfp_03.png]]
Best regards,
Juan Manuel
Uwe Brauer writes:
> Hi
>
> Currently
>
> #+CAPTION: La función La función $x^2 e^{-\alpha x} = \frac{1}{\alpha}$, $\alpha=-\ln(1-p)$ con $p=0.01$ con $p=0.3$
> #+NAME: fig:plotcalor23
>
> [[./images/dfp_03.png]]
>
> Gets translated to
>
> \begin{figure}[htbp]
> \centering
> \includegraphics[width=.9\linewidth]{./images/dfp_03.png}
> \caption{\label{fig:plotcalor23}La función La función \(x^2 e^{-\alpha x} = \frac{1}{\alpha}\), \(\alpha=-\ln(1-p)\) con \(p=0.01\) con \(p=0.3\)}
> \end{figure}
>
> For reasons that needs a longer explanation I would need.
>
>
>
> \includegraphics[width=.9\linewidth]{./images/dfp_03.png}
> \captionof{figure}{\label{fig:plotcalor23}La función La función \(x^2 e^{-\alpha x} = \frac{1}{\alpha}\), \(\alpha=-\ln(1-p)\) con \(p=0.01\) con \(p=0.3\)}
>
>
> How can this be achieved?
>
> Thanks
>
> Uwe Brauer
>
>
>
>
^ permalink raw reply [relevance 10%]
* Re: First steps exporting to tex
@ 2021-04-04 11:36 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-04 11:36 UTC (permalink / raw)
To: Ypo; +Cc: orgmode
Ypo writes:
> I've already tried that. But it doesn't seem to understand the HOME
> directory ~~/~. At least at Windows.
I haven't touched Windows for a thousand years :-), but maybe this thread
can help you:
https://stackoverflow.com/questions/13584118/how-to-write-a-path-with-latex
best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Choosing a LaTeX Compiler (my predilection for LuaTeX)
@ 2021-04-06 20:09 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-06 20:09 UTC (permalink / raw)
To: tomas; +Cc: orgmode
Hi Tomas,
tomas@tuxteam.de writes:
> AFAIK Lua(La)Tex can output dvi (and Juan Manuel's answer implies
> thati, too). Either via the option --output-format=dvi or invoking
> it as "dviluatex".
>
> But perhaps I missed something.
Yes, the first option I have commented in my previous mail (setq
luamagick etc ...) converts from pdf to png via 'convert' (imagemagick);
in the second option (setq luasvg etc ...) compiles with the option
`-output-format dvi' and then the converter is dvisvgm.
Best regards,
Juan Manuel
https://juanmanuelmacias.com/
^ permalink raw reply [relevance 10%]
* Re: Choosing a LaTeX Compiler (my predilection for LuaTeX)
@ 2021-04-07 19:52 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-07 19:52 UTC (permalink / raw)
To: physiculus; +Cc: orgmode
Hello again,
physiculus writes:
> Yes that works!
> usually i do not use imagemagick. I use graphicsmagick, but ido not know
> how i have to set the right command line.
> SVG does nothing.
> Very sad :-(
> I want to use this because of quality reasons.
> Do you know, how i can test svg?
the dvisvgm option with luatex is definitely wrong, since dvisvgm does
not support opentype fonts. Sorry for having you confused with my other
snippet. The good news, it seems, is that dvisvgm will support opentype
fonts as of version 2.10, which I assume the next version of texlive
will include it. The actual version is 2.9.1 (command dvisvgm
--version).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [Patch] to correctly sort the items with emphasis marks in a list
@ 2021-04-12 13:50 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-12 13:50 UTC (permalink / raw)
To: orgmode
Nicolas Goaziou writes:
> I cannot reproduce it. With your initial list, and a minimal init file,
> I get:
>
> - /a/
> - a
> - b
> - /v/
>
> Could you try with a minimal Emacs, too?
That's weird ... I have tried launching emacs -q in a virtual machine,
and I keep getting the wrong result (git version, master branch):
- /a/
- /v/
- a
- b
I have tried with the typical keyboard shortcut and also with M-: and
evaluating (org-sort-list t? a nil nil nil)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [Patch] to correctly sort the items with emphasis marks in a list
@ 2021-04-12 23:18 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-04-12 23:18 UTC (permalink / raw)
To: Ypo; +Cc: orgmode, Nicolas Goaziou
Hi Ypo,
Ypo writes:
> This is my result after doing "org-sort-list a":
>
> - /a/
> - /v/
> - a
> - b
>
> Regards
Thanks for trying. So it seems that you can reproduce the problem as
well... I wonder if anyone else is able to reproduce it, preferably in a
minimal emacs.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [PATCH] Startup option to separate macros arguments with an alternative string
@ 2021-04-22 13:46 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-22 13:46 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: orgmode
Hi Nicolas,
Thank you very much for your suggestions.
Nicolas Goaziou writes:
> This change will need to be tested extensively in "test-org-element.el"
> and "test-org-macro.el".
>
> However, as a start, I suggest starting a new thread about a suggested
> change in the syntax, with a clear title, examples, and code. Then we
> can leave time for users to react to it.
>
> Do you want to take care of it?
Ok, I agree. Next week I will start a new thread for submit this new
proposal.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [tip] search this mailing list with helm-surfraw
@ 2021-04-27 20:20 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-27 20:20 UTC (permalink / raw)
To: Bastien; +Cc: orgmode
Hi Bastien,
Bastien writes:
> Neat!
>
> You might want to write another one for the public-inbox archive:
>
> E.g. https://orgmode.org/list/?q=Juan+Manuel+Mac%C3%ADas
I was unaware that searches in the public-box archive are faster...
Thank you very much for the advice :-)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [patch] to allow org-attach-git to handle individual repositories
@ 2021-04-28 13:42 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-28 13:42 UTC (permalink / raw)
To: Bastien; +Cc: orgmode
Hi Bastien,
Bastien writes:
> It looks good but it is significative enough to require you to sign
> the FSF copyright assignment. If you're willing to go through this
> (which will secure future contributions too), please see:
Thanks for the advice. I just signed and sent the FSF copyright
assignment.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: How to create a macro that inserts multiline text with :B_ignoreheading: tag?
@ 2021-04-30 20:40 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-04-30 20:40 UTC (permalink / raw)
To: Richard Stanton; +Cc: orgmode
Hi Richard,
Richard Stanton <rhstanton@berkeley.edu> writes:
> I’d like to define a macro called, say, articletext, to insert this
> header into my document before exporting to LaTeX, so the org file
> would look something like this:
>
> {{{article text}}}
> This text appears only in the article version.
Macro definitions do not allow spaces.
You can try something like:
#+MACRO: article_text (eval (concat "*** More explanation coming" "\s" ":B_ignoreheading:\n:PROPERTIES:\n:BEAMER_env: ignoreheading\n:END:"))
{{{article_text}}}
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Multilingual support (proposals and state of the question)
@ 2021-05-17 18:10 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-05-17 18:10 UTC (permalink / raw)
To: Denis Maier; +Cc: orgmode
Hi Denis,
Denis Maier writes:
> Why not add a :lang property to other blocks as well?
>
> #+begin_quote :lang en
> this is english.
> #+end_quote
>
> WDYT?
>
> Denis
It's an interesting possibility. However, I think that the advantage of
Org src blocks is that you can include anything you want, even quote
blocks. And you also have org-edit-special...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [org-footnote--allow-reference-p]
@ 2021-05-20 10:17 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-05-20 10:17 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Hi Uwe,
Uwe Brauer writes:
> It seems that the function org-footnote--allow-reference-p
> is the culprit, but which places are *forbidden* the doc string does not
> say much.
If you mean to insert a note in an empty cell, you can insert just
before the note mark a zero width space (M-x insert-char RET 200b RET)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [org-footnote--allow-reference-p]
@ 2021-05-20 10:38 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-05-20 10:38 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Uwe Brauer writes:
> Ah! That was it, thanks!
> I think the documentation of org-footnote-action
> could be a bit more explicit and cover this case.
In the manual the use of the zero width space character is in the section
'Escape Character'. Perhaps it would be nice to add more usage examples. A
very typical (and practical) use is when you want to emphasize a part of a
word:
with /meta/<zero-with-space>literature you get (LaTeX)
\emph{meta}literature instead of the literal /meta/literature...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Smart quotes not working correctly with single quotes
@ 2021-05-28 20:37 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-05-28 20:37 UTC (permalink / raw)
To: Andreas Gösele; +Cc: orgmode
Hi Andreas,
Andreas Gösele writes:
> I tried it, but it doesn't work. It leaves the simple quotes
> untouched. Did you test it and did it work then?
I forgot to tell you (sorry!) that you should set the variable
`org-export-allow-bind-keywords' as non-nil:
(setq org-export-allow-bind-keywords t)
If you are going to use that filter in many documents, you can better add to your
~ /.emacs:
(add-to-list 'org-export-filter-final-output-functions 'single-quote-filter)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: TMIO Pre-release, request for feedback
@ 2021-05-30 19:42 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-05-30 19:42 UTC (permalink / raw)
To: Timothy; +Cc: orgmode
Hi Timothy,
Timothy writes:
> Hi Everyone,
>
> As we arrive at the end of May, I'm about to publish the 3rd issue of
> /This Month in Org/. I thought I'd share the current draft with the list
> the day before I publish to so that those of you who are interested have
> the chance to point out any errors, let me know if there's anything I
> haven't covered that you'd like to see, along with any other feedback
> you may have.
>
> For the next day, you can find the draft at:
> https://blog.tecosaur.com/tmio/DRAFT-2021-05-31.html
> and then once published it will live at:
> https://blog.tecosaur.com/tmio/2021-05-31.html
Thank you very much for your excellent work, and for all the effort and
time you put in it. I think your /This Month in Org/ conveys, above all,
something very valuable that all Org users share: an immense and
uncompromising enthusiasm for Org and Emacs :-D
I like the design of the site: very clear and readable.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: suggestion to change default org-latex-pdf-process to latexmk
@ 2021-06-01 15:52 10% ` Juan Manuel Macías
1 sibling, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-01 15:52 UTC (permalink / raw)
To: Bruce D'Arcus; +Cc: orgmode
Hi Bruce,
Bruce D'Arcus writes:
> So what do LaTeX users think about changing the default for
> "org-latex-pdf-process" to "latexmk"?
It sounds like a good idea to me. In fact I have `org-latex-pdf-process'
set to latexmk in my ~ /.emacs (with the option to always compile with
LuaTeX).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: suggestion to change default org-latex-pdf-process to latexmk
@ 2021-06-02 8:40 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-02 8:40 UTC (permalink / raw)
To: Stefan Nobis; +Cc: orgmode
Stefan Nobis writes:
> An alternative may be to use latexmk only if citations are found (new
> feature, new dependencies). Or a wrapper that checks whether latexmk
> is available and works (e.g. trying to call "latexmk --version") and
> falls back to the old routine of manually running the engine and
> bibtex/biber if necessary.
Another possibility would be to add to the documentation all the
instructions needed on how to properly configure `org-latex-pdf-process'
with latexmk, for those users who wish to use bibtex or biblatex.
Although latexmk is also useful for many packages that need multiple
compilations, indexes, etc.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* [bug?] org-link-set-parameters: when `:display 'full', link face is applied only in description part
@ 2021-06-03 21:11 10% Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-06-03 21:11 UTC (permalink / raw)
To: orgmode
Hi all,
In master:
if I do:
(org-link-set-parameters "foo"
:display 'full
:face '(:foreground "chocolate" :weight bold :underline t))
and then:
[[foo:target][description]]
the face parameter is only applied in the description part.
Expected result: shouldn't the face be applied to the entire link?
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [PATCH] Allow LaTeX reference command (\ref) to be customised
@ 2021-06-06 18:29 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-06 18:29 UTC (permalink / raw)
To: Timothy; +Cc: orgmode
Hi Timothy,
Timothy writes:
> I've started doing some more cross-referencing in documents exported to
> LaTeX, and a hardcoded use of \ref has begun to stand out to me as a
> rather annoying thing. Hypperef provides \autoref for adding helpful
> prefixes (section, figure, etc.), and there are other packages which one
> may want to use to generate 'clever' references (like cleveref with
> \cref).
>
> As such, I think that the hardcoded \ref should actually be turned into
> a customisable format string, which is what the attached patch does.
I think it's a great idea. There are many options in LaTeX to manage
cross references, beyond the standar \ref. I use the varioref package a
lot (https://www.ctan.org/pkg/varioref).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: literate programming, development log -- ideas?
@ 2021-06-07 12:00 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-07 12:00 UTC (permalink / raw)
To: Greg Minshall; +Cc: orgmode
Hi Greg,
Greg Minshall writes:
> but i also feel a need for something that might be called a lab
> notebook, a development log, of ideas, including dead ends, i pursue
> during the development process, with links, etc.. but, i'm not really
> sure how to structure this bit, how to integrate it in the rest of the
> .org file -- i.e., as a separate heading, or related to the code section
> that (originally) was under development when the notes were created.
> or...? etc.
I use `org-add-note' a lot, in a wide variety of scenarios. According to their
docstring:
"Add a note to the current entry.
This is done in the same way as adding a state change note."
And I've set (setq org-log-into-drawer t)
On the other hand, maybe you can find interesting the org-marginalia package:
(https://github.com/nobiot/org-marginalia).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* org-critical-edition (a package for philologists and classicists)
@ 2021-06-07 13:09 10% Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-07 13:09 UTC (permalink / raw)
To: orgmode
Hi all,
I have uploaded the (very) initial version of my package
org-critical-edition:
https://gitlab.com/maciaschain/org-critical-edition
This package lets you prepare a philological critical edition in Org
Mode. The natural output is LaTeX with the reledmac package
(https://www.ctan.org/pkg/reledmac).
(For those who are not philologists, this is an example of critical
edition that I typesetted recently: https://imgur.com/a/drqCib5)
Feedback welcome!
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Failure to resolve internal links on ox-html export?
@ 2021-06-11 18:31 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-06-11 18:31 UTC (permalink / raw)
To: Tim Visher; +Cc: orgmode
Hi Tim,
Try setting this variable to non-nil:
(setq org-export-with-broken-links t)
Best regards,
Juan Manuel
Tim Visher writes:
> Hi Everyone,
>
> I'd like to be able to link to various areas of a large wiki file I
> maintain for when I'm looking at an entry in emacs. However, I will
> often email exported subtrees and when I do that if I have a link to a
> heading that's outside the current subtree it fails with a
> `user-error: Unable to resolve link: …`, I assume because the export
> tree doesn't contain that heading.
>
> Is there any way to tell the exporter to simply make those into plain
> text _or_ to simply ignore the error?
>
> Thanks in advance!
>
> --
>
> In Christ,
>
> Timmy V.
>
> https://blog.twonegatives.com
> http://five.sentenc.es
>
^ permalink raw reply [relevance 10%]
* Re: Write Markdown in Org mode
@ 2021-06-12 15:51 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-12 15:51 UTC (permalink / raw)
To: leo; +Cc: orgmode
Hi Leo,
leo writes:
> Good to know. I’m not too keen to learn yet another text markup language, but I might give org mode a try…
It's worth a try! Org markup language is very similar to Markdown. My
advice is that you take from Org only what you need, because Org has so
many features that at first it can saturate you. A Recommended initial
reading may be the compact guide, which gives you a pretty global vision
without going too deep in each aspect: https://orgmode.org/guide/
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: appearance of list as results from evaluating code blocks
@ 2021-06-23 19:43 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-23 19:43 UTC (permalink / raw)
To: Johannes Brauer; +Cc: orgmode
Hi Johannes,
Johannes Brauer writes:
> Hi!
> Evaluating a code block containing a list expression using org-babel for elisp or Clojure, for example
> (list 1 2 3)
> I get
> #+RESULTS:
> | 1 | 2 | 3 |
> I would prefer
> #+RESULTS:
> ( 1 2 3 )
>
> Is it possible to get this.
Try
#+begin_src emacs-lisp :results raw
(list 1 2 3)
#+end_src
#+RESULTS:
(1 2 3)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Virtually prefix headlines according to content
@ 2021-06-29 13:34 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-06-29 13:34 UTC (permalink / raw)
To: Rodrigo Morales; +Cc: orgmode
Rodrigo Morales writes:
> What I would like to know is whether it is possible to format a headline
> by taking into consideration the properties it has. For example, in this
> specific scenario, I would like to make all headlines that have a
> "GITHUB" to show "GH" before the actual headline (the content would look
> like this).
You can define a function with `org-map-entries' that adds (for example) a
tag :github: to all headers with the property GITHUB:
#+begin_src emacs-lisp
(defun add-github-tag ()
(interactive)
(org-map-entries (lambda ()
(save-restriction
(save-excursion
(org-narrow-to-subtree)
(goto-char (point-min))
(end-of-line)
(insert " :github:"))))
"+GITHUB={.+}"))
(add-hook 'org-mode-hook #'add-github-tag)
#+end_src
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: convert subtree or nested list to table
@ 2021-07-05 20:01 10% ` Juan Manuel Macías
[not found] ` <CAN_Dec8iqKS+3qvjkYvQxovegnEzqR_rra0Q-ZA9baPz1mXDAA@mail.gmail.com>
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-07-05 20:01 UTC (permalink / raw)
To: Matt Price; +Cc: orgmode
Hi Matt,
Matt Price writes:
> I have to write a number of text-heavy documents which need to be
> delivered as tables with wrapped paragraphs in most cells. Working
> directly in table format is pretty arduous and uncomfortable. Has
> anyone ever written a function to accept a list or subtree as input
> and process it into a table?
>
> If anyone has done something similar, I'd love some tips!
Some time ago I wrote some functions for my personal use that allow edit
table cells (with a lot of text and/or paragraphs) in a dedicated
buffer. I don't know if something like that is what you are looking for,
but if you are interested, I can clean up the code a bit and upload it
here.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: convert subtree or nested list to table
@ 2021-07-07 18:27 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-07-07 18:27 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Hi Uwe, thanks for testing the code.
Uwe Brauer writes:
> I am running (a couple of week old) GNU emacs master and org-mode git
> master. I even restarted my emacs session
>
> What do I miss?
I can't reproduce the issue (GNU Emacs 27.2 and org git master). In my
case everything works as expected (taking into account that with this
code of mine the expectations have to be modest :-).
I will do a test on Emacs master...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: org-mode export to (latex) PDF
@ 2021-07-10 13:52 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-07-10 13:52 UTC (permalink / raw)
To: Jean-Christophe Helary; +Cc: orgmode
Hi Jean-Christophe,
Jean-Christophe Helary writes:
> I guess it is an issue with the Latex backend and could have been solved with the proper Latex settings, but it seems weird that the default settings do not allow for out-of-the-box multilingual support.
I agree with you that Org should have multilingual support. A few months
ago I started this thread here, with some proposals:
https://orgmode.org/list/87o8d95pvo.fsf@posteo.net/
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: TMIO July Post: Introducing Citations
@ 2021-08-02 7:23 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-08-02 7:23 UTC (permalink / raw)
To: Timothy; +Cc: orgmode
Hi Timothy,
Timothy writes:
> Hi Everyone,
>
> Just letting you know that on my blog TMIO (This Month In Org) I've just
> published the July post. I've decided to focus entirely on citations
> this time :)
>
> Should this be of interest, here it is:
> https://blog.tecosaur.com/tmio/2021-07-31-citations.html
Thank you very much for this comprehensive and very useful post: the
best way to start my summer vacation! :-)
And many thanks to those who have developed this interesting and
promising new Org feature.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: return column from table as a column
@ 2021-08-13 14:47 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-08-13 14:47 UTC (permalink / raw)
To: Roger Mason; +Cc: orgmode
Hi Roger,
It's a dirty solution, but you can try:
#+name: s1
| scale | scale1 | scale3 | jid |
| - | 1.00402 | 0.952329 | 1632 |
| - | 1.00402 | 0.962247 | 1633 |
#+begin_src emacs-lisp :var data=s1 col=3
(let* ((column (mapcar (lambda (r) (format "%s" (nth col r))) data)))
(mapcar 'list column))
#+end_src
#+RESULTS:
| jid |
| 1632 |
| 1633 |
Best regards,
Juan Manuel
Roger Mason writes:
> Hello,
>
> I need to extract a column from a table to use as input to a source
> block. I want the extracted column to be returned as a column but it is
> returned as a row. The following illustrates the problem:
>
> #+name: s1
> | scale | scale1 | scale3 | jid |
>
> | - | 1.00402 | 0.952329 | 1632 |
> | - | 1.00402 | 0.962247 | 1633 |
>
> #+begin_src emacs-lisp :var data=s1[,3]
> data
> #+end_src
>
> #+RESULTS:
> | jid | 1632 | 1633 |
>
> I want:
>
> | jid |
> | 1632 |
> | 1633 |
>
> Is there some means of changing 'data=s1[,3]' to accomplish this?
>
> Thanks,
> Roger
>
> GNU Emacs 27.2 (build 1, amd64-portbld-freebsd11.4, X toolkit, cairo
> version 1.16.0, Xaw3d scroll bars)
>
> Org mode version 9.2.3 (release_9.2.3-390-gfb5091 @
> /home/rmason/.emacs.d/org-git/lisp/)
>
^ permalink raw reply [relevance 10%]
* Re: Custom function for killing the thing at point
@ 2021-08-13 22:46 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-08-13 22:46 UTC (permalink / raw)
To: Rodrigo Morales; +Cc: orgmode
Hi Rodrigo,
Thanks for sharing, it seems interesting and useful. But I think this
function is missing in your post: `my/kill-new'.
Best regards,
Juan Manuel
Rodrigo Morales writes:
> I just created this function for copying the thing under the cursor (it
> works for some #+BEGIN blocks and links). I think it would be useful for
> others, so I'm creating this post for getting feedback on the Elisp code
> and sharing it to those interested.
>
> #+BEGIN_SRC elisp
> (defun my/org-kill-thing-at-point ()
> "Kill the thing at point.
>
> The following things are currently supported
>
> - #+BEGIN_SRC <<any>>
> - #+BEGIN_EXPORT <<any>>
> - #+BEGIN_EXAMPLE <<any>>
> - #+BEGIN_COMMENT
> - Org links (the description is not copied)"
> (interactive)
> (let* (content
> (element (org-element-context))
> (type (org-element-type element)))
> (cond ((or (eq type 'src-block)
> (eq type 'export-block)
> (eq type 'example-block)
> (eq type 'comment-block))
> (setq content (plist-get (cadr element) :value)))
> ((eq type 'link)
> (setq content (plist-get (cadr element) :raw-link)))
> (t
> (error "The element at point couldn't be copied.")))
> (my/kill-new content)))
> #+END_SRC
>
> #+BEGIN_SRC elisp
> (define-key org-mode-map (kbd "C-c c") 'my/org-kill-thing-at-point)
> #+END_SRC
>
^ permalink raw reply [relevance 10%]
* Re: how to get multi-line author in ODT export?
@ 2021-08-27 1:46 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-08-27 1:46 UTC (permalink / raw)
To: John Kitchin; +Cc: orgmode, Eric S Fraga
Hi John,
you're welcome. I realized that in these lines of the meta.xml file:
<dc:creator> ... </dc:creator>
<meta:initial-creator> ... </meta:initial-creator>
line breaks can be achieved simply by adding a new line without marks (as
discussed in this thread:
https://stackoverflow.com/questions/10917555/adding-a-new-line-break-tag-in-xml/10923392)
Best regards,
Juan Manuel
John Kitchin writes:
> That is really nice, thanks for sharing it!
> John
>
> -----------------------------------
> Professor John Kitchin (he/him/his)
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>
> On Thu, Aug 26, 2021 at 12:55 PM Juan Manuel Macías
> <maciaschain@posteo.net> wrote:
>
> Hi again,
>
> Another simpler approach, with a filter:
>
> #+TITLE: The kessel run in 12 parsecs
> #+AUTHOR: Han Solo !!! Chewbacca !!! Lando Calrissian
>
> #+BIND: org-export-filter-plain-text-functions (author-lb-filter)
> #+begin_src emacs-lisp :exports results :results none
> (defun author-lb-filter (text backend info)
> (cond ((org-export-derived-backend-p backend 'odt)
> (replace-regexp-in-string "!!!" "\n" text))
> ((org-export-derived-backend-p backend 'latex)
> (replace-regexp-in-string "!!!" "\\\\\\\\" text))))
> #+end_src
>
> Content...
>
> Best regards,
>
> Juan Manuel
>
> Juan Manuel Macías writes:
>
> > Hi Eric,
> >
> > I think the problem is in this two lines of `org-odt-template',
> that
> > creates the meta.xml file inside the odt file:
> >
> > (format "<dc:creator>%s</dc:creator>\n" author)
> > (format "<meta:initial-creator>%s</meta:initial-creator>\n"
> author)
> >
> > Perhaps, modifying them like this:
> >
> > (format "<dc:creator><![CDATA[%s]]></dc:creator>\n"
> (replace-regexp-in-string "\\\\\\\\" "\n" author))
> > (format "<meta:initial-creator><![CDATA
> [%s]]></meta:initial-creator>\n" (replace-regexp-in-string
> "\\\\\\\\" "\n" author))
> >
> > We could do this in our documents:
> >
> > #+AUTHOR: Han Solo \\ Chewbacca
> >
> > (little tested)
> >
> > Best regards,
> >
> > Juan Manuel
> >
> > Eric S Fraga writes:
> >
> >> So, as usual, I answer my own question, sort of.
> >>
> >> The problem is that org exports the author text enclosed within
> a
> >> special directives, specifically:
> >>
> >> (format "<text:initial-creator>%s</text:initial-creator>"
> author))
> >>
> >> New line directives are not allowed within this declaration, it
> >> seems. Removing (manually) the initial-creator directive then
> works.
> >>
> >> So, my question would be: is this text:initial-creator tagging
> >> necessary? If not, can we remove it? The OpenDocument schema
> is vague
> >> about whether this is necessary. If we cannot remove it, i.e
> if
> >> initial-creator is required in the document, could it be put in
> >> separately (as a meta:initial-creator tag) so that the author
> field can
> >> be more general?
> >>
> >> I am *not* an ODT expert of any sort. But it is my route to
> Word
> >> documents when the need arises (which is luckily seldom).
> >>
> >> Anyway, no panic: I can simply manually edit the odt file just
> before
> >> the final processing...
> >>
> >> Thank you,
> >> eric
> >
> >
>
^ permalink raw reply [relevance 10%]
* Re: pygments support
@ 2021-08-27 13:49 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-08-27 13:49 UTC (permalink / raw)
To: Yuchen Pei; +Cc: orgmode
Hi Yuchen,
I only know this one, but haven't tried it:
https://github.com/or/pygments-orgmode-lexer
Best regards,
Juan Manuel
Yuchen Pei writes:
> Hello,
>
> I was playing with my cgit setup when I noticed that pygments does not
> support org mode syntax highlighting[1].
>
> Just wondering if anyone has worked on it, or if there's any
> "unofficial" org mode component (lexer?), before I go ahead and
> try to write my own.
>
> [1]: https://pygments.org/languages/
^ permalink raw reply [relevance 10%]
* Re: [ANN] org-ql 0.6 released
@ 2021-09-22 12:10 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-09-22 12:10 UTC (permalink / raw)
To: Adam Porter; +Cc: orgmode
Hi Adam,
Thank you very much for this great package. I could no longer live without
org-ql/helm-org-ql :-)
Best regards,
Juan Manuel
Adam Porter writes:
> Hi friends,
>
> FYI, I just released version 0.6 of org-ql. Please see the changelog
> here:
>
> https://github.com/alphapapa/org-ql#06
^ permalink raw reply [relevance 10%]
* Re: [PATCH] Fix some typos
@ 2021-09-22 20:18 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-09-22 20:18 UTC (permalink / raw)
To: Max Nikulin, Marco Wahl; +Cc: orgmode
Hi all:
Max Nikulin writes:
> Please, forgive my ignorance of Shakespeare's poetry.
>
> On 17/09/2021 17:05, Marco Wahl wrote:
>>> On 17/09/2021 04:40, Stefan Kangas wrote:
>>
>>>> Please find attached another clean-up patch that fixes a small
>>>> number of typos. > > Thou shall not change "memeory" to "memory" tho
> I think, a bit more is required to avoid recurring attempts to change
> spelling if you would like to see such variant. Static code analyzers
> usually have a feature that allows to ignore specific warning at a
> particular line, see e.g.
> https://flake8.pycqa.org/en/latest/user/violations.html#in-line-ignoring-errors
> for Python's flake8.
>
> Maybe "LocalWords:" could do a similar trick for ispell.el at least
> for the whole file. Unsure if it is possible to add an exception for
> the quote only.
>
> However there is namely "memory" in the "1609 Quarto", see e.g.
> https://en.wikipedia.org/wiki/Sonnet_1 Web pages with the same variant
> as in the Org manual do not mention the source (particular edition). I
> hope, I just do not know what is considered as the canonical variant
> for not so old language.
I am not an expert on Shakespeare's poetry either, but as the author of
the patch where Sonnet 1 is included, I can say that 'memeory' is a typo
(sorry). At least I didn't use that word intentionally. I don't know if
there is any textual variant 'memeory', but in my case it is nothing
more than a simple typo :-).
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [PATCH] org.el: prevent partial fontification when a link is full displayed (was org-link-set-parameters: when :display full, etc.)
@ 2021-09-26 11:35 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-09-26 11:35 UTC (permalink / raw)
To: Bastien; +Cc: orgmode
Hi Bastien, thank you for your message,
Bastien writes:
> I could not apply the patch in the bugfix or main branch. Is it still
> relevant? If the bug is still here, feel free to send an updated patch.
I have consulted the log, and the patch was already applied by Nicololas
in commit:
40a20136d * | | Prevent partial fontification when a link is displayed full
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Possible bug? Combine emphasis marker faces?
@ 2021-09-28 16:54 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-09-28 16:54 UTC (permalink / raw)
To: Protesilaos Stavrou; +Cc: orgmode
Hi Protesilaos,
Protesilaos Stavrou writes:
> Is there a way to get composite styles? Such as bold and italic or
> verbatim and underline, etc.?
A somewhat dirty solution (without patching the code) could be
evaluating highlight-regexp, for example as a local variable:
#+begin_src emacs-lisp
(defface my/org-it-bold
'((t :slant italic :bold t))
"")
(highlight-regexp "\\([-[:space:]('\"{]\\|^\\)\\(\\([*/_+]\\)\\([*/_+]\\)\\([^[:space:]]\\|[^[:space:]].*?\\(?:
.*?\\)\\{0,15\\}[^[:space:]]\\)\\3\\)\\([-[:space:].,:!?;'\")}\\[]\\|$\\)" 'my/org-it-bold)
#+end_src
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: how to export checkboxes to odt?
@ 2021-09-28 20:47 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-09-28 20:47 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Hi Uwe,
Uwe Brauer writes:
> Any idea how to export checkboxes to odt?
>
> I mean not just simply having [ ] in the odt document but having them translated as actual boxes.
You can try:
(defun my/org-odt--checkbox (item)
"Return check-box string associated to ITEM."
(let ((checkbox (org-element-property :checkbox item)))
(if (not checkbox) ""
(format "<text:span text:style-name=\"%s\">%s</text:span>"
"OrgCode" (cl-case checkbox
(on "\u2611 ") ; CHECK MARK
(off "\u2610 ")
(trans "[-] ")))))) ;; I don't know which character to choose here...
(advice-add 'org-odt--checkbox :override #'my/org-odt--checkbox)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Sub-figures in Org Mode
@ 2021-10-23 0:00 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-10-23 0:00 UTC (permalink / raw)
To: Jason Ross; +Cc: orgmode
Hi Jason,
Jason Ross <jasonross1024@gmail.com> writes:
> Are there any workarounds people use to create subfigures in Org Mode
> when exporting to LaTeX? Example output:
In this thread I explain a procedure to export images as subfigures
using org links: https://list.orgmode.org/87mty1an66.fsf@posteo.net/
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: A quick LaTeX reference guide in Org
@ 2021-10-25 11:35 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-10-25 11:35 UTC (permalink / raw)
To: Tim Cross; +Cc: orgmode
Tim Cross writes:
> There is also a latex2e.info package 'out there'. I have it installed
> from my Linux distro and find being able to run (info)Latex very useful
> as a basic reference.
Thank you very much for this information, I did not know it. I just saw
that there is a `latex2e-help-texinfo' package in my distro (Arch), not in
the official repositories but in the AUR. Very useful.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Support for tabularray in LaTeX export
@ 2021-10-25 14:18 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-10-25 14:18 UTC (permalink / raw)
To: Vikas Rawal; +Cc: orgmode
Vikas Rawal writes:
>>
>> Hi Vikas,
>>
>> You can define a modified version of `org-latex--org-table',
>> adding a new LaTeX attribute `:options'. Something like this:
>
> Is there a case for incorporating this in orgmode itself? There is some general utility for this in my view.
I can prepare a patch based on that code, if you consider it useful
(https://list.orgmode.org/87ilzjgyqg.fsf@posteo.net/)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Introducing Org-transclusion
@ 2021-10-30 12:31 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-10-30 12:31 UTC (permalink / raw)
To: Noboru Ota; +Cc: orgmode
Hi Noboru,
Noboru Ota writes:
> I would like to introduce an add-on package I have been developing for
> about one year and ask for discussion / advice.
>
> The package is named "Org-transclusion", and is available on GitHub at
> https://github.com/nobiot/org-transclusion. Simply put, it lets you
> insert a copy of text content via a file link or ID link within an Org
> file. The GitHub repository contains links short video presentations
> and documentation in detail.
I installed your package a few months ago and I have to say that it
works quite well, although I have not had, at the moment, the
opportunity to make intensive use of it. What I can say is that the
concept seems very interesting to me. Very nice package.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Sub-figures in Org Mode
@ 2021-10-30 14:28 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-10-30 14:28 UTC (permalink / raw)
To: Jason Ross; +Cc: orgmode
Hi Jason, sorry for the late reply.
Jason Ross writes:
> I'm looking at declaring a "figure" block the way you are, but
> `org-element-map'ing over the links inside the block and processing them
> with the "normal" link-handling machinery. That way, image options work
> the same way in a subfigure as they do normally.
I really like your idea, and it's more consistent with the Org syntax,
since (as you say) the images behave like images and it is not necessary
to enter the options via marks within the link description, which is somewhat
hacky. I think your idea could also be adapted to LaTeX (and HTML)
backends...
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [patch] ox-latex.el: add `:options' LaTeX attribute to tables
@ 2021-11-03 17:38 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-11-03 17:38 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: orgmode
Hi Nicolas,
Nicolas Goaziou writes:
> Thank you.
>
> Could you also document it in the manual?
Of course, tomorrow I will upload an updated version of the patch with
the documentation in the manual. Should I also add an entry in ORG-NEWS,
in "Version 9.6" node?
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: insert automatically a reference to a section header and a link
@ 2021-11-17 18:17 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-11-17 18:17 UTC (permalink / raw)
To: Stefan Nobis; +Cc: orgmode
Stefan Nobis writes:
> #+begin_src emacs-lisp
> (defun sn/ox-latex-filter-special-ref-vref (text backend info)
> (when (org-export-derived-backend-p backend 'latex)
> (replace-regexp-in-string "\\\\ref{" "\\\\vref{" text)))
>
> (add-to-list 'org-export-filter-link-functions #'sn/ox-latex-filter-special-ref-vref)
> #+end_src
In Org 9.5 there is a new variable `org-latex-reference-command'. You
can do something like:
(setq org-latex-reference-command "\\vref{%s}")
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: "Orgdown", the new name for the syntax of Org-mode
@ 2021-11-29 3:25 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-11-29 3:25 UTC (permalink / raw)
To: Joost Kremers; +Cc: orgmode
Joost Kremers writes:
> Why not just use the term "Org markup"? It's descriptive and should be
> understandable to people familiar with the concept of markup languages.
This. 'Org markup language' and 'Org Syntax' are obvious and natural
terms that can easily be inferred from the Org manual. Honestly I don't
see much point in coming up with new names for a concept which is
already transparent and self-explanatory. It is something I find
unnecessary and baroque.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: how to export red colored TeX to latex
@ 2021-11-30 17:43 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-11-30 17:43 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Uwe Brauer writes:
> Thanks, right now, I don't need links but it is good to know that there is a way to use them.
It's just a way of using links to produce different strings, depending
on the export format (LaTeX, HTML...). I use them quite a bit for text
segments as \foreignlanguage{}{}, \textcolor{}{}, etc. Anyway, that
specific link does not have any associated link action.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: how to export red colored TeX to latex
@ 2021-12-01 15:00 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-12-01 15:00 UTC (permalink / raw)
To: Eric S Fraga; +Cc: orgmode
Hi Eric,
Eric S Fraga writes:
> Very nice Juan! I would find this use of links quite useful.
Thank you. Yes, org-link-set-parameters is quite productive, and
addictive in occasions! :-): I also have link types defined for somewhat
extravagant things, such as linking videos and music from the dlna
server of my raspberry...
Anyway, for format chunks of text in export I think
org-link-set-parameters is a good alternative to macros.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Org-syntax: Intra-word markup
@ 2021-12-02 11:30 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-12-02 11:30 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode, Denis Maier
Hi Denis and Ihor,
Ihor Radchenko writes:
> Denis Maier <denismaier@mailbox.org> writes:
>
>> Currently, org syntax doesn't officially seem to support intra-word
>> emphasis. Am I missing something?
>
> intra-*word* works just fine for me.
>
> Best,
> Ihor
I think what Denis is referring to is a construction of the type
*intra*word, which, if I'm not mistaken, is not supported and can only
be achieved by inserting a zero width space.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal
@ 2021-12-06 5:57 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-12-06 5:57 UTC (permalink / raw)
To: Russell Adams; +Cc: orgmode
Russell Adams writes:
> What makes Org dramatically different is the editing experience in
> Emacs. Collapsing the outline, filtering on metadata, exports, agenda,
> etc. Those are Emacs features, not specific to the actual markup
> format.
>
> My impression is we already have stretched our resources thin trying
> to maintain Org. Pushing to provide compatibility with non-Emacs tools
> seems a poor use of their time, and rude to ask of them.
>
> If non-Emacs users and coders want to use Org formatted files, they
> are free to spend their time customizing their tools to make it
> work. If the Org project owes anything to anyone, it's a consistent
> experience for the users who have used Org for years. Not changes to
> satisfy potential users or follow trendy fads.
>
> My experience has been that Org's markup is so simple and could be
> summarized in a few lines. Anything more complex enters the territory
> of Emacs only features (ie: drawers. exports, view control, source
> blocks, reporting). Those are unlikely to be portable, so we're back
> to "use Emacs".
I think that I cannot agree more with this. Org Mode is GNU Emacs, and
the magic of Org Mode is the magic of GNU Emacs. That's why I insist
that going to Org means going to Emacs.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: caption width in LateX export
@ 2021-12-27 7:41 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2021-12-27 7:41 UTC (permalink / raw)
To: Seb; +Cc: orgmode
Hi Seb
Seb writes:
> When exporting to LaTeX, is there a mechanism to make the figure
> captions as wide as the figure? In pure LaTeX, this can be easily
> accomplished by placing the figure inside a minipage environment.
> Using a special block, as in:
>
> \begin{minipage}{0.7\textwidth}
>
> #+CAPTION: looooooong caption.
> [[file_path]]
>
> \end{minipage}
>
> fails, as it seems impossible to pass arguments to the special block.
> Any tips welcome.
If you use the caption package (https://www.ctan.org/pkg/caption), you
can indicate in each figure the width of the caption. In this case, you
would have to introduce the code using raw latex via the `:caption'
property:
#+LaTeX_Header: \usepackage{caption}
#+ATTR_LaTeX: :caption \captionsetup{width=.3\linewidth}\caption{Lorem ipsum dolor sit amet, consectetuer adipiscing elit}
#+ATTR_LaTeX: :width .3\linewidth
[[file_path]]
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* [BUG] Underlined text in parentheses is not exported correctly
@ 2021-12-31 10:14 10% Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2021-12-31 10:14 UTC (permalink / raw)
To: orgmode
Hi all,
I don't know if this is a known issue...
Consider the text:
(_underline_)
When exported to LaTeX we get:
(\textsubscript{underline}\_)
And to HTML:
(<sub>underline</sub>_)
The same result with:
(_underline_ text)
LaTeX:
(\textsubscript{underline}\_ text)
But this:
(this word is _underline_)
is exported correctly:
(this word is \uline{underline})
If I do M-! (occur org-match-substring-regexp)
I get:
10:(_underline_)
22:(_underline_ text)
Best regards, and happy New Year,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: [PATCH] Re: [BUG] Underlined text in parentheses is not exported correctly
@ 2022-01-01 11:28 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-01-01 11:28 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: orgmode
Ihor Radchenko writes:
> However, thinking about it more, I feel that prioritising underline
> should work better. The underline parser recently got changed into a
> stricter version. Now, only underlines starting after spaces,-,(,',",
> and { are recognised as an underlines.
>
> So, the attached patch is changing the priority of the parsing.
> Maybe Nicolas knows some tricky cases when the patch makes things wrong,
> but those cases are certainly not covered by tests.
Great! I vote for this patch, I think it is a necessary addition. In my
case I have not found any error.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: A simple Lua filter for Pandoc
@ 2022-01-04 15:11 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-01-04 15:11 UTC (permalink / raw)
To: orgmode
Hi Timothy:
Timothy writes:
> I’m quite interested in this, thanks for sharing. In fact, I’ll probably add
> this to <https://github.com/tecosaur/org-pandoc-import>.
Interesting package. Until now I used a number of homemade functions to
convert docx/odt files from Dired, but I think your package will be very
useful to me ;-)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Tool to compare and choose fonts
@ 2022-01-05 10:16 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-01-05 10:16 UTC (permalink / raw)
To: Ypo; +Cc: orgmode
Ypo writes:
> Was a tool to compare fonts presented in this list some time ago?
>
> I lost it, I thought I discovered it on Reddit, but now I am thinking
> I found it here.
>
> It was a script that presented on emacs every font in the computer, in
> pairs; so the user chose one font each time, like if it were a
> "championship" between fonts.
https://github.com/alphapapa/unpackaged.el#font-compare
Outside of Emacs there are many tools for auditing fonts. In TeX live
you have the otfinfo script, for example, very useful. And recently the
Unicode Font Table package has been uploaded to CTAN, to represent
character tables in (Lua/Xe)LaTeX:
https://www.ctan.org/pkg/unicodefonttable
(an example that I have done inside Org, using LaTeX blocks:
https://i.imgur.com/eiiAUlB.png)
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Filter to put decorative initial letters
@ 2022-01-11 16:21 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-01-11 16:21 UTC (permalink / raw)
To: William Denton; +Cc: orgmode
Hi William,
William Denton writes:
> This is beautiful, and a nice Org hack. I appreciate the
> typographical and design examples you send, and have learned a lot
> from them. Thank you.
>
> Bill
Thanks for your kind words, I'm glad you found that code useful.
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: puzzled about :fit for LaTeX src block
@ 2022-01-12 17:22 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2022-01-12 17:22 UTC (permalink / raw)
To: Eric S Fraga; +Cc: orgmode
Hi Eric,
Eric S Fraga writes:
> I have a LaTeX src block which creates an image using tikz. In a book
> I'm writing, the image, when created as a png, does not get shrunk but
> is instead a full page (with the actual diagram in the top left corner).
> If I create a PDF, instead, it works fine.
Testing two possibilities:
What (latex) code produces that image in the output *tex file of your book?
and
C-h v RET org-format-latex-header RET: what value?
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: puzzled about :fit for LaTeX src block
@ 2022-01-13 11:17 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-01-13 11:17 UTC (permalink / raw)
To: Eric S Fraga; +Cc: orgmode
Hi Eric,
Eric S Fraga writes:
> Both the same and the default value from org.
I'm not sure, but maybe the problem comes from the
\documentclass{article} in org-format-latex-header. Can you try
replacing that with "\\documentclass[varwidth]{standalone}"?
Another possibility: please try adding the header arg. :imagemagick yes
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: Playing down the text in org-mode
@ 2022-01-13 18:50 10% ` Juan Manuel Macías
[not found] ` <87bl0feahc.fsf@posteo.net-MtJnHBm----2>
1 sibling, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-01-13 18:50 UTC (permalink / raw)
To: fatiparty; +Cc: orgmode
Hi,
fatiparty--- via "General discussions about Org-mode." writes:
> Is there anything to perform the opposite, playing down the text?
Are you referring to nested emphasis, something like in LaTeX
\emph{foo \emph{bar} baz}
= foo...baz in italic; bar in normal font?
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: org-->html text between @ should be red.
@ 2022-01-15 18:21 10% ` Juan Manuel Macías
0 siblings, 1 reply; 200+ results
From: Juan Manuel Macías @ 2022-01-15 18:21 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Uwe Brauer writes:
> Can I have a similar setting when exporting an org file to html via the
> «normal» html exporter?
Using a custom filter?
#+begin_src emacs-lisp
(defun foo (text backend info)
(when (org-export-derived-backend-p backend 'html)
(replace-regexp-in-string "@\\([^@]*\\)@"
"<span style=\"color:red\">\\1</span>"
text)))
(add-to-list 'org-export-filter-final-output-functions 'foo)
#+end_src
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
* Re: org-->html text between @ should be red.
@ 2022-01-15 19:59 10% ` Juan Manuel Macías
0 siblings, 0 replies; 200+ results
From: Juan Manuel Macías @ 2022-01-15 19:59 UTC (permalink / raw)
To: Uwe Brauer; +Cc: orgmode
Uwe Brauer writes:
> Thanks very much it works as expected. However I just realized (and
> this is true also for the org-mime filter that the reg-exp has a flaw.
>
> I used the text
>
>
> =email:oub@mat.ucm.es=
>
> So there is only one @, nevertheless the exporter translated that to
> <code>email:oub<span style="color:red">mat.ucm.es</code><br />
>
> But this is wrong in my view.
>
> Any ideas how to deal with such a situation?
You can bind the function to org-export-filter-plain-text-functions
instead of ...-final-output-functions.
That way you wouldn't get false positives on lines like:
=email:oub@mat.ucm.es= some text @some text@
<code>email:oub@mat.ucm.es</code> some text <span style="color:red">some text</span>
Best regards,
Juan Manuel
^ permalink raw reply [relevance 10%]
Results 201-400 of ~1000 next [<= 9%] | prev [>= 10%] | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2021-06-03 21:11 10% [bug?] org-link-set-parameters: when `:display 'full', link face is applied only in description part Juan Manuel Macías
2021-06-04 11:31 ` Juan Manuel Macías
2021-06-06 22:34 ` Juan Manuel Macías
2021-06-08 0:24 ` [PATCH] org.el: prevent partial fontification when a link is full displayed (was org-link-set-parameters: when :display full, etc.) Juan Manuel Macías
2021-09-26 6:08 ` Bastien
2021-09-26 11:35 10% ` Juan Manuel Macías
2024-01-29 20:05 10% An academic journal made entirely in Org-Mode Juan Manuel Macías
2022-06-20 14:03 10% Org and Hyperbole Juan Manuel Macías
2020-12-28 13:38 10% Org to ConTeXt exporter? Juan Manuel Macías
2021-01-08 2:37 ` Jason Ross
2021-01-09 17:42 10% ` Juan Manuel Macías
2020-12-28 15:04 ` Marcin Borkowski
2020-12-28 15:38 10% ` Juan Manuel Macías
2020-12-28 16:23 ` Diego Zamboni
2020-12-28 18:03 10% ` Juan Manuel Macías
2021-08-03 10:47 10% [PATCH] ox.el: fix spanish translation for `footnotes' Juan Manuel Macías
2022-03-11 22:24 10% helm-org-names: browse the names of code blocks, tables and figures Juan Manuel Macías
2021-06-07 13:09 10% org-critical-edition (a package for philologists and classicists) Juan Manuel Macías
2021-03-22 21:59 10% Items with emphasis marks are not sorted properly in a list Juan Manuel Macías
2023-09-16 18:00 10% [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword Juan Manuel Macías
[not found] <mailman.57.1618243212.17744.emacs-orgmode@gnu.org>
2021-04-12 18:51 ` [Patch] to correctly sort the items with emphasis marks in a list Ypo
2021-04-12 23:18 10% ` Juan Manuel Macías
2021-04-12 23:52 ` Samuel Wales
2021-04-13 14:16 10% ` Juan Manuel Macías
2022-10-10 15:19 10% Information about all LaTeX packages in an Org document Juan Manuel Macías
2021-06-03 14:54 10% Remove all Org metadata with header argument `:comments org' Juan Manuel Macías
2021-07-09 9:15 10% [PATCH] [BUG] Bad fontification in full displayed links Juan Manuel Macías
2021-07-10 1:50 ` Ihor Radchenko
2021-07-10 12:12 10% ` Juan Manuel Macías
2024-01-29 20:03 10% An academic journal entirely made in Org-Mode Juan Manuel Macías
2021-02-15 17:37 10% 'false' list item Juan Manuel Macías
2021-02-21 6:56 ` Kyle Meyer
2021-02-21 19:33 10% ` Juan Manuel Macías
2021-02-21 19:40 ` Diego Zamboni
2021-02-21 21:27 ` Samuel Wales
2021-02-21 22:25 10% ` Juan Manuel Macías
2021-02-21 7:05 ` Tim Cross
2021-02-21 14:49 10% ` Juan Manuel Macías
2021-04-12 13:50 10% [Patch] to correctly sort the items with emphasis marks in a list Juan Manuel Macías
2021-02-23 18:23 10% false-list-item-mode? Juan Manuel Macías
2021-03-31 18:56 10% About exporting Juan Manuel Macías
2021-12-31 10:14 10% [BUG] Underlined text in parentheses is not exported correctly Juan Manuel Macías
2021-12-31 11:13 ` Ihor Radchenko
2021-12-31 11:31 10% ` Juan Manuel Macías
2021-12-31 14:43 ` [PATCH] " Ihor Radchenko
2022-01-01 11:28 10% ` Juan Manuel Macías
2022-09-18 12:27 9% [Patch] Pre-/postpend arbitrary LaTeX code to a section Juan Manuel Macías
2021-01-29 16:03 9% org-attach-git don't automatically commit changes Juan Manuel Macías
2021-01-30 5:10 ` Ihor Radchenko
2021-01-30 13:38 ` Juan Manuel Macías
2021-01-31 3:33 ` Ihor Radchenko
2021-01-31 10:29 ` Juan Manuel Macías
2021-01-31 10:52 ` Ihor Radchenko
2021-01-31 13:16 10% ` Juan Manuel Macías
2021-01-31 13:40 ` Ihor Radchenko
2021-01-31 14:36 10% ` Juan Manuel Macías
2021-01-31 11:41 10% ` Juan Manuel Macías
2021-10-24 14:23 9% A quick LaTeX reference guide in Org Juan Manuel Macías
2021-10-24 20:18 ` Tim Cross
2021-10-25 11:35 10% ` Juan Manuel Macías
2021-10-25 12:30 ` Eric S Fraga
2021-10-25 14:10 10% ` Juan Manuel Macías
2024-03-01 20:34 9% Experimental public branch for inline special blocks Juan Manuel Macías
2024-04-09 8:52 ` Ihor Radchenko
2024-04-09 10:51 ` Max Nikulin
2024-04-09 14:05 ` Ihor Radchenko
2024-04-10 23:00 10% ` Juan Manuel Macías
2024-03-03 20:29 ` Juan Manuel Macías
2024-03-10 2:08 10% ` `:export' attribute?: " Juan Manuel Macías
2021-01-05 18:33 Inserting LaTex expressions using a filter fails Mart van de Wege
2021-01-05 21:58 10% ` Juan Manuel Macías
2021-01-06 7:50 ` Mart van de Wege
2021-01-06 11:51 10% ` Juan Manuel Macías
2021-01-06 12:00 ` Mart van de Wege
2021-01-06 12:24 10% ` Juan Manuel Macías
2021-01-06 15:17 ` Mart van de Wege
2021-01-06 15:58 10% ` Juan Manuel Macías
2021-04-04 10:31 how to export (latex) a image without using figure Uwe Brauer
2021-04-04 11:17 10% ` Juan Manuel Macías
2021-03-06 19:34 Org as a book publisher Juan Manuel Macías
[not found] ` <87ft16hn62.fsf@emailmessageidheader.nil>
2021-03-07 20:20 10% ` Juan Manuel Macías
2021-06-11 17:53 Failure to resolve internal links on ox-html export? Tim Visher
2021-06-11 18:31 10% ` Juan Manuel Macías
2021-06-18 19:47 ` Tim Visher
2021-06-18 20:37 10% ` Juan Manuel Macías
2021-09-28 16:46 how to export checkboxes to odt? Uwe Brauer
2021-09-28 20:47 10% ` Juan Manuel Macías
2021-06-16 9:33 no inline images anymore after reinstall Prof. Dr. Johanna May
2021-06-16 12:51 9% ` Juan Manuel Macías
2024-02-20 20:35 [proof of concept] inline language blocks Juan Manuel Macías
2024-02-21 8:42 ` Ihor Radchenko
2024-02-21 10:57 10% ` Juan Manuel Macías
2024-02-21 12:00 ` Ihor Radchenko
2024-02-21 12:53 ` Juan Manuel Macías
2024-02-21 13:10 ` Ihor Radchenko
2024-02-21 14:13 ` Juan Manuel Macías
2024-02-21 22:11 ` Samuel Wales
2024-02-21 22:28 ` Juan Manuel Macías
2024-02-21 23:02 10% ` Juan Manuel Macías
2024-02-28 10:29 ` Max Nikulin
2024-02-28 13:15 ` Juan Manuel Macías
2024-02-28 17:21 ` Max Nikulin
2024-02-28 23:42 ` Juan Manuel Macías
2024-02-29 7:05 ` Max Nikulin
2024-02-29 10:41 10% ` Juan Manuel Macías
2024-02-29 12:05 ` Max Nikulin
2024-02-29 12:50 10% ` Juan Manuel Macías
2021-07-05 19:44 convert subtree or nested list to table Matt Price
2021-07-05 20:01 10% ` Juan Manuel Macías
[not found] ` <CAN_Dec8iqKS+3qvjkYvQxovegnEzqR_rra0Q-ZA9baPz1mXDAA@mail.gmail.com>
2021-07-06 12:56 ` Juan Manuel Macías
2021-07-07 6:18 ` Uwe Brauer
2021-07-07 18:27 10% ` Juan Manuel Macías
2022-05-23 21:06 About 'inline special blocks' Juan Manuel Macías
2022-05-24 2:36 ` Tim Cross
2022-05-24 3:56 ` Ihor Radchenko
2022-05-25 13:55 10% ` Juan Manuel Macías
2020-12-17 17:23 [PATCH] A proposal to add LaTeX attributes to verse blocks Juan Manuel Macías
2021-01-03 10:25 ` TEC
2021-01-03 13:07 10% ` Juan Manuel Macías
2021-01-03 13:08 ` TEC
2021-01-07 18:52 ` Juan Manuel Macías
2021-05-01 10:58 ` Bastien
2021-05-01 11:46 10% ` Juan Manuel Macías
2021-06-09 19:35 org-attach a directory? Ypo
2021-06-09 23:39 ` John Kitchin
2021-06-10 3:56 ` Ypo
2021-06-10 12:37 ` Christian Barthel
2021-06-10 14:01 10% ` Juan Manuel Macías
2021-06-07 11:43 literate programming, development log -- ideas? Greg Minshall
2021-06-07 12:00 10% ` Juan Manuel Macías
2023-08-06 12:03 [patch] ox-latex.el: fix blank lines behavior in verse block Juan Manuel Macías
2023-08-07 11:40 ` Ihor Radchenko
2023-08-07 17:23 ` Juan Manuel Macías
2023-08-09 7:57 ` Ihor Radchenko
2023-08-09 8:41 ` Juan Manuel Macías
2023-08-10 9:27 ` Ihor Radchenko
2023-08-10 10:39 10% ` Juan Manuel Macías
2023-08-11 10:00 ` Ihor Radchenko
2023-08-11 18:52 ` Juan Manuel Macías
2023-08-12 7:56 ` Ihor Radchenko
2023-08-14 20:10 ` Juan Manuel Macías
2023-08-15 10:08 ` Ihor Radchenko
2023-08-15 11:50 10% ` Juan Manuel Macías
2024-01-22 20:42 Possible LaTeX export bug: Footnotes in items Eric Anderson
2024-01-24 12:11 ` [BUG] Footnotes in section titles Ihor Radchenko
2024-01-24 14:14 ` Max Nikulin
2024-01-24 15:23 ` Juan Manuel Macías
2024-01-24 15:31 ` Colin Baxter
2024-01-24 15:41 ` Juan Manuel Macías
2024-01-26 12:53 ` Ihor Radchenko
2024-01-26 16:43 ` Max Nikulin
2024-02-01 14:44 ` [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc) (was: [BUG] Footnotes in section titles) Ihor Radchenko
2024-02-01 17:44 10% ` [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc) Juan Manuel Macías
2021-06-12 9:15 Write Markdown in Org mode leo
2021-06-12 12:35 ` Juan Manuel Macías
2021-06-12 15:14 ` leo
2021-06-12 15:51 10% ` Juan Manuel Macías
2021-09-22 6:26 [ANN] org-ql 0.6 released Adam Porter
2021-09-22 12:10 10% ` Juan Manuel Macías
2021-01-31 19:37 [patch] to allow org-attach-git to handle individual repositories Juan Manuel Macías
2021-04-28 3:57 ` Bastien
2021-04-28 13:42 10% ` Juan Manuel Macías
2022-01-12 13:08 puzzled about :fit for LaTeX src block Eric S Fraga
2022-01-12 17:22 10% ` Juan Manuel Macías
2022-01-13 10:14 ` Eric S Fraga
2022-01-13 11:17 10% ` Juan Manuel Macías
2021-04-02 18:15 [Patch] to correctly sort the items with emphasis marks in a list Juan Manuel Macías
2021-04-09 22:28 ` Nicolas Goaziou
2021-04-10 0:01 9% ` Juan Manuel Macías
2021-04-10 10:19 ` Nicolas Goaziou
2021-04-10 11:41 10% ` Juan Manuel Macías
2020-12-22 17:12 *strong* markup not honored at boundary of macro input during HTML export m27315
2020-12-23 14:58 ` m27315
2020-12-23 15:22 10% ` Juan Manuel Macías
[not found] ` <7e5e7cbe-31d6-2d9e-e450-9c1b54dba95e@gmail.com>
2020-12-23 16:05 10% ` Juan Manuel Macías
2021-11-17 7:36 insert automatically a reference to a section header and a link Uwe Brauer
2021-11-17 10:04 ` Eric S Fraga
2021-11-17 13:58 ` Uwe Brauer
2021-11-17 14:06 ` John Kitchin
2021-11-17 14:15 ` Uwe Brauer
2021-11-17 14:59 ` Stefan Nobis
2021-11-17 15:42 10% ` Juan Manuel Macías
2021-11-17 15:55 ` Uwe Brauer
2021-11-17 16:29 ` Stefan Nobis
2021-11-17 18:17 10% ` Juan Manuel Macías
2022-01-13 18:27 Playing down the text in org-mode fatiparty--- via General discussions about Org-mode.
2022-01-13 18:50 10% ` Juan Manuel Macías
[not found] ` <87bl0feahc.fsf@posteo.net-MtJnHBm----2>
2022-01-13 19:15 ` fatiparty--- via General discussions about Org-mode.
2022-01-13 19:42 ` Juan Manuel Macías
2022-01-13 19:53 ` fatiparty--- via General discussions about Org-mode.
[not found] ` <87iluncrr6.fsf@posteo.net-MtK5wx2----2>
2022-01-13 20:53 ` fatiparty--- via General discussions about Org-mode.
2022-01-13 21:39 10% ` Juan Manuel Macías
2021-06-18 22:15 publishing: no default publishing function, or symbol is not defined Christopher W. Ryan via General discussions about Org-mode.
2021-06-19 12:48 ` Juan Manuel Macías
2021-06-19 18:28 ` [External Email] " Christopher W. Ryan via General discussions about Org-mode.
2021-06-19 19:32 ` Juan Manuel Macías
2021-06-22 20:26 ` Christopher W. Ryan via General discussions about Org-mode.
2021-06-25 8:38 10% ` Juan Manuel Macías
2022-03-07 15:18 interleaving comment between rows of a table? Greg Minshall
2022-03-07 15:54 10% ` Juan Manuel Macías
2022-04-29 15:03 Org as a workspace (an impromptu reflection) Juan Manuel Macías
2022-05-02 19:17 ` Nick Dokos
2022-05-03 23:41 10% ` Juan Manuel Macías
2021-11-30 16:28 how to export red colored TeX to latex Uwe Brauer
2021-11-30 16:56 ` Juan Manuel Macías
2021-11-30 17:11 ` Uwe Brauer
2021-11-30 17:43 10% ` Juan Manuel Macías
2021-12-01 6:28 ` Eric S Fraga
2021-12-01 15:00 10% ` Juan Manuel Macías
2021-02-01 15:17 word counts and org-mode drawers Sharon Kimble
2021-02-01 23:29 10% ` Juan Manuel Macías
2023-10-22 21:12 Are 'placement' and 'float' "obsolete terms" in inline images export Juan Manuel Macías
2023-10-23 9:27 ` Ihor Radchenko
2023-10-23 19:00 10% ` Juan Manuel Macías
2022-01-09 18:02 Org Syntax Specification Timothy
2022-01-15 12:40 ` Sébastien Miquel
2022-01-15 16:36 ` Depreciating TeX-style LaTeX fragments (was: Org Syntax Specification) Timothy
2022-01-16 8:08 ` Sébastien Miquel
2022-01-16 9:46 ` Depreciating TeX-style LaTeX fragments Colin Baxter 😺
2022-01-16 13:26 9% ` Juan Manuel Macías
2022-03-17 22:44 Org and multimedia (tips?) Juan Manuel Macías
2022-03-18 14:40 ` Max Nikulin
2022-03-19 11:13 10% ` Juan Manuel Macías
2022-05-15 11:54 [tip] Export and open a PDF in Android via Termux Juan Manuel Macías
2022-05-16 15:00 ` Max Nikulin
2022-05-16 16:05 10% ` Juan Manuel Macías
2023-09-06 14:55 ox-latex language handling in Org-9.5 vs 9.6 Max Nikulin
2023-09-06 22:20 ` Juan Manuel Macías
2023-09-07 11:50 ` Ihor Radchenko
2023-09-07 14:19 ` Juan Manuel Macías
2023-09-07 14:49 ` Max Nikulin
2023-09-08 10:30 ` Max Nikulin
2023-09-08 14:42 ` Juan Manuel Macías
2023-09-08 19:02 ` [patch] Fixes and improvements in org-latex-language-alist (was: ox-latex language handling in Org-9.5 vs 9.6) Juan Manuel Macías
2023-09-09 9:11 ` Ihor Radchenko
2023-09-10 16:15 ` Max Nikulin
2023-09-10 16:52 ` Ihor Radchenko
2023-09-11 17:06 ` Max Nikulin
2023-09-12 9:05 ` Ihor Radchenko
2023-09-12 15:22 ` Max Nikulin
2023-09-12 18:12 10% ` [patch] Fixes and improvements in org-latex-language-alist Juan Manuel Macías
2021-04-03 18:45 How to get a table into a variable in a shell code block? Greg Minshall
2021-04-03 19:01 10% ` Juan Manuel Macías
2021-08-13 14:17 return column from table as a column Roger Mason
2021-08-13 14:47 10% ` Juan Manuel Macías
2021-08-13 16:32 ` Roger Mason
2021-08-13 17:12 10% ` Juan Manuel Macías
2020-11-28 16:59 Remembrance Agents Gerardo Moro
2020-11-28 18:26 ` Jean Louis
2020-11-29 13:07 ` Gerardo Moro
2020-11-29 13:52 ` Eric S Fraga
2020-11-29 17:29 ` Jean Louis
2020-11-29 17:47 ` Eric S Fraga
2020-11-30 11:15 ` Jean Louis
2021-01-06 6:41 ` Possibility to copy text outside EMACS and send it to orgmode document Gerardo Moro
2021-01-06 16:31 10% ` Juan Manuel Macías
2021-02-01 9:10 http links translated to html : target "_blank" Uwe Brauer
2021-02-01 11:03 ` Juan Manuel Macías
2021-02-01 13:56 ` Uwe Brauer
2021-02-01 14:46 ` Juan Manuel Macías
2021-02-01 15:20 ` Uwe Brauer
2021-02-01 21:01 10% ` Juan Manuel Macías
2021-10-30 11:51 Introducing Org-transclusion Noboru Ota
2021-10-30 12:31 10% ` Juan Manuel Macías
2021-06-29 11:25 Virtually prefix headlines according to content Rodrigo Morales
2021-06-29 13:34 10% ` Juan Manuel Macías
2020-12-08 11:35 Bug: Footnotes on Headers and LaTeX export [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)] Charis Michelakis
2020-12-09 15:06 10% ` Juan Manuel Macías
2021-05-22 14:12 [PATCH] org.el: use only link descriptions in indirect buffer names Juan Manuel Macías
2021-05-23 10:41 ` Ihor Radchenko
2021-05-23 11:25 9% ` Juan Manuel Macías
2021-06-17 12:06 example paper written in org completely Eric S Fraga
2021-06-17 12:51 10% ` Juan Manuel Macías
2021-08-13 18:40 Org + git branches for derived files Ken Mankoff
2021-08-13 20:53 10% ` Juan Manuel Macías
2021-12-05 7:35 Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal Ihor Radchenko
2021-12-05 9:16 ` Juan Manuel Macías
2021-12-05 10:24 ` Ihor Radchenko
2021-12-05 11:08 ` Juan Manuel Macías
2021-12-05 12:08 ` Ihor Radchenko
2021-12-05 18:59 ` Juan Manuel Macías
2021-12-05 23:24 ` Russell Adams
2021-12-06 5:57 10% ` Juan Manuel Macías
2021-08-04 16:01 ConTeXt exporter for Org Mode Jason Ross
2021-08-04 19:43 10% ` Juan Manuel Macías
2021-04-30 15:19 How to create a macro that inserts multiline text with :B_ignoreheading: tag? Richard Stanton
2021-04-30 20:40 10% ` Juan Manuel Macías
2021-05-31 10:40 An attempt to convert Elfeed entries (with parameters) to Org trees Juan Manuel Macías
2021-06-23 14:56 ` Ihor Radchenko
2021-06-24 8:02 10% ` Juan Manuel Macías
2023-08-04 7:25 [patch] Fix inner smart quotes in French Juan Manuel Macías
2023-08-04 11:09 ` Bastien
2023-08-10 14:10 ` Max Nikulin
2023-08-10 14:49 ` Bastien
2023-08-10 21:50 10% ` Juan Manuel Macías
2021-08-13 22:29 Custom function for killing the thing at point Rodrigo Morales
2021-08-13 22:46 10% ` Juan Manuel Macías
2022-01-20 14:33 Exporting Org file to Html with collapsable headings ZIPING CHEN
2022-01-21 12:23 10% ` Juan Manuel Macías
2021-02-18 16:33 [PATCH] Startup option to separate macros arguments with an alternative string Juan Manuel Macías
2021-04-19 9:19 ` Nicolas Goaziou
2021-04-21 16:01 ` Juan Manuel Macías
2021-04-22 12:55 ` Nicolas Goaziou
2021-04-22 13:46 10% ` Juan Manuel Macías
2021-12-02 10:50 Org-syntax: Intra-word markup Denis Maier
2021-12-02 11:18 ` Ihor Radchenko
2021-12-02 11:30 10% ` Juan Manuel Macías
2021-12-02 11:58 ` Timothy
2021-12-02 12:26 ` Denis Maier
2021-12-02 13:07 ` Ihor Radchenko
2021-12-02 19:03 ` Nicolas Goaziou
2021-12-03 14:24 ` Max Nikulin
2021-12-03 15:01 9% ` Juan Manuel Macías
2022-07-08 13:03 Taking notes of videos in Emacs Gerardo Moro
2022-07-08 13:25 ` Juan Manuel Macías
2022-07-09 7:31 ` Gerardo Moro
2022-07-09 11:37 10% ` Juan Manuel Macías
2022-02-18 0:47 Pandoc and nested emhases Juan Manuel Macías
2022-02-18 12:06 ` Max Nikulin
2022-02-18 12:31 10% ` Juan Manuel Macías
2021-07-10 13:42 org-mode export to (latex) PDF Jean-Christophe Helary
2021-07-10 13:52 10% ` Juan Manuel Macías
2021-07-10 16:13 ` Maxim Nikulin
2021-07-10 16:44 ` Stefan Nobis
2021-07-13 16:53 ` Maxim Nikulin
2021-07-14 6:44 ` Stefan Nobis
2021-07-14 17:30 ` Maxim Nikulin
2021-07-14 19:05 ` Stefan Nobis
2021-07-15 17:10 ` Maxim Nikulin
2021-07-15 19:40 9% ` Juan Manuel Macías
2022-05-08 22:22 [tip] Insert arbitrary LaTeX code at the beginning of any float environment Juan Manuel Macías
2022-05-09 12:47 ` Ihor Radchenko
2022-05-09 14:01 10% ` Juan Manuel Macías
2021-04-05 9:25 [tip] search this mailing list with helm-surfraw Juan Manuel Macías
2021-04-25 5:00 ` Bastien
2021-04-27 20:20 10% ` Juan Manuel Macías
2021-06-26 14:44 Export Org mode files to (gag, barf) MS Office? Brandon Taylor
2021-06-26 15:15 10% ` Juan Manuel Macías
2021-06-23 19:27 appearance of list as results from evaluating code blocks Johannes Brauer
2021-06-23 19:43 10% ` Juan Manuel Macías
2021-08-27 13:29 pygments support Yuchen Pei
2021-08-27 13:49 10% ` Juan Manuel Macías
2021-06-01 15:36 suggestion to change default org-latex-pdf-process to latexmk Bruce D'Arcus
2021-06-01 15:52 10% ` Juan Manuel Macías
2021-06-02 0:00 ` Tim Cross
2021-06-02 6:07 ` Stefan Nobis
2021-06-02 8:40 10% ` Juan Manuel Macías
2021-06-06 18:19 [PATCH] Allow LaTeX reference command (\ref) to be customised Timothy
2021-06-06 18:29 10% ` Juan Manuel Macías
2021-09-26 12:24 [BUG] Conflict between org-emphasis and org-latex Léo Ackermann
2021-09-26 12:57 10% ` Juan Manuel Macías
2021-09-28 15:14 Possible bug? Combine emphasis marker faces? Protesilaos Stavrou
2021-09-28 16:54 10% ` Juan Manuel Macías
2022-01-04 10:14 A simple Lua filter for Pandoc Juan Manuel Macías
2022-01-04 11:26 ` Timothy
2022-01-04 15:11 10% ` Juan Manuel Macías
2021-01-19 22:05 Region-based meta-notes Lawrence Bottorff
2021-01-19 22:39 10% ` Juan Manuel Macías
2022-06-29 19:18 PDF export, table of contents and internal links Sébastien Gendre
2022-06-29 19:56 9% ` Juan Manuel Macías
2020-12-01 12:08 Footnote definition within a verse block has spurious line breaks when exported to LaTeX Juan Manuel Macías
2020-12-05 9:09 ` Nicolas Goaziou
2020-12-05 13:47 10% ` Juan Manuel Macías
2022-08-08 14:39 [PATCH] Documentation and NEWS for ` org-latex-language-alist' Juan Manuel Macías
2022-08-09 11:43 ` Ihor Radchenko
2022-08-16 14:16 ` Juan Manuel Macías
2022-08-20 5:51 ` Ihor Radchenko
2022-08-20 7:17 ` http: links in the manual Max Nikulin
2022-08-21 9:55 9% ` Juan Manuel Macías
2022-07-08 12:17 LaTeX export: when is it more useful to use LuaTeX instead of pdfTeX? Juan Manuel Macías
2022-07-08 18:49 ` Thomas S. Dye
2022-07-09 2:23 ` Max Nikulin
2022-07-09 10:42 ` Juan Manuel Macías
2022-07-09 12:15 ` Max Nikulin
2022-07-09 14:58 ` Juan Manuel Macías
[not found] ` <b58ee3cc-c58c-b627-9cc5-51993020db2c@gmail.com>
2022-07-09 20:22 ` Juan Manuel Macías
2022-07-10 20:23 ` [possible patch] Basic fontspec code for LuaLaTeX and XelaTeX (was "LaTeX export: when is it more useful...") Juan Manuel Macías
2022-07-11 2:19 ` Ihor Radchenko
2022-07-11 14:19 ` Timothy
2022-07-11 15:00 10% ` Juan Manuel Macías
2022-07-09 3:24 ` LaTeX export: when is it more useful to use LuaTeX instead of pdfTeX? Tim Cross
2022-07-09 9:59 ` Juan Manuel Macías
2022-07-09 23:49 ` Tim Cross
2022-07-10 19:31 10% ` Juan Manuel Macías
2022-07-12 17:18 missing a character / font in agenda? Daniel Ortmann
2022-07-12 17:58 ` Juan Manuel Macías
2022-07-12 18:45 ` [External] : " Daniel Ortmann
2022-07-12 19:52 ` Juan Manuel Macías
2022-07-12 20:03 ` Juan Manuel Macías
2022-07-12 23:04 ` Daniel Ortmann
2022-07-12 23:31 ` Ihor Radchenko
2022-07-13 0:26 ` Stefan Kangas
2022-07-13 10:01 10% ` Juan Manuel Macías
2021-05-28 2:54 Smart quotes not working correctly with single quotes Andreas Gösele
2021-05-28 10:10 9% ` Juan Manuel Macías
2021-05-28 15:42 ` Andreas Gösele
2021-05-28 19:48 ` Nicolas Goaziou
2021-05-28 20:19 10% ` Juan Manuel Macías
2021-05-28 17:02 ` Juan Manuel Macías
2021-05-28 20:27 ` Andreas Gösele
2021-05-28 20:37 10% ` Juan Manuel Macías
2022-09-13 15:54 error org export to pdf when latex letter class has been added to org-latex-classes M. Pger
2022-09-13 17:55 ` Juan Manuel Macías
2022-09-13 19:59 ` M. Pger
2022-09-13 20:15 10% ` Juan Manuel Macías
2021-06-08 17:15 literate programming, development log -- ideas? (ominbus reply) Greg Minshall
2021-06-08 17:21 ` Samuel Banya
2021-06-09 8:59 ` Eric S Fraga
2021-06-09 22:21 ` Dr. Arne Babenhauserheide
2021-06-10 22:07 ` Samuel Wales
2021-06-11 0:13 ` Samuel Banya
2021-06-11 14:30 10% ` Juan Manuel Macías
2023-03-21 3:36 org-ctags land grab Nick Dokos
2023-08-24 11:39 ` [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading? Bastien Guerry
2023-08-24 11:44 ` Ihor Radchenko
2023-08-24 12:08 ` Bastien Guerry
2023-08-24 12:15 ` Ihor Radchenko
2023-08-24 12:36 ` Bastien Guerry
2023-08-24 12:40 ` Ihor Radchenko
2023-08-24 12:48 ` Bastien Guerry
2023-08-24 12:56 ` Ihor Radchenko
2023-08-24 13:02 ` Bastien Guerry
2023-08-24 13:36 ` Ihor Radchenko
2023-08-24 14:08 ` Bastien Guerry
2023-08-25 9:44 ` [DISCUSSION] Re-design of inlinetasks (was: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?) Ihor Radchenko
2023-08-25 17:58 ` [DISCUSSION] Re-design of inlinetasks Juan Manuel Macías
2023-08-26 10:58 ` Ihor Radchenko
2023-08-26 11:42 ` Juan Manuel Macías
2023-08-26 12:33 ` Ihor Radchenko
2023-08-26 14:21 ` Juan Manuel Macías
2023-08-26 16:33 ` Ihor Radchenko
2023-08-26 17:31 ` Juan Manuel Macías
2023-08-26 17:43 ` Ihor Radchenko
2023-08-26 19:19 10% ` Juan Manuel Macías
2023-08-27 9:21 ` Ihor Radchenko
2023-08-27 17:25 10% ` Juan Manuel Macías
2021-04-03 9:31 First steps exporting to tex Ypo
2021-04-03 10:15 ` Martin Steffen
2021-04-04 11:04 ` Ypo
2021-04-04 11:36 10% ` Juan Manuel Macías
2021-08-14 15:06 Smart quotes for Greek (questions for a possible patch) Juan Manuel Macías
2021-08-15 21:28 ` mvar
2021-08-27 16:23 ` Protesilaos Stavrou
2021-08-31 11:11 9% ` Juan Manuel Macías
2021-11-12 22:35 whitespace in org source files excalamus--- via General discussions about Org-mode.
2021-11-13 12:57 10% ` Juan Manuel Macías
2020-12-27 16:44 Bug: Tildes in URL impact visible link text [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)] Chris Hunt
2020-12-27 18:12 10% ` Juan Manuel Macías
2020-12-27 20:14 ` tomas
2020-12-27 21:33 10% ` Juan Manuel Macías
2021-10-26 16:05 [patch] ox-latex.el: add `:options' LaTeX attribute to tables Juan Manuel Macías
2021-11-03 16:32 ` Nicolas Goaziou
2021-11-03 17:38 10% ` Juan Manuel Macías
2021-03-01 12:55 [tip for EXWM users] An alternative method for isolate trees Juan Manuel Macías
2021-03-01 13:37 ` Julian M. Burgos
2021-03-01 14:10 10% ` Juan Manuel Macías
2021-03-01 15:37 ` Julian M. Burgos
2021-03-01 16:42 9% ` Juan Manuel Macías
2023-08-18 18:27 [Tip] Popup-menu with several actions for a link Juan Manuel Macías
2023-08-19 19:53 ` Ihor Radchenko
2023-08-19 20:29 ` Juan Manuel Macías
2023-08-20 7:23 ` Ihor Radchenko
2023-08-20 10:13 10% ` Juan Manuel Macías
2022-01-05 2:09 Tool to compare and choose fonts Ypo
2022-01-05 10:16 10% ` Juan Manuel Macías
2021-08-26 13:43 how to get multi-line author in ODT export? Eric S Fraga
2021-08-26 14:24 ` Eric S Fraga
2021-08-26 16:05 10% ` Juan Manuel Macías
2021-08-26 16:54 ` Juan Manuel Macías
2021-08-26 18:34 ` John Kitchin
2021-08-27 1:46 10% ` Juan Manuel Macías
2021-04-30 13:26 [PATCH] Possibility of using alternative separators in macros Juan Manuel Macías
2021-05-11 11:01 ` Eric S Fraga
2021-05-11 16:12 ` Juan Manuel Macías
[not found] ` <87im3prvz8.fsf@ucl.ac.uk>
2021-05-11 18:25 ` Juan Manuel Macías
2021-05-15 13:29 ` Bastien
2021-05-15 20:14 ` Juan Manuel Macías
2021-05-15 20:25 ` Bastien
2021-05-15 21:05 10% ` Juan Manuel Macías
2024-01-02 23:46 [possible patch] Remove the '\\[0pt]' string from the last line of a verse block in LaTeX export Juan Manuel Macías
2024-01-13 15:08 ` Ihor Radchenko
2024-01-13 16:05 10% ` Juan Manuel Macías
2024-01-13 18:28 ` Ihor Radchenko
2024-01-13 20:22 ` Juan Manuel Macías
2024-01-14 12:33 ` Ihor Radchenko
2024-01-14 21:58 ` Juan Manuel Macías
2024-01-16 14:09 ` Ihor Radchenko
2024-01-16 19:33 ` Juan Manuel Macías
2024-01-17 13:00 ` Ihor Radchenko
2024-01-17 17:50 ` Juan Manuel Macías
2024-01-18 13:05 ` Ihor Radchenko
2024-01-19 17:28 10% ` Juan Manuel Macías
2024-01-20 12:34 ` Ihor Radchenko
2024-01-20 13:22 ` Juan Manuel Macías
2024-01-20 13:46 ` Ihor Radchenko
2024-01-20 15:41 ` Juan Manuel Macías
2024-01-20 18:47 ` Ihor Radchenko
2024-01-20 20:27 ` Juan Manuel Macías
2024-01-21 13:42 ` Ihor Radchenko
2024-01-21 19:25 9% ` Juan Manuel Macías
2024-01-20 10:09 ` Max Nikulin
2024-01-20 10:57 10% ` Juan Manuel Macías
2021-06-02 2:03 Format babel code block for export? Galaxy Being
2021-06-02 9:42 10% ` Juan Manuel Macías
2021-05-30 17:33 TMIO Pre-release, request for feedback Timothy
2021-05-30 19:42 10% ` Juan Manuel Macías
2021-08-01 20:29 TMIO July Post: Introducing Citations Timothy
2021-08-02 7:23 10% ` Juan Manuel Macías
2021-09-02 0:42 Support for tabularray in LaTeX export Vikas Rawal
2021-09-02 8:36 ` Juan Manuel Macías
2021-09-02 10:08 ` Vikas Rawal
2021-10-25 14:04 ` Vikas Rawal
2021-10-25 14:18 10% ` Juan Manuel Macías
2022-02-17 14:56 Question Regarding Creating HTML Style Buttons With Org Mode Samuel Banya
2022-02-17 22:10 10% ` Juan Manuel Macías
2022-02-18 19:59 ` Samuel Banya
2022-02-18 20:38 10% ` Juan Manuel Macías
2021-04-02 15:54 Including Email Address in the Reply in Mailing-list Husain Alshehhi
2021-04-02 23:08 ` Tim Cross
2021-04-02 23:45 10% ` Juan Manuel Macías
2022-10-30 9:49 org-fstree.el overview over directories (but no comments are possible) Uwe Brauer
2022-10-30 12:52 ` Juan Manuel Macías
2022-10-30 13:10 ` Uwe Brauer
2022-10-30 13:56 ` Juan Manuel Macías
2022-10-30 14:01 ` Uwe Brauer
2022-10-30 15:40 9% ` Juan Manuel Macías
2022-10-30 17:16 ` Uwe Brauer
2022-10-30 18:17 ` Juan Manuel Macías
2022-10-30 18:48 ` Uwe Brauer
2022-10-30 19:04 ` Juan Manuel Macías
2022-10-30 19:21 ` Uwe Brauer
2022-10-30 19:26 ` [correction] (was: org-fstree.el overview over directories (but no comments are possible)) Uwe Brauer
2022-10-30 19:51 10% ` [correction] Juan Manuel Macías
2022-10-30 21:23 ` [correction] Uwe Brauer
2022-10-31 12:22 ` [correction] Juan Manuel Macías
2022-10-31 12:55 ` [correction] Uwe Brauer
2022-10-31 15:08 ` [correction] Juan Manuel Macías
2022-10-31 15:48 ` [correction] Uwe Brauer
2022-10-31 16:23 10% ` [correction] Juan Manuel Macías
2022-10-31 16:58 ` [correction] Uwe Brauer
2022-10-31 17:35 ` [correction] Juan Manuel Macías
2022-10-31 17:38 ` [correction] Uwe Brauer
2022-10-31 21:01 ` [correction] Juan Manuel Macías
2022-11-01 7:13 ` [correction] Uwe Brauer
2022-11-01 7:16 ` [correction] Uwe Brauer
2022-11-01 13:52 10% ` [correction] Juan Manuel Macías
2021-05-17 15:41 Multilingual support (proposals and state of the question) Juan Manuel Macías
2021-05-17 16:03 ` Denis Maier
2021-05-17 18:10 10% ` Juan Manuel Macías
2022-05-14 19:58 I can't set dabbrev to respect the writen case Ypo
2022-05-14 22:32 ` Juan Manuel Macías
2022-05-15 10:40 ` Ypo
2022-05-15 13:58 10% ` Juan Manuel Macías
2020-12-13 16:28 #+include and org-export-before-processing-hook Eric S Fraga
2020-12-13 17:26 10% ` Juan Manuel Macías
2021-10-03 15:28 [PATCH] ox-latex.el: Unify in one single list Babel and Polyglossia languages alists Juan Manuel Macías
2022-07-10 9:25 ` Ihor Radchenko
2022-07-14 12:34 ` Juan Manuel Macías
2022-07-17 9:55 ` Ihor Radchenko
2022-07-19 15:01 ` Juan Manuel Macías
2022-07-19 17:01 ` Max Nikulin
2022-07-19 19:31 ` Juan Manuel Macías
2022-07-20 16:12 ` Max Nikulin
2022-07-20 21:30 ` Juan Manuel Macías
2022-07-21 14:36 ` Max Nikulin
2022-07-21 15:39 10% ` Juan Manuel Macías
2021-03-24 1:33 "Org" source blocks and minted Michael Gauland
2021-03-24 4:18 10% ` Juan Manuel Macías
2021-03-24 4:24 ` Timothy
2021-03-26 11:55 10% ` Juan Manuel Macías
2021-03-17 20:29 Syntax Proposal: Multi-line Table Cells/Text Wrapping Atlas Cove
2021-03-17 22:07 ` Juan Manuel Macías
2021-03-18 13:38 ` Atlas Cove
2021-03-18 15:15 10% ` Juan Manuel Macías
2021-03-18 14:26 ` Timothy
2021-03-18 14:31 ` Atlas Cove
2021-03-18 21:58 ` Tim Cross
2021-03-18 22:41 10% ` Juan Manuel Macías
2021-03-20 22:49 ` Samuel Wales
2021-03-21 8:43 9% ` Juan Manuel Macías
2021-03-19 8:08 ` tomas
2021-03-19 8:44 10% ` Juan Manuel Macías
2021-03-19 8:53 ` tomas
2021-03-19 9:22 ` Juan Manuel Macías
2021-03-19 10:14 ` tomas
2021-03-19 10:53 ` Juan Manuel Macías
2021-03-19 13:43 ` tomas
2021-03-19 15:07 9% ` Juan Manuel Macías
2022-06-10 18:28 [Patch] ob-tangle.el: New value 'ascii' for the header argument ':comments' Juan Manuel Macías
2022-06-12 19:18 ` Rudolf Adamkovič
2022-06-12 19:55 ` Juan Manuel Macías
2022-06-13 8:24 ` Rudolf Adamkovič
2022-06-13 10:22 10% ` Juan Manuel Macías
2020-12-27 13:02 A way to avoid unwanted new lines when using paragraph quotes? Kashyap Chamarthy
2020-12-27 13:55 10% ` Juan Manuel Macías
2021-11-28 19:46 "Orgdown", the new name for the syntax of Org-mode Karl Voit
2021-11-28 22:25 ` Juan Manuel Macías
2021-11-28 22:57 ` Tom Gillespie
2021-11-28 23:16 ` Joost Kremers
2021-11-29 3:25 10% ` Juan Manuel Macías
2022-01-07 0:41 Filter to put decorative initial letters Juan Manuel Macías
2022-01-11 0:43 ` William Denton
2022-01-11 16:21 10% ` Juan Manuel Macías
2022-03-16 11:23 leading superscript on a line for ODT export Eric S Fraga
2022-03-16 12:03 ` Juan Manuel Macías
2022-03-16 12:46 ` Eric S Fraga
2022-03-16 13:12 10% ` Juan Manuel Macías
2022-01-15 18:04 org-->html text between @ should be red Uwe Brauer
2022-01-15 18:21 10% ` Juan Manuel Macías
2022-01-15 19:39 ` Uwe Brauer
2022-01-15 19:59 10% ` Juan Manuel Macías
2022-10-27 15:11 Error opening an .org file Renato Pontefice
2022-10-27 15:50 ` tomas
[not found] ` <624F24A1-CC82-45F5-8CB2-D9423A86E023@gmail.com>
[not found] ` <Y1qstDQckZLJR3eb@tuxteam.de>
2022-10-27 16:19 ` Renato Pontefice
2022-10-27 17:21 10% ` Juan Manuel Macías
2021-12-27 1:22 caption width in LateX export Seb
2021-12-27 7:41 10% ` Juan Manuel Macías
2021-04-05 20:48 Choosing a LaTeX Compiler (my predilection for LuaTeX) Juan Manuel Macías
2021-04-05 21:17 ` Dr. Arne Babenhauserheide
2021-04-05 21:36 ` Juan Manuel Macías
2021-04-06 19:03 ` physiculus
2021-04-06 19:46 ` tomas
2021-04-06 20:09 10% ` Juan Manuel Macías
2021-04-06 19:13 ` Juan Manuel Macías
2021-04-07 16:57 ` physiculus
2021-04-07 17:26 9% ` Juan Manuel Macías
2021-04-07 17:53 ` physiculus
2021-04-07 19:52 10% ` Juan Manuel Macías
2021-02-28 20:21 printing org table landscape on complete page Andrés Ramírez
2021-02-28 20:53 10% ` Juan Manuel Macías
2021-10-22 23:27 Sub-figures in Org Mode Jason Ross
2021-10-23 0:00 10% ` Juan Manuel Macías
2021-10-26 17:46 ` Jason Ross
2021-10-30 14:28 10% ` Juan Manuel Macías
2021-02-16 16:30 [question] lisp code in :results header arg.? Juan Manuel Macías
2021-02-16 17:58 ` Berry, Charles via General discussions about Org-mode.
2021-02-16 18:25 10% ` Juan Manuel Macías
2021-09-16 21:40 [PATCH] Fix some typos Stefan Kangas
2021-09-17 9:03 ` Timothy
2021-09-17 10:05 ` Marco Wahl
2021-09-22 16:47 ` Max Nikulin
2021-09-22 20:18 10% ` Juan Manuel Macías
2022-05-07 14:31 [PATCH] org-attach: Attach current Gnus article parts Juan Manuel Macías
2022-05-08 12:30 ` Ihor Radchenko
2022-05-08 13:23 9% ` Juan Manuel Macías
2022-05-27 16:23 how to export an org file, to 2 different locations (in to different formats) Uwe Brauer
2022-05-27 18:42 9% ` Juan Manuel Macías
2022-05-28 0:18 ` Juan Manuel Macías
2022-05-28 6:36 ` Uwe Brauer
2022-05-28 7:23 ` Juan Manuel Macías
2022-05-28 8:40 ` Uwe Brauer
2022-05-28 9:06 10% ` Juan Manuel Macías
2021-05-20 7:14 can't install footnotes in certain table cells Uwe Brauer
2021-05-20 9:57 ` [can't insert footnotes in all table cells] (was: can't install footnotes in certain table cells) Uwe Brauer
2021-05-20 10:06 ` [org-footnote--allow-reference-p] (was: [can't insert footnotes in all table cells]) Uwe Brauer
2021-05-20 10:17 10% ` [org-footnote--allow-reference-p] Juan Manuel Macías
2021-05-20 10:21 ` [org-footnote--allow-reference-p] Uwe Brauer
2021-05-20 10:38 10% ` [org-footnote--allow-reference-p] Juan Manuel Macías
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).