I'm creating this patch because the prologue and epilogue header
arguments can be useful for SQL code blocks. For example, in PostgreSQL
:prologue can be used for setting the schema name where operations are
to be executed (see example below)
#+BEGIN_SRC org
* The foo schema
:PROPERTIES:
:HEADER-
On Friday, 2 Jul 2021 at 20:56, Uwe Brauer wrote:
> Now I want to add also result and new, but only the first two rows, the
> only way to do it seems to be your original approach.
At this point, you need to start using more advanced formulas,
e.g. involving conditionals, maybe. You could do arit
On Saturday, 3 Jul 2021 at 00:33, Nicolas Goaziou wrote:
> If you have so many keys, you shouldn't be using Org Cite Basics in the
> first place!
Nicolas,
I think there's a conceptual misunderstanding here (and it could be
mine, of course).
My bibliography database contains thousands of entries
On 2021-07-02, Matt Price wrote:
> Hi,
>
> (cc:ing Jens L. in case this is relevant for his dev work on org-re-reveal).
Hi Matt,
just a quick reply: Yes, that is certainly relevant for me, but I do
not have the time to investigate this at the moment. Note that I
use references with org-ref and
Hello,
Eric S Fraga writes:
> On Saturday, 3 Jul 2021 at 00:33, Nicolas Goaziou wrote:
>> If you have so many keys, you shouldn't be using Org Cite Basics in the
>> first place!
> I think there's a conceptual misunderstanding here
[...]
> My bibliography database contains thousands of entrie
On Fri, Jul 2, 2021 at 4:05 PM Nicolas Goaziou wrote:
> "Bruce D'Arcus" writes:
> > If I select that, "nil" is added to the citation, so that the result
> > is "[cite/nil:@key]".
>
> That's expected. "nil" is the name of the processor's fall-back style,
> ignoring any inheritance. It is differe
Hello,
"Bruce D'Arcus" writes:
> On Fri, Jul 2, 2021 at 4:05 PM Nicolas Goaziou wrote:
>> That's expected. "nil" is the name of the processor's fall-back style,
>> ignoring any inheritance. It is different from the empty style (""),
>> which takes into account inheritance.
>
> Two things:
>
>
On Sat, Jul 3, 2021 at 5:20 AM Nicolas Goaziou wrote:
> > First, after adding a style, I can't see how to subsequently remove it
> > using this interface, to just have "[cite:@key]". Is that possible?
>
> Of course. Just select the empty string instead of an entry. It is done
> with C-j on Select
I am giving up with this issue.
My summary. New function `mailcap-view-file' has a problem similar to
Bug#44824 (kde-open5 and "gio open" called directly or through xdg-open
are unreliable in Emacs, I consider it as fixed in Org mode) that was
reported by several users and refused by developer
> From: Maxim Nikulin
> Date: Sat, 3 Jul 2021 18:29:30 +0700
>
> I am giving up with this issue.
That's too bad. I see no reason to give up, and I urge you to
reconsider, please.
> >> Because of I can not imagine such case for mailcap handler in Emacs yet
> >> and, accordingly to you, "this co
Timothy writes:
> Would it be strange if running the code block with just
>
> :output graphics
>
> Automatically added "link" if *only* graphics is set, and generated a
> file name if no :file is set?
It wouldn't be strange. ob-jupyter [1] auto-generates file names for
images, and it's convenien
Apparently, A ">" character was accidentally inserted in the first line
of the patch. I'm attaching the patch again.
--
La información contenida en este e-mail y sus anexos es confidencial,
privilegiada y está dirigida exclusivamente a su destinatario, en
consecuencia, solo puede ser utiliza
On Saturday, 3 Jul 2021 at 09:58, Nicolas Goaziou wrote:
> My tongue in cheek answer was about the weakness of the Org Cite
> _Basic_ library. [...] I was merely pointing out that this is not the
> scope of the demo for the interface I wrote.
Ah ha, there was indeed a basic conceptual misunders
On Sat, Jul 3, 2021 at 10:58 AM Eric S Fraga wrote:
> > Anyway, I'll try to provide something a little more useful out of the
> > box, based on your comment and Bruce D'Arcus suggestion.
>
> But that's partly why I mentioned ivy-bibtex: solutions already exist
> and there should be no need to re-
I’ve found a few partial solutions:
1)
#+begin_src emacs-lisp :results raw :exports (if (eq org-export-current-backend
'beamer) "results" "none")
(eval (concat "#+begin_src python\n print('Hello, world')\n#+end_src"))
#+end_src
This prints the python code if exporting to Beamer and not if e
hi.
i am trying to simplify adding regression test cases to a program.
to generate the base, "compared-to" results, i want to write some code
in a source block, then evaluate it, producing the "true" value.
then, later during development, i want to check if the code that ran in
that block gives
Hello Jack,
Many thanks for the feed back
On Friday, 2 Jul 2021 at 21:21, Jack Kamm wrote:
> Hi Jeremie,
>
>>> The requirement for a second file parameter was added in Org 9.3 to
>>> support the use case in this thread:
>>>
>>> https://orgmode.org/list/3ac2f42a-8ff2-1464-fa36-451e2ef0e...@pressu
Sorry if I have misunderstood the proposals here, but ...
A user might like to construct a figure consisting of various subfigures such
as in a subfloat environment.
Will this be reasonably simple to accomplish if `:results graphics' (with no
`file' element) automatically inserts a link?
Curre
> On Jul 3, 2021, at 9:35 AM, Greg Minshall wrote:
>
> hi.
>
> i am trying to simplify adding regression test cases to a program.
>
> to generate the base, "compared-to" results, i want to write some code
> in a source block, then evaluate it, producing the "true" value.
>
> then, later dur
Hi Chuck,
> A user might like to construct a figure consisting of various subfigures such
> as in a subfloat environment.
>
> Will this be reasonably simple to accomplish if `:results graphics' (with no
> `file' element) automatically inserts a link?
>
> Currently, omitting the file element leav
Thanks Jens!
I've added some comments in the issue you linked to, but in the meantime
I've also come up with what seems to be at least a semi-viable hack for
adding native CSL citation support to org-re-reveal. It involves creating
two new variables and then let-setting `citeproc-fmt--formatters-a
I found `org-notify` does not support macOS desktop notification. So I write a
small patch for this.
Thanks for reviewing.
0001-org-clock.el-Make-org-notify-support-macOS-notificat.patch
Description: Binary data
Chuck,
thanks. (i'm not surprised at an e-lisp suggestion from you! :)
i worry about accidental modification of the base case results during
the chaos of development. it occurs to me (reading through
(org-babel-ref-resolve)) to keep my base case source blocks marked with
[:results silent], whic
On 04/07/2021 07:23, stardiviner wrote:
I found `org-notify` does not support macOS desktop notification. So I write a
small patch for this.
I am surprised that there is no OS-agnostic function in Emacs that sends
simple notification, suitable when no advanced feature are necessary.
Only OS-
24 matches
Mail list logo
