Hi, Greg.
The recent changes to org-contrib's location/structure have been
accounted for on straight's
"develop" branch. Once on that branch you can rely on the default
recipe:
#+begin_src emacs-lisp
(straight-use-package 'org-contrib)
#+end_src
You can see which version of straight
Dear All,
Is it possible to have cross reference in LaTeX export for Org
mode. To be specific: I have a org file segmented into sections, say as
follows:
*** example of Org file, excluding the headers**
* Section 1
contains some text, a label [label:label1] and some citation
Eric S Fraga writes:
> On Tuesday, 4 May 2021 at 01:49, Timothy wrote:
>> For the future, I'd think Julia actually warrants 1st class inclusion in
>> Org, and I've instigated an effort to write an ob-julia that works well.
>
> +1! Happy to help test if you wish. I use Julia as my programming
On 17 May 2021, Nick Dokos wrote:
The online manual is for 9.4 (the released version). What you see in
org-manual.org
is for 9.5 (which AFAIK has not been released yet).
Well, that certainly explains that. I've been running Org from source for years
now, and referring to the (older) online
Hi Garjola,
I had the same problem.
I fixed it by downloading manually the last working version of Org from
https://orgmode.org/elpa/,
i.e. https://orgmode.org/elpa/org-20210503.tar
and manually stored the extracted directory into my elpa directory,
/home/garjola/.emacs.d/elpa/ in your case.
On Tue, May 18, 2021, 11:45 AM Nicolas Goaziou wrote:
> In a rebased "wip-cite-new" branch, I made an modest attempt to write
> a `biblatex' citation processor ...
Looks a bit more than "modest"!
I don't use biblatex either; hopefully some folks that do can test this.
I'm not sure on
On Mon 17-May-2021 at 16:01:25 +02, Nicolas Goaziou
wrote:
> Hello,
>
> Garjola Dindi writes:
>
>> I am using the most recent elpa version of org
>> 9.4.5 (9.4.5-93-gbc857b-elpa @
>> /home/garjola/.emacs.d/elpa/org-20210510/) with emacs master branch.
>>
>> Since updating org yesterday, when I
Lennart,
John's idea seems good. also, you could generate a separate RESULT for
each language, then :var each language's "failed" RESULT into your bash
block and fail if any of them are set?
cheers, Greg
Sorry for the noise, replying to add the X-Woof-Patch:applied header.
Hi ian,
ian martins writes:
> I gave this a try and it works for me. One thing I noticed is that if you
> run a call asynchronously, the final result ends up under the source block
> instead of the call. In the example below both RESULTS were written after
> I ran the call.
>
> #+name:
Hi Bastien,
Bastien writes:
> Please feel free to commit this patch in master so that more people
> can test it, we can test and fix oddities while preparing for 9.5.
OK, I have incorporated the minor fixes from Kyle's review and pushed to
master.
Cheers,
Jack
Hi Bastien,
you know what, I wanna do my part:
https://sr.ht/~aimebertrand/org-mac-link/
Salut
Aimé
Bastien @ 2021-05-18 16:00 :
Hello Aimé,
Aimé Bertrand writes:
I would love to, but don not now what that entails.
Willing to try, but don't wanna break stuff for the community.
Thanks
Hello,
In a rebased "wip-cite-new" branch, I made an modest attempt to write
a `biblatex' citation processor, in the file "oc-biblatex.el".
Here is what is in there. Remarks follow.
--8<---cut here---start->8---
This library registers the `biblatex' citation
On 2021-05-18, 19:31 +0700, Maxim Nikulin wrote:
> The question may be risen in emacs-devel but I am unsure if I will
> participate in discussion.
Why?
>> Can you test this function:
>>
>> (defun org-table--comma-as-decimal-sep ()
>>"Return nil or 2 if separator is dot or comma
Given all the different languages involved, I don't think there is a way to
use a common variable.
One way might be to have each block output some kind of string if it fails,
and then in the last block you could search for the buffer for that string.
Something like this:
* Section 1
Timothy writes:
In src blocks, you have the org-block-begin-line face applied. This (in
any sensible theme) has the same background as org-block.
I might be confused by my own config, but that doesn't seem to be the
case. Unless customized, the =org-block-begin-line= inherits from
Hi Sébastien,
Sébastien Miquel writes:
> Here's such a patch.
Applied, thanks a lot.
>> Also, do you want to become the maintainer for org-src.el? We need
>> more people taking charge of specific areas in Org's code.
> I do intend to keep monitoring this list and help around for the
>
Hello Aimé,
Aimé Bertrand writes:
> I would love to, but don not now what that entails.
> Willing to try, but don't wanna break stuff for the community.
Thanks for your consideration, appreciated.
> - Do I have to stick to sourcehut or can I use gitlab as well?
You can do whatever forge
Dear list,
I am working on a dynamic report in Org mode, where I use source blocks
in various languages to process data. Several blocks produce text or
tables that become part of the PDF on export.
The final chapter should state whether all checks passed, or whether one
or more failed (it is not
Hi Bastien,
Bastien writes:
Before I revert the commit and try your suggestion, can you share a
patch that add both changes (the revert and your fix) manually so I
can test it? If this fixes the original issue while preserving
electric indentation, I'm okay with it.
Here's such a patch.
Hi Sébastien, thanks for your comments.
Sébastien Miquel writes:
> Hi Timothy,
>
> Thanks for your work. I hope this can be merged.
:)
> Here are a few comments.
>
> Doesn't this line in ~org-toggle-inline-results-display~ throw the
> configured delimiters away when called twice ?
> : (setq
Hi Bastien,
I would love to, but don not now what that entails.
Willing to try, but don't wanna break stuff for the community.
- Do I have to stick to sourcehut or can I use gitlab as well?
- I would have to make sure the packages gets into elpa, melpa or
others?
Salut
Aimé Bertrand
Do
It seems, there is no reliable way to work with numbers in a
locale-aware way in emacs. I am still against hard-coded list of
locales. Requirement to customize a variable is rather inconvenient.
Considering such properties as a part of translation is a little better
but I prefer to avoid it.
Hi Timothy,
Thanks for your work. I hope this can be merged.
Here are a few comments.
Doesn't this line in ~org-toggle-inline-results-display~ throw the
configured delimiters away when called twice ?
: (setq org-inline-src-prettify-results (not
org-inline-src-prettify-results))
I think the
On 2021-05-16, 23:24 +0700, Maxim Nikulin wrote:
> On 14/05/2021 21:54, Utkarsh Singh wrote:
>> On 2021-05-13, 00:08 +0700, Maxim Nikulin wrote:
>>
>>> Comma is decimal separator for es_ES, de_DE, ru_RU, etc. The point is
>>> that order in which separator candidates are tried should depend on
Hi Sébastien,
Sébastien Miquel writes:
> The commit `bfda3cc7df31fa79222efb4c190618c3c85a3d04` breaks automatic
> (electric) indentation in src blocks for all configurations.
Yes, this was intentional: there are many variables interfering in
this area, and preventing electric indentation for
Bonjour Aimé,
Aimé Bertrand Ntumwa-Nziza writes:
> as per your wish and hint (thanx).
Thanks, applied to https://git.sr.ht/~bzg/org-contrib
Please see the README in https://git.sr.ht/~bzg/org-contrib
Do you want to take over maintainership of org-mac-link.el?
If so, please set up a
27 matches
Mail list logo
