Maxim Nikulin writes:
[utf8x]
> Maybe, I have seen such warnings. However I have tested neither utf8
> nor utf8x on real examples. That is why I am unaware what can be
> broken in particular. For small examples with various symbols
> outside of ASCII, utf8x may give better support.
The main poin
John Kitchin writes:
> #+RESULTS: foo
> :results:
> \[\displaystyle{\sin\left(\frac{a}{b}\right)}\]
> :end:
>
> the key is the drawer I think.
FYI as of
https://code.orgmode.org/bzg/org-mode/commit/b90b850ae8be46a1ebe7d13b05ad79869e8d1032
a LaTeX environment will "just work". i.e.
#+RESULTS:
fwiw, this may depend on the source language (rather than -- solely? --
on org interpretation of the output block:
#+begin_src R
data.frame(a=c("this", "is", "a", "test"), b=c("tset", "a", "si", "oot,
siht"))
#+end_src
#+RESULTS:
| this | tset |
| is | a |
| a| si|
|
I'm using https://github.com/bastibe/org-static-blog to generate
http://members.wolfram.com/billw
See especially
http://members.wolfram.com/billw/2021-07-05-romanovsky-on-bronstein.html
I have an org file full of these things to denote side-by-side columns of
English and Russian text:
@@htm
one thing about org that i think has been making it complex, in
addition to number of features, is non-orthogonality.
On 7/13/21, Tim Cross wrote:
>
> Tom Gillespie writes:
>
> [snip]
>
>>
>> Once I wrap up the formal grammar for org, one of the next things I
>> plan to work on is a clear specif
Tom Gillespie writes:
[snip]
>
> Once I wrap up the formal grammar for org, one of the next things I
> plan to work on is a clear specification for org babel. This is
> critical because so many of the suggestions that come in deal with
> individuals' specific problems and thus fail to account
*** More reliable sources and less fake news! ***
To everyone involved: Thank you for making the world a better
place.
R+
Nicolas Goaziou writes:
Hello,
It took years, but citations are now full part of Org syntax.
Thanks to everyone involved over the time!
Now, it needs to be documen
In implementing an extension you might consider doing it as a generalized
form of what I did with ob-racket (https://github.com/togakangaroo/ob-racket
).
I think it is best to rely on the import/require/include mechanism of the
language you're using. Pretty much all of them support adjacent files.
We have been receiving many new feature suggestions and requests
coming in for org babel. I think that Tim's suggestion is the right
one. Nearly all of these need to be implemented as an extension first
and tested independently. Further, even if this is done, it should be
clear that there is zero e
On Tue, 13 Jul 2021 at 21:06, Alan Ristow wrote:
>
> Also, thanks to Ihor and Bhavin for your work on this. Prior to applying
> the patch, I was noticing new bizarre behavior relating to recurring
> tasks. I haven't been running the patched org very long yet, but so far,
> so good.
Thank you for
Sorry, that escaped too soon. I meant to say that
#+attr_org: :width 300
wasn't resizing the images in the Org buffer to 300 pixels wide. Turned out it
wasn't Imagemagick, it was the variable org-image-actual-width, which was set to
ignore any attr_* directives. I changed that and now it'
Hi Maxim,
Maxim Nikulin writes:
> I do not know if new engines allows to get list of available fonts and
> to choose a set of fonts with better coverage than lmodern.
LuaTeX and XeTeX use harfbuzz as OpenType rendering engine. On
LuaLaTeX and XeLaTeX you must use the fontspec package
(https://ww
Following up on this two years later ...
I had some images that I wanted to shrink in my Org buffer, but
#+attr_org:
(setq org-image-actual-width nil)
I had the variable set to t: "When non-nil, use the actual width of images when
inlining them." There are a few other options, but nil do
On 10/07/2021 23:44, Stefan Nobis wrote:
Maxim Nikulin writes:
(add-to-list 'org-latex-inputenc-alist '("utf8" . "utf8x"))
so I am unaware whether \usepackage[utf8x]{inputenc} has any drawbacks.
Do not do this. Both, utf8x and ucs, are obsolete and deprecated for
quite some time.
Maybe, I h
Is there a timeline for when this will be available in orgmode.org/elpa or
other package repository? I tried it today, but it doesn't seem to be there
yet, at least not in this version:
Org mode version 9.4.6 (9.4.6-10-gee652a-elpaplus @
/Users/jkitchin/Dropbox/emacs/scimax/elpa/org-plus-contrib-2
On 7/13/21 4:55 AM, Carlo Tambuatco wrote:
Newbie question: what command do I use to apply the patch…?
I can tell you what worked for me. I think you probably need to have
cloned org using git for it to work, but I am far from being a git wiz
so there could be a workaround I don't know about
This link (
https://stackoverflow.com/questions/36926513/are-there-elisp-functions-that-list-markers-in-a-given-buffer)
suggests there is not a good way to find all the markers associated with a
buffer.
John
---
Professor John Kitchin (he/him/his)
Doherty Hall A207
Hello,
I'm using #+BEGIN_SRC sh code blocks and org-mode nicely renders the
output as a table:
#+BEGIN_SRC sh
echo FIRST SECOND THIRD
echo first second third
#+END_SRC
#+RESULTS:
| FIRST | SECOND | THIRD |
| first | second | third |
And this is very nice. Unfortunately the autodetection
18 matches
Mail list logo