I'm figuring out complex citation objects with prefixes and suffixes and
multiple keys, and found that not all styles export properly (from what I
understand). Here's an Org file that runs through all the citation styles (the
Basic.bib is below). Each citation object has a global prefix
Matt writes:
> On Sat, 13 Jan 2024 19:00:16 +0100 Ihor Radchenko wrote ---
>
> > Since posh is POSIX-compliant, generic PS1/PS2 variables should work, and
> we
> > do not need a special entry in `org-babel-shell-set-prompt-commands' -
> > we can remove "posh" record from there.
>
The attached patch makes names in ob-shell.el use the same prefix
"org-babel-shell-" (along with a few similar minor consistency
updates).
Without the patch, three naming conventions exist:
- org-babel-shell
- org-babel-sh
- ob-shell <- that's my fault :)
The Org Babel shell library was
Uwe Brauer via "General discussions about Org-mode."
writes:
> #+NAME: many-cols
> | a | b | c |
> | d | e | f |
> | g | h | i |
>
> #+NAME: hline-please
> #+BEGIN_SRC python :var tab=many-cols :hlines yes
> return tab
> #+END_SRC
>
> #+RESULTS: hline-please
> | a | b | c |
> | d | e | f |
> | g
Hi,
The documentation for `org-latex-caption-above’ seems to imply that it can be
set to a non-nil value to always place captions at the start of environments,
instead of the end. However, with a non-nil value which is not a sequence,
exporting something like the following from org causes an
On Sat, 13 Jan 2024 19:00:16 +0100 Ihor Radchenko wrote ---
> Since posh is POSIX-compliant, generic PS1/PS2 variables should work, and we
> do not need a special entry in `org-babel-shell-set-prompt-commands' -
> we can remove "posh" record from there.
>
> I'd rather keep the
fixed version of the attachment;; open this file with command
;; emacs --no-splash -q -mm how_to_write_a_context_export_backend_v01.el
;; In "emacs-lisp" dropdown menu above, select "evaluate buffer"
;; then, a first Ctrl-c Ctrl-c will compile
;; finally, a second Ctrl-c Ctrl-c will bring you
> Uwe Brauer via "General discussions about Org-mode."
> writes:
> No, this is because you customized `org-src-preserve-indentation' or
> `org-edit-src-content-indentation', while the provided example only
> works with default indentation settings. Python is sensitive to
> whitespace and your
Hi all,
I try to learn how to start a new back-end for ConTeXt
(https://wiki.contextgarden.net).
There is already a version based on ox-latex.el
(https://github.com/Jason-S-Ross/ox-context/)
but in order to contribute I wanted to learn the basics.
I started a first elisp script (attached).
Uwe Brauer via "General discussions about Org-mode."
writes:
> I tried to use the examples of the above link
> ...
> #+NAME: no-hline
> #+BEGIN_SRC python :var tab=many-cols :hlines no
> return tab
> #+END_SRC
>
> Now already the first failed:
> ,
> |
> | File "", line 4
> | return
Mark Barton writes:
>> Not so easy for src block and other verbatim text - there is simply no
>> way to escape "|" in tables.
>
> ...
> In your example of the src block, I don't normally make those headers, but
> could the pipe char be replaced only in the clock table? If clock table links
>
Ihor Radchenko writes:
>> #+caption: Schematic
>> [[https://www.draketo.de/wissen/essd-14-4811-2022-f02-web--cc-by.png][file:essd-14-4811-2022-f02-web--cc-by.png]]
>> ...
Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=38c6eb2b7
--
Ihor Radchenko // yantar92,
On 14.01.2024 20:18, gerard.vermeu...@posteo.net wrote:
On 14.01.2024 13:16, Ihor Radchenko wrote:
gerard.vermeu...@posteo.net writes:
[...]
I tried make test and the tests are still failing with this new patch:
1 unexpected results:
FAILED test-ob/demarcate-block ((should (string=
Hi
I tried to use the examples of the above link
#+NAME: many-cols
| a | b | c |
|---+---+---|
| d | e | f |
|---+---+---|
| g | h | i |
#+NAME: no-hline
#+BEGIN_SRC python :var tab=many-cols :hlines no
return tab
#+END_SRC
Now already the first failed:
,
|
| File "", line 4
|
Ihor Radchenko writes:
> Joseph Turner writes:
>
>>> See `org-open-file' IN-EMACS argument - we may use different handlers
>>> to open file links. Currently, IN-EMACS can be 'system or 'emacs. But
>>> nothing stops us from adding more options.
>>
>> Thanks! Are you suggesting something like
15 matches
Mail list logo
