n the buffer,
but I can't find a way to reliably trigger a "setup refreshment" of these
options from `emacs-lisp`.
Any ideas ?
Sincerely yours,
--
Emmanuel Charpentier
Le mercredi 17 avril 2024 à 22:41 +0200, Emmanuel Charpentier a écrit :
[ Snip... ]
A couple more data points :
* The problem I described happens when I run `emacs` on files
belonging in a Windows tree, symlinked to the Linux tree. Running
`emacs` on files outside this symlinked tree works
Le mercredi 17 avril 2024 à 20:18 +, Ihor Radchenko a écrit :
> Emmanuel Charpentier writes:
[ Snip... ]
> What if you do M-x trace-function org-compile-file-commands
No such function : I just have org-compile-file , which I traced.
>
> and run the preview.
> Then,
Le mercredi 17 avril 2024 à 16:48 +, Ihor Radchenko a écrit :
> Emmanuel Charpentier writes:
>
> > I have a case where the current way of forcing the temporary
> > directory
> > to me `/tmp` is wrong. Running emacs on Ubuntu **under WSL2**,,
> > exporting la
On 25/03/2024 19:49, Max Nikulin wrote:
> > (defun org-ensure-tmp-dir (dir-symbol prefix)
> > (let ((dir (symbol-value dir-symbol)))
> > ;; Temporary directory has not been cleaned.
> > (or (and dir (file-directory-p dir) dir)
>
>
>`if' should be used instead of `or' here.
>
>
>
>>
>>
\usepackage{rotating}
\usepackage[normalem]{ulem}
\usepackage{amsmath}
\usepackage{amssymb}
\usepackage{capt-of}
\usepackage{hyperref}
\usepackage{minted}
\usepackage{fontspec}
\setmonofont{Unifont}
\date{\today}
\title{}
\hypersetup{
pdfauthor={Emmanuel Charpentier},
pdftitle={},
pdfkeywords=
Le jeudi 11 août 2022 à 12:32 +, Fraga, Eric a écrit :
> On Thursday, 11 Aug 2022 at 13:51, Emmanuel Charpentier wrote:
[ Snip... ]
> > Why locally ?
>
> In case you have different configurations.
Nice idea ! I was (still am) aiming at a "default configuration" I
Le jeudi 11 août 2022 à 09:48 +, Fraga, Eric a écrit :
> On Thursday, 11 Aug 2022 at 10:00, Emmanuel Charpentier wrote:
> > Since about a week, exporting directly to Beamer ceased to work.
> > See
> > the attached Minimal.org file :
> > Debugger entered--Lisp
--
which isn't very helpful... Any hint would be welcome.
Sincerely yours,
--
Emmanuel Charpentier
PS : CC me would be appreciated : I'm not on the list, and read it via
the archive...
# Pour débugguer l'exportation Beamer
#+begin_src emacs-lisp :exports none :results sile
derstand why my
test used to succeed... A better patch will follow ( but not
tonight...).
HTH,
--
Emmanuel Charpentier
Le mercredi 03 novembre 2021 à 17:19 +0100, Nicolas Goaziou a écrit :
> Hello,
>
> Emmanuel Charpentier writes:
>
> > This (minuscule) patch allows to pass a relative (to the buffer's
> > default directory) file name to denote the CSL style file.
>
>
"A quick LaTeX reference guide"...
Nice oxymoron !
--
Emmanuel Charpentier
-+-|
| 0 | 0 |
| 1 | 1 |
| 2 | 4 |
| 3 | 9 |
| 4 | 16 |
#+name: testplot
#+begin_src gnuplot :var data=table0 :exports results
reset
plot data with linespoints
#+end_src
HTH,
--
Emmanuel Charpentier
You may find this John Kitchin's blog post illuminating.
HTH,
--
Emmanuel Charpentier
ansferred my rights to GNU for emacs-
related works.
--
Emmanuel Charpentier
From 80e4121f8a74aec1e5638713ce7af8e041404e44 Mon Sep 17 00:00:00 2001
From: Emmanuel Charpentier
Date: Tue, 19 Oct 2021 19:57:17 +0200
Subject: [PATCH] oc-csl : accept relative CSL filenames
---
lisp/oc-csl.el |
shape is lost to the processing function.
I am looking for explanations and/or hints.
Attached : the source of the present mail.
Thanks in advance...
--
Emmanuel Charpentier
#+options: author:nil toc:nil
#+property: header-args:python :session
# #+latex_header: \usepackage{minted}
#+begin_src
deux phrases.
- =Org= -> Org
- J'enlèverais la partie introductive expliquant pourquoi il est utile
de citer le travail d'autrui. Ceci dit, il vaut mieux attendre l'avis
d'autres personnes concernées par la fonctionnalité.
[ Emmanuel Charpentier : I think that this justificatio
laced by incises or footnotes ... or proper citations.
--
Emmanuel Charpentier
retty common in scientific papers
> and proposals to see that.
>
> It may not make sense to make an @misc bibtex entry for that purpose,
> since it is a one time citation for that document, and is like a
> lambda reference.
The problem with that approach is that the reader has to somehow
reverse your function (which is by no way guranteed to be
bijective...).
--
Emmanuel Charpentier
TstNatBib.tar.gz
Description: application/compressed-tar
of
the bibliographic relation...
> This isn't currently recognized as a cite, but something like this
> seems like a reasonable solution to me.
> [cite/text:@ private communication]
Such special casing is probably a bugs' nest... err.. hive. And
pointless, as explained /supra/.
HTH,
--
Emmanuel Charpentier
> John
but is still less straightforward. I'd rather
have a documented, understood way to export LaTeX snippets/ blocks
marked as such explicitly exported to ODT...
Hope this is clearer,
--
Emmanuel Charpentier
Le dimanche 18 juillet 2021 à 22:25 +0800, Timothy a écrit :
>
> Hi Emmanu
at are the consequences.
Having an option allowing latex code marked as such to be passed to
other exporters (possibly with conversion) would allow a "cleaner"
solution.
What do you think ?
--
Emmanuel Charpentier
once by the function execution and once by the "#+results:"
paragraph.
John's black magic with drawers allows to keep the link between
function and results.
HTH,
--
Emmanuel Charpentier
Le mercredi 14 juillet 2021 à 14:41 +0800, Timothy a écrit :
>
> John Kitchin w
ing
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>
>
>
> On Sun, Jul 4, 2021 at 2:51 PM Emmanuel Charpentier
> wrote:
> > I tried this :
> >
> > #+property: header-args:sage :session
> > #+opt
is problematic if you want to use caching... Exporting
LaTeX blocks to ODT/HTML would be a better solution...
Ideas ?
Le dimanche 04 juillet 2021 à 14:10 -0400, John Kitchin a écrit :
> Can you declare the output as org so they will just be latex
> snippets?
>
> On Sun, Jul 4, 2021 at 3:4
ODT.
I'm currently lookin into a =:post= workaround. But an option to export
=latex= blocks to selected exporters (ODT, HTML, possibly Morkdown via
pandoc).
I'll keep you posted.
Le dimanche 04 juillet 2021 à 14:10 -0400, John Kitchin a écrit :
Can you declare the output as org so they w
Dear list,
Org-mode offers the ability to create functions returning LaTeX results
: such occurrences are frequent with Sagemath, Maxima, Mathematica, R,
and even emacs's Calc...
Such functions can be declared has having LaTeX output, and the
resulting =#+begin_export latex ... #+end_export lat
rg-mode...
Sincerely yours,
--
Emmanuel Charpentier
I get this code ?
Related question : is there an ETA of these new abilities in =Org= ?
--
Emmanuel Charpentier
blishers not
accepting \LaTeX ? I suspect medicine...
HTH,
--
Emmanuel Charpentier
more fundamental problem with this
useful potential feature ?
I am aware that I can get this in the \LaTeX export of the document by
inserting ~\listoffigures~ at the right place. Bit this won't export to
other formats.
Thoughts ?
--
Emmanuel Charpentier
ted.
* The exact list name has as "s" after "package".
* I'd give a full ~emacs-lisp~ snippet (but I agree that this is
disputable...).
Care fo a formal patch ?
HTH,
--
Emmanuel Charpentier
ailable in Org 9.3. Hopefully, it should not be long, even
> though
It's clear now. Thanks !
--
Emmanuel Charpentier
> I have no ETA. I'm Cc'ing Bastien as he may know.
>
> Regards,
>
Le mardi 23 avril 2019 à 10:26 +0200, Nicolas Goaziou a écrit :
> Hello,
>
> Emmanuel Charpentier writes:
>
> > Le lundi 22 avril 2019 à 15:26 +0200, Nicolas Goaziou a écrit :
> > > Emmanuel Charpentier writes:
> > >
> > > > Do you want a
Dear Nicolas,
Thanks for the clarification. I misread the documentation.
Sorry for the noise...
--
Emmanuel Charpentier
Le samedi 04 mai 2019 à 23:00 +0200, Nicolas Goaziou a écrit :
> Hello,
>
> Emmanuel Charpentier writes:
>
> > Org-mode tables do export with thei
setup{
pdfauthor={Emmanuel Charpentier},
pdftitle={},
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs 26.1 (Org mode 9.2.3)},
pdflang={English}}
\begin{document}
The table \ref{tab:orge528190} , manual conversion and rough
approxomation of
\ref{tab:orgb3737d9}, erports correcly, while the orgina
happening when minted is *NOT*
used.
HTH,
--
Emmanuel Charpentier
[ Previous posts : Snip... ]
Title: Test of source block exports
The Python block 1 generates the figure 1
Figure 1: Figure generated by python
Listing 1: Python code generating a figureimport matplotlib, numpy
matp
ially,
--Emmanuel Charpentier
Le mardi 30 avril 2019 à 13:46 -0400, John Kitchin a écrit :
> This works as expected in LaTeX for me with org-ref (you could
> probably use raw latex if you wanted):
> #+caption: The first source block. label:src-1#+BEGIN_SRC
> ipythonprint('
Hi, Nicolas !
Le mardi 30 avril 2019 à 19:05 +0200, Nicolas Goaziou a écrit :
> Hello,
>
> Emmanuel Charpentier writes:
>
> > Whereas the HTML exporter correctly recognize a source block as
> > such,
> > the LaTeX/PDF exporter does not.
> >
> > This c
(remaining bugs, etc..) to prepare a patch-
request (I'm not much of a programmer...).
Back to the problem at hand : I'm still bugged by the fact that ox-
pandoc does the right thing in the present case (as well as the built-
in HTML exporter, by the way), and that the built-in LaTeX exporter is
buggy. I just posted a formal bug report limited to this.
Cordially yours,
--
Emmanuel Charpentier
I shall report formally the problems mentioned in
http://lists.gnu.org/archive/html/emacs-orgmode/2019-04/msg00240.html,
trying to isolate them as much as possible. I'll start with the
simplest (and, IMHO, the most annoying).
Whereas the HTML exporter correctly recognize a source block as such,
t
.
Indeed I just checked that its exported docx can be converted by pandoc
into a "correct" docx (correct here meaning that my captions are
correctly labelled and numbered).
Have to think again...
--Emmanuel Charpentier
Le lundi 29 avril 2019 à 17:23 -0400, John Kitchin a écrit :
> I th
versity
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>
>
>
> On Mon, Apr 29, 2019 at 1:06 PM Emmanuel Charpentier <
> emm.charpent...@free.fr> wrote:
> > Dear list,
> >
> >
> >
> >
as advertised.
So I have a couple of questions:
* What can be done to reconcile org-ref's, latex-exporter's and ox-
pandoc's requirements for bibliographies ?
* How to fix the pdf exporters' quirks with code snippets ?
HTH,
--
Emmanuel Charpentier
Le lundi 22 avril 2019 à 15:26 +0200, Nicolas Goaziou a écrit :
> Emmanuel Charpentier writes:
>
> > Do you want a direct answer or a partch against /etc/ORG-NEWS ?
>
> Anything that suits you.
A patch it is (enclosed).
If this documentation is customaty, this should b
Possible duplicate answer (my email provider isn't very reliable at the
moment...).
Le lundi 22 avril 2019 à 14:04 +0200, Nicolas Goaziou a écrit :
> Hello,
>
> Emmanuel Charpentier writes:
>
> > Attached is my proposal for the feature I suggested. My quick tests
>
Attached is my proposal for the feature I suggested. My quick tests
pass[1]. Better tests by someone knowledgeable in graphics would be
useful, as well as a test in the test suite.
HTH,
--
Emmanuel Charpentier
[1] I get unrelated failures from "make test" :
4 unexpected results:
mechanism may be implemented for the HTML exporter.
--
Emmanuel Charpentier
Thanks ! Ths switch excaped my attention, probably because it is buried
in a "literal example" section, which I didn't connect to noweb care
and feeding...
Maybe the "noweb" section might benefit of a discrete recall of
relevant switches ?
Thanks again !
--
Emmanuel
=
The indentation is not respected in the included JAGS snippets. Further
attempts with exporting to PDF (both the built-in exporter and ox-
pandoc) and DOCX (ox-pandoc) show that the problem remains the same,
but, IIRC, with slight variations in whitespace.
That's not serious (just ugly) for R/JAGS ; but it might be serious for
Python/Sage, where whitespace is syntaxic.
Thoughts ?
--
Emmanuel Charpentier
t;
End of block called from an Org Python block
>>> # Kept to pacify Org...
... FN
'Bidule.txt'
>>>
>>> open('/tmp/babel-2gEcoQ/python-r1nkjR', 'w').write(str(_))
>>>
>>>
>>> 'org_babel_python_eoe'
'org_babel_python_eoe'
>>>
=
Possibly relevant : from (packages-list-packages) :
python-mode20181223.1933 installed Python major
mode
Also posibly relevant : a very similar Sage block, whose edit mode is
sage-shell-mode, runs without problem.
I'm lost. Suggestions ?
--
Emmanuel Charpentier
anuel Charpentier
Le samedi 02 mars 2019 à 22:11 +0100, Emmanuel Charpentier a écrit :
> Dear list,
>
> I would like to use Sage to build the text of a Graphviz program to
> display some graph, then pass this program body to a dot code block.
>
> The first step is easy. But I
://emacs.stackexchange.com/questions/20652/org-babels-call-functionality-wraps-all-results-in-quotes
][seems]]
that a similar problem exists for Python code...
Any suggestions ?
--
Emmanuel Charpentier
gt;
L
#+end_src
===
Thanks a lot !
--
Emmanuel Charpentier
Le lundi 04 février 2019 à 18:03 +0100, Nicolas Goaziou a écrit :
> Hello,
>
> Robert Pluim writes:
>
> > John Kitchin writes:
> >
> > > #+RESULTS:
> > > : <<
s I've read so far suggests anything about the length of a block
identifier, I consider this a bug in the Python language support code.
What do you think ? Any hint ?
Thanks a lot !
--Emmanuel Charpentier
> John
>
> ---
> Professor John K
, 'w').write(str(_))
│ >>>
│ >>>
│ >>> 'org_babel_python_eoe'
│ 'org_babel_python_eoe'
│ >>> L=[]
│ >>> for i in range(1,6):
│ ... L.append(i)
│ ...
│ >>> L
│ [1, 2, 3, 4, 5]
│ >>>
│ >>> open('/tmp/babel-OJSsxf/python-fW5gK0'
, 'w').write(str(_))
│ >>>
│ >>>
│ >>> 'org_babel_python_eoe'
│ 'org_babel_python_eoe'
│ >>> L=[]
│ >>> for i in range(1,6):
│ ... L.append(i)
│ ...
│ >>> L
│ [1, 2, 3, 4, 5]
│ >>>
│ >>> open('/tmp/babel-OJSsxf/python-fW5gK0'
tree.
I'm afraid to be a bit out of my depth here...
Suggestions ?
--
Emmanuel Charpentier
Le lundi 24 décembre 2018 à 01:24 +0100, Emmanuel Charpentier a écrit :
> Dear list,
>
> I have a couple of gripes about LaTeX handling in ODT export when one
> needs MathML conversion
ble should be tested, and the test for the jarfile
should be done *only* if executable is "java" (or, better, belongs to a
list of "reasonable" java executables or scripts...).
So my second question is : what do you think ?
HTH,
--
Emmanuel Charpentier
sly a list of figures and list of listings
* No list of figures bt by direct use of "\listoffigures" in LaTeX.
Shouldn't we consider this a bit of a misdesign ? I dont (yet) seem a
way to en hance this.
Suggestions ?
--
Emmanuel Charpentier
> Best wishes,
>
> Emmanuel Charpentier
demonstrating the use of this exporter's options to enable the
addition of the needed features (figure inclusion, tables of tables /
figures / listings, etc...) ? The "manual" available as a README is way
too terse to be usable without diving in the source code and pandoc's
docume
Thanks ! I'll make a sixth attempt...
--
Emmanuel Charpentier
Le mer. 19 déc. 2018 à 16:04, Eric S Fraga a écrit :
> On Wednesday, 19 Dec 2018 at 15:39, Emmanuel Charpentier wrote:
> > Could you let me know if some attachments are blocked by the list manager
> > or mail ser
server ?
Tkanks in advance,
--
Emmanuel Charpentier
Rights transferred to FSF (scanned signed copy of the form set to
ass...@fsf.org).
HTH,
--
Emmanuel Charpentier
Le dim. 2 déc. 2018 à 21:26, a écrit :
> Dear all,
>
> Please find enclosed a proposed patch (against master) to document the
> need for babel/polyglossia in or
; > described, whereas export to latex needs (undocumented)
> > supplementary
> > steps.
> >
> > At the very minimum, this need for further config should be
> > mentioned
> > in the docs ; preferably, a default should be proposed.
>
> See above about
l's (and polyglossia's)
abilities by specifying a set of possible #+language:s (first
call) or switch to another language (further calls down the
file...).
* concerning french: I understand that "frenchb" is obsolete and
that one should use "french" inst
or not, believe it or not, this setup is sufficient to create the
problem I reported.
HTH,
--
Emmanuel Charpentier
Le mar. 27 nov. 2018 à 15:20, Eric S Fraga a écrit :
> On Sunday, 25 Nov 2018 at 21:36, emanuel.charpent...@gmail.com wrote:
> > I forgot to add that, when exporting to pla
or and date), "#+language: fr"
remains in red, even after C-c C-c. (Approximate colors : I'm semi-
color-blind).
HTH,
--
Emmanuel Charpentier
Le dimanche 25 novembre 2018 à 23:31 +0100, Nicolas Goaziou a écrit :
> Emmanuel Charpentier writes:
>
> > Thanks for a prom
One more data point : I can reproduce the problem with no init file :
* same org file
* emacs started by "emacs -q"
* M-x (require 'org)
* C-x C-f TstLanguage.org
* C-c C-e l p
==> Same result.
HTH,
--
Emmanuel Charpentier
Le dimanche 25 novembre 2018 à 20:03 +010
Thanks for a prompt answer ! A couple questions :
1) What do you mean by "minimal configuration" ? A stripped
.emacs/d/init.el ?
2) How can I get the "development version" ? I'm following MELPA
already...
--
Emmanuel Charpentier
Le dimanche 25 novembre 2018 à 20:03
call,
but nothing even remotely babel-related (i. e. nothing related to the
LaTeX package babel, which isn't loaded...)
- the PDF file has a table of contents entitled "Contents".
HTH,
--
Emmanuel Charpentier
# Vérification d'un loup possible sur #+language...
#+title
71 matches
Mail list logo
