Hi Andreas,
I don't know if this is a bug, but I would say that in principle it's
the expected result. Single quotes are understood here as inner quotes
or second-level quotation marks, therefore they are only activated
nested in text with first level quotes: " ... '...' ... "
lorem "ipsum 'dolor
In an earlier discussion, people raised the issue of fontification and previews.
But I'm wondering what Nicolas has already implemented, and what he or
others might still add.
Details:
John Kitchin (based on his experience with org-ref):
https://lists.gnu.org/archive/html/emacs-orgmode/2021-04/
On Fri, May 28, 2021 at 8:17 AM Bruce D'Arcus wrote:
> I think that example would imply overlays as well, though I don't
> really understand all the technical details or org-specific pros and
> cons (tooltips vs overlays and such) ...
I guess one could combine approaches; a compact display inlin
On Thu, May 27, 2021 at 12:13 PM Bruce D'Arcus wrote:
>
> On Thu, May 27, 2021 at 11:02 AM Bruce D'Arcus wrote:
>
> > One other thing I tested just now not yet accounted for: a locator
> > whose values is a list; for example, that renders as (Doe 2019, pp.
> > 23, 25).
> >
> > Is there an easy wa
Hello,
"Bruce D'Arcus" writes:
> Pandoc has an option to surround more complex locators, that might
> confuse the parser, in braces.
>
> More:
>
> https://pandoc.org/MANUAL.html#extension-citations
>
> Is that feasible here too?
I'd like to avoid this if possible. We'll see what we can do when
I may have missed something somewhere, but does anyone have a MWE for the
new citation syntax, including a minimal bibliography file, style files for
the various backends, & an org file with included citations? I am trying to
test out oc-csl.el but am pretty sure I am not dong it right.
I'm using this init file with emacs -Q:
https://gist.github.com/bdarcus/2645f99363fc47ddab2aae24c5d9e66c
Note, though, it's not ideal because adding citeproc was a PITA. If
you figure out how to adapt it so it installs and loads citeproc and
its dependencies, let me know, so I can update it?
...
Thanks Juan Manuel!
Your suggestion works for LaTeX, but I need the other formats too. I
tried to convert the LaTeX document with pandoc, tex4h and latex2html to
odt and html but none of them produces the correct output.
So I'm wondering whether there is any way to make org export to
recognize si
On punctuation moving in oc-csl, Nicolas, do we need to configure
something to turn it on?
This input:
quote, punctuation: “my quote” [cite/text/caps:@latexcompanion].
... for US English input, should yield this in the plain output for a
note style:
quote, punctuation: “my quote.”[3]
... but r
Steps to reproduce:
1) In an empty org-mode buffer, type a * SPC a C-b C-b C-b .
2) The buffer now has two lines, the first one "a" and the second "* a".
Expected:
3) The second line is formatted as a first-level heading.
Actual:
3) The second line is formatted as normal text.
Emacs : GNU Emac
|
|-+---+--++--+---|
| 20210528-053900 | 647_1 | 20210528-053900 1 -1333.58106425 | 7 |
01:00:00 | Job Wall-clock time: 00:03:16 |
| 20210528-053900 | 647_1 | 20210528-053900 2 -1333.25006295 | 7 |
01:00:00 | Job Wall-clock time: 00:03:16 |
| 20210528-053900 | 647_1 | 20210528-053900 3 -1332.40596663
Hello,
"Bruce D'Arcus" writes:
> On Wed, May 26, 2021 at 4:39 PM Nicolas Goaziou
> wrote:
>
>> The processor uses the "en-US" CSL locale file shipped with Org for rendering
>> localized dates and terms in the references, independently of the language
>> settings of the Org document. Additiona
On Fri, May 28, 2021 at 11:54 AM Nicolas Goaziou wrote:
> > Related, could we also have a `org-cite-csl-styles-dir' defcustom, to
> > avoid having to specify the full path?
>
> Good idea. Also implemented.
Thank you!
> > And/or alternately just `org-cite-csl-dir' for both locales and
> > styl
Nicolas Goaziou writes:
>> Also, is it possible for me to set things up so that export to latex
>> runs through the oc-biblatex processor, but otherwise it uses oc-csl,
>> where I have (obviously) different styles for each?
>
> It is not possible to set export processor per export back-end, but
Hi All,
A few days ago I pushed "org-plot: Use consistent method to find table"
https://code.orgmode.org/bzg/org-mode/commit/f72a658bd0 without
putting it through as a patch, as it's one of a few minor tweaks I've
made that I thought would be more noise than signal.
However, there's an implicatio
Hi Timothy,
> Timothy writes:
> Hi All, A few days ago I pushed "org-plot: Use consistent method
> to find table"
> https://code.orgmode.org/bzg/org-mode/commit/f72a658bd0 without
> putting it through as a patch, as it's one of a few minor tweaks
> I've made that I thoug
Colin Baxter writes:
> It doesn't work for me. I get "No data in plot" in the gnuplot buffer. I
> am probably doing something stupid.
That's odd, it "just works™" for me. Just to check: you are running Org
HEAD?
--
Timothy
Hi Andreas,
A quick fix (for LaTeX, odt and HTML), if you want to use second-level
quotes as first-level quotes in parts of your document, could be to
define a filter. You must put these quotes as ´ ... ´ (for example):
#+LANGUAGE: de
#+OPTIONS: ':t
#+BIND: org-export-filter-final-output-functio
> Timothy writes:
> Colin Baxter writes:
>> It doesn't work for me. I get "No data in plot" in the gnuplot
>> buffer. I am probably doing something stupid.
> That's odd, it "just works™" for me. Just to check: you are
> running Org HEAD?
It does work for me. I needed
Hello,
Timothy writes:
> Nicolas Goaziou writes:
>
>>> Also, is it possible for me to set things up so that export to latex
>>> runs through the oc-biblatex processor, but otherwise it uses oc-csl,
>>> where I have (obviously) different styles for each?
>>
>> It is not possible to set export pr
Hello,
"Andreas Gösele" writes:
> So I'm wondering whether there is any way to make org export to
> recognize single quotes also outside from double quote. It should be
> possible as inner quotes is not the only use of simple quotes.
As Juan Manual Macías wrote, I confirm single quotes are only
Hello,
"Bruce D'Arcus" writes:
> On punctuation moving in oc-csl, Nicolas, do we need to configure
> something to turn it on?
>
> This input:
>
> quote, punctuation: “my quote” [cite/text/caps:@latexcompanion].
>
> ... for US English input, should yield this in the plain output for a
> note styl
> On May 28, 2021, at 8:52 AM, Roger Mason wrote:
>
> Hello,
>
> I have an SQL source block that returns this:
>
> #+RESULTS: query
>
>
[snip]
> I would like to pass this into R for further processing. At the moment
> I have this:
>
> #+begin_src R :session :colnames yes :var data=quer
Nicolas Goaziou writes:
>> Forgive me if I'm jumping in without a good understanding of the
>> context, but does this mean that I can't easily have biblatex be used
>> when exporting to .tex and citeproc used when exporting to HTML?
>
> It depends on what you mean by "easily".
Well, what I'm h
Timothy writes:
> Nicolas Goaziou writes:
>> You can, for example, select the appropriate citation processor
>> according to `org-export-current-backend' in an export hook.
>
> I see, this sounds like not too much trouble, but I think ideally this
> would be OOTB behaviour.
I wouldn't hold my
"Bruce D'Arcus" writes:
> In an earlier discussion, people raised the issue of fontification and
> previews.
>
> But I'm wondering what Nicolas has already implemented, and what he or
> others might still add.
>
> Details:
>
> John Kitchin (based on his experience with org-ref):
>
> https://list
Nicolas Goaziou writes:
> I wouldn't hold my breath.
>
> First, IIUC, there's no reason to force biblatex over natbib OOTB as
> both are widely in use. But, more importantly, "oc-csl" require the
> external Citeproc library, so it cannot be loaded by default. As
> a consequence, no default conf
On Fri, May 28, 2021 at 1:43 PM Nicolas Goaziou wrote:
>
> "Bruce D'Arcus" writes:
>
> > In an earlier discussion, people raised the issue of fontification and
> > previews.
> >
> > But I'm wondering what Nicolas has already implemented, and what he or
> > others might still add.
> >
> > Details
Timothy,
> However, there's an implication to this change that I think deserves
> mentioning (and will be in this months TMIO). This now means that you
> can put a #+plot line before #+results and it will actually work!
very nice -- thanks!
Greg
Andreas Gösele writes:
> [...] I tried to convert the LaTeX document with pandoc, tex4h and
> latex2html to odt and html but none of them produces the correct
> output.
>
> So I'm wondering whether there is any way to make org export to
> recognize single quotes also outside from double quote.
On Fri, May 28, 2021 at 1:54 PM Timothy wrote:
>
>
> Nicolas Goaziou writes:
>
> > I wouldn't hold my breath.
> >
> > First, IIUC, there's no reason to force biblatex over natbib OOTB as
> > both are widely in use. But, more importantly, "oc-csl" require the
> > external Citeproc library, so it c
27;,'energy')
t
#+end_src
#+RESULTS:
|date | cycle | energy |
|-+---+|
| 20210528-053900 | 1 | -1333.58106425 |
| 20210528-053900 | 2 | -1333.25006295 |
| 20210528-053900 | 3 | -1332.40596663 |
| 20210528-053900 | 4 | -1327.188029
"Bruce D'Arcus" writes:
> On Fri, May 28, 2021 at 1:54 PM Timothy wrote:
>>
>>
>> Nicolas Goaziou writes:
>>
>> > I wouldn't hold my breath.
>> >
>> > First, IIUC, there's no reason to force biblatex over natbib OOTB as
>> > both are widely in use. But, more importantly, "oc-csl" require the
>>
"Andreas Gösele" writes:
> So I'm wondering whether there is any way to make org export to
> recognize single quotes also outside from double quote. It should be
> possible as inner quotes is not the only use of simple quotes.
Genuine question: what language uses two different styles of outer
(l
"Bruce D'Arcus" writes:
> Beyond requiring oc-basic (or any other "activate" processor), do I
> need to do anything more to "use" it?
You need to associate it to the "active" capability:
(setq org-cite-activate-processor 'basic)
(or with a file-local variable).
> So then it might be ideal t
Hi,
Axel Svensson writes:
Steps to reproduce:
1) In an empty org-mode buffer, type a * SPC a C-b C-b C-b .
2) The buffer now has two lines, the first one "a" and the second "* a".
Expected:
3) The second line is formatted as a first-level heading.
Actual:
3) The second line is formatted as nor
Hi Nicholas,
Nicolas Goaziou writes:
> Genuine question: what language uses two different styles of outer
> (level 1) quotes? And in what context?
I answer in the case of Spanish. In Spanish the level 1 quotes are «»
(french quotes). The level 2 are “...” (english quotes). Only in some
cases, an
Thanks Juan Manuel!
I tried it, but it doesn't work. It leaves the simple quotes
untouched. Did you test it and did it work then?
Best regards,
Andreas
Juan Manuel Macías writes:
> Hi Andreas,
>
> A quick fix (for LaTeX, odt and HTML), if you want to use second-level
> quotes as first-level q
Dear All,
I'm trying to catch up with the new developments, it isn't easy :-).
I think it would be really helpful to be able to map different
backends to different processors, because latex based solutions like
natbib can handle only latex-based backends, so anybody who wanted to
export both to l
Hi Andreas,
Andreas Gösele writes:
> I tried it, but it doesn't work. It leaves the simple quotes
> untouched. Did you test it and did it work then?
I forgot to tell you (sorry!) that you should set the variable
`org-export-allow-bind-keywords' as non-nil:
(setq org-export-allow-bind-keywords t
On Fri, May 28, 2021 at 3:59 PM Nicolas Goaziou
wrote:
>
> "Bruce D'Arcus" writes:
>
> > Beyond requiring oc-basic (or any other "activate" processor), do I
> > need to do anything more to "use" it?
>
> You need to associate it to the "active" capability:
>
> (setq org-cite-activate-processor '
Nicolas Goaziou writes:
> "Andreas Gösele" writes:
>
>> So I'm wondering whether there is any way to make org export to
>> recognize single quotes also outside from double quote. It should be
>> possible as inner quotes is not the only use of simple quotes.
>
> Genuine question: what language us
On Fri, May 28, 2021 at 9:52 AM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > Pandoc has an option to surround more complex locators, that might
> > confuse the parser, in braces.
> >
> > More:
> >
> > https://pandoc.org/MANUAL.html#extension-citations
> >
> > Is that feasib
Albert Krewinkel writes:
> Andreas Gösele writes:
>
>> [...] I tried to convert the LaTeX document with pandoc, tex4h and
>> latex2html to odt and html but none of them produces the correct
>> output.
>>
>> So I'm wondering whether there is any way to make org export to
>> recognize single quote
* ox-latex.el (org-latex-src-block): moved (("language" ,lst-lang)) to the head
of the list.
This fixes wiping out preceding definitions given in
`org-latex-listings-options'.
TINYCHANGE
---
lisp/ox-latex.el | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lisp/ox-latex.el
Juan Manuel Macías writes:
> Andreas Gösele writes:
>
>> I tried it, but it doesn't work. It leaves the simple quotes
>> untouched. Did you test it and did it work then?
>
> I forgot to tell you (sorry!) that you should set the variable
> `org-export-allow-bind-keywords' as non-nil:
>
> (setq org
Bastien writes:
> Taylor Sutton writes:
>
>> I can fix it.
>
> It looks like your understanding of the problems is enough to propose
> a patch -- would you like to propose one?
(I'm going through old bug reports.)
This was six years ago, and I had a glance at org-mobile.el, and it
seems like t
Ypo writes:
> ... I would like habits to go in the time of the day
> when they are programmed to be done. Is it possible?
Could you elaborate? Are you talking about position of the habit graph?
Best,
Ihor
Richard Stanton writes:
> I currently load org using straight.el as follows:
> ...
> (use-package org-contrib
> :after org
> ...
> (use-package org
> :after (jupyter)
I suspect that something else is pulling built-in org version before
jupyter gets loaded. To make sure that the straight versi
Tom Gillespie writes:
> Hi all,
> Here is the 4th (or so) iteration of the grammar for titles that
> I think deals with most of the issues in this thread along with a
> bunch of nasty test cases. The previous attempts can be inspected in
> the git history, but long story short, it is extreme
Hi David,
Laundry produces a full s-expression representation of the org
parse tree (though it is still evolving). I haven't added a pass that
converts it to some Racket internal representation (probably will be
structs). If you get it installed and put #lang org at the top of an
org file you c
51 matches
Mail list logo
