On Thu, May 20, 2021 at 6:37 PM Thomas S. Dye wrote:
>
> Interested lurker here. From the biblatex-chicago manual:
>
> "You can load the package via the usual \usepackage{biblatex},
> adding either style=chicago-notes or style=chicago-authordate"
Alas, I get errors when I use that invocation.
Maxim,
> The patch removed this phrase.
sorry about that.
> I have no idea how to express it in a better way. The tables are same
> for Org >= 9.5 and for Org < 9.5 (modulo bugs in indentation fixed in
> 9.4.6). Only default configuration evolves in time.
again, i apologize. my confusion was
Interested lurker here. From the biblatex-chicago manual:
"You can load the package via the usual \usepackage{biblatex},
adding either style=chicago-notes or style=chicago-authordate"
All the best,
Tom
Denis Maier writes:
Hi,
Am 20.05.2021 um 19:06 schrieb Nicolas Goaziou:
Hello,
Hi,
Am 20.05.2021 um 19:06 schrieb Nicolas Goaziou:
Hello,
"Bruce D'Arcus" writes:
On Thu, May 20, 2021 at 9:57 AM Denis Maier wrote:
I'm not really sure we need bare substyles at all. At least in biblatex
it's the basis for the other commands.
Though see my followup message on
Am 20.05.2021 um 19:15 schrieb Nicolas Goaziou:
Hello,
Denis Maier writes:
By the way, I have the impression we can easily get rid of the
bare-variants completely. If we don't need footcitetext (or if we rename
the variant to note/text as that would be more appropriate, we can
something like
* Samuel Wales [2021-05-21 01:19]:
> thanks for pointing us to this variable.
>
> docstring says "This process ensures that these values are unique and
> valid...", so it sounds like you could create non-unique or invalid
> identifiers without it.
>
> does this mean, for example, if the user
* Nicolas Goaziou [2021-05-20 23:00]:
> > Is there a possibility to tell Org, that <> really remains
> > "target" as in id="target" instead of a random ID?
>
> See `org-html-prefer-user-labels'.
Thanks.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
thanks for pointing us to this variable.
docstring says "This process ensures that these values are unique and
valid...", so it sounds like you could create non-unique or invalid
identifiers without it.
does this mean, for example, if the user exports a subtree with two
link targets with the
thanks for the example. yes, that is the example i was thinkng of.
i was asking, why does adding uniqueness do any good currently. if
the user has your example as follows, it does create duplicates in the
output, but i don't get why that all by itself needs fixing by
default.
===vvv
I may try
Bummer!
This non-minimal example (modified from a document that originally
called biblatex-chicago directly) works for me:
\usepackage[style=chicago-authordate, giveninits=true,
uniquename=mininit, noibid, sortcites=true, backend=biber,
bibencoding=utf8]{biblatex}
All the best,
Tom
Hi Nicolas,
Please help review and merge this patch. Thanks
Best Regards
Sun.Lin
From e963bd5554b076c813cde1f59d75f0686fec8a14 Mon Sep 17 00:00:00 2001
From: Sun Lin
Date: Thu, 13 May 2021 09:52:33 +
Subject: [PATCH] org-agenda-files: work with relateive file paths.
* lisp/org.el
Am 19.05.2021 um 17:23 schrieb Nicolas Goaziou:
Denis Maier writes:
In that case, I'd think that note/bare => footcitecite isn't
a particular good fit. Footcitetext puts the citation in a footnote,
just that it doesn't print a footnote mark in a running text.
(This is useful in cases where the
"Bruce D'Arcus" writes:
> On Tue, May 18, 2021, 11:45 AM Nicolas Goaziou wrote:
>
> I don't use biblatex either; hopefully some folks that do can test
> this.
I could test this. I write multiple posts in APA style every week, all
with citations, and I cannot wait to use Org instead of LaTeX
Hi
In the following table:
It is possible to insert a footnote in a regular way, right now I cannot.
What shell I do? What is the recipe to insert footnotes in all cells.
Thanks
Uwe Brauer
| this | that | | | | F | | |
|--+--+-+---+-+---+---+---|
|
>>> "UB" == Uwe Brauer writes:
> Hi
> In the following table:
The subject is wrong, I am still googling but don't understand why I
cannot insert footnotes in all cells in a table.
smime.p7s
Description: S/MIME cryptographic signature
>>> "UB" == Uwe Brauer writes:
>>> "UB" == Uwe Brauer writes:
>> Hi
>> In the following table:
> The subject is wrong, I am still googling but don't understand why I
> cannot insert footnotes in all cells in a table.
It seems that the function org-footnote--allow-reference-p
is the
Hi Uwe,
Uwe Brauer writes:
> It seems that the function org-footnote--allow-reference-p
> is the culprit, but which places are *forbidden* the doc string does not
> say much.
If you mean to insert a note in an empty cell, you can insert just
before the note mark a zero width space (M-x
>>> "JMM" == Juan Manuel Macías writes:
> Hi Uwe,
> Uwe Brauer writes:
>> It seems that the function org-footnote--allow-reference-p
>> is the culprit, but which places are *forbidden* the doc string does not
>> say much.
> If you mean to insert a note in an empty cell, you can insert just
>
On Thu, May 20, 2021 at 4:18 AM Denis Maier wrote:
> Could be, but also [cite/text/bare] or cite/foot/bare or cite/super/bare
> as they all are essentially just wrappers around the plain cite command
> (textcite is a bit different, but parencite and footcite really have the
> same definition as
On Thu, May 20, 2021 at 3:22 AM Rudolf Adamkovič wrote:
> I could test this. I write multiple posts in APA style every week, all
> with citations, and I cannot wait to use Org instead of LaTeX for all my
> work. Is it possible to test this with use-package somehow? Note, I am
> still fairly new
Uwe Brauer writes:
> Ah! That was it, thanks!
> I think the documentation of org-footnote-action
> could be a bit more explicit and cover this case.
In the manual the use of the zero width space character is in the section
'Escape Character'. Perhaps it would be nice to add more usage examples.
Hi,
If there is a philologist among the colisters who is working on critical
editions (a type of text with several complex apparatus of footnotes and
endnotes, and with numbering and various material at the margin ---an
example of critical edition I recently typesetted for a German publisher:
On Thu, May 20, 2021 at 7:56 AM Bruce D'Arcus wrote:
> I take that summary to mean this basic question can be handled by a
> combination of autocite and export config; autocite=inline (or
> autocite=footnote) as default export, but of course configurable?
An example of using the autocite
With the following org file on master:
#+name: gen
#+begin_src emacs-lisp
(cons 1 2)
#+end_src
#+header: :var inp=gen()
#+begin_src emacs-lisp
inp
#+end_src
C-c C-c on the second code block yields:
executing Emacs-Lisp code block (gen)...
(1 . 2)
org-babel-disassemble-tables: Wrong type
Bastien writes:
> Org 9.4.6, a bugfix release, is out, avaiable in Org ELPA
> and as a standalone archive.
>
> Hopefully this will be the last one before we release 9.5.
Thanks!
Adding release header ;)
Best,
Ihor
So backing up a bit, as I was getting confused, here's [1] one summary
of the different core biblatex commands.
- \cite [autocite=plain]: Citations are typeset as-is;
- \parencite [autocite=inline]: Citations are typeset in parentheses;
- \footcite [autocite=footnote]: Citations are typeset as
Ihor Radchenko writes:
> Adding release header ;)
Oh, thanks - sorry I forgot this!
--
Bastien
Hi Maxim,
applied as 507cf71de in master, thanks!
For your next patch to be perfect, please include a commit message:
https://orgmode.org/worg/org-contribute.html#commit-messages
--
Bastien
Am 20.05.2021 um 13:45 schrieb Juan Manuel Macías:
Hi,
If there is a philologist among the colisters who is working on critical
editions (a type of text with several complex apparatus of footnotes and
endnotes, and with numbering and various material at the margin ---an
example of critical
Hi Maxim,
applied in Worg, thanks!
--
Bastien
Am 20.05.2021 um 12:36 schrieb Bruce D'Arcus:
> On Thu, May 20, 2021 at 4:18 AM Denis Maier
wrote:
>
>> Could be, but also [cite/text/bare] or cite/foot/bare or cite/super/bare
>> as they all are essentially just wrappers around the plain cite command
>> (textcite is a bit different, but
Am 20.05.2021 um 13:56 schrieb Bruce D'Arcus:
So backing up a bit, as I was getting confused, here's [1] one summary
of the different core biblatex commands.
- \cite [autocite=plain]: Citations are typeset as-is;
- \parencite [autocite=inline]: Citations are typeset in parentheses;
- \footcite
Nick,
> I've merged the develop branch into the master branch this morning,
> too. So you should be able to reap that benefit on either branch, but
> I still recommend using the lockfiles to your advantage.
thanks again.
since "we" have you on the line, i wonder if i might impose on you and
Am 20.05.2021 um 15:22 schrieb Bruce D'Arcus:
On Thu, May 20, 2021 at 9:07 AM Denis Maier wrote:
Am 20.05.2021 um 12:36 schrieb Bruce D'Arcus:
On Thu, May 20, 2021 at 4:18 AM Denis Maier wrote:
But maybe cite/plain or cite/basic or so?
First, are those two suggestions just synonyms for
Thank you for your comments, Greg.
On 20/05/2021 01:06, Greg Minshall wrote:
>
> patches to patches... :) i think these are really just typos, rather
> than any useful substantial comment.
>
> - s/is enable (the default) or not:/is enabled (the default) or not:/
The patch removed this phrase.
Hello,
Axel Kielhorn writes:
> In columnview mode the estimate is calculated[1] but the dynamic block
> doesn’t get updated.
>
> I did some bisecting and the last version where both column view and dynamic
> block were working is:
>
> Merge branch 'maint' 1aeb958e5 Marco Wahl
>
Axel Kielhorn writes:
>> Am 20.05.2021 um 19:58 schrieb Nicolas Goaziou :
>>
>> Org Duration is strict about what it is fed with (which is good). Effort
>> property expects a duration as value. But "3-8" is not a valid duration.
>> However, "3" is a valid duration; it means 3 minutes.
>
> The
The main patch that fixes org-remove-invisible to improve list sorting is
landed.
Let me remind that there were patches that added more test cases:
https://orgmode.org/list/s5p88r$go9$1...@ciao.gmane.io
Is there any interest in them?
In the following subthread Nicolas mentioned that some of
> Am 20.05.2021 um 19:58 schrieb Nicolas Goaziou :
>
> Org Duration is strict about what it is fed with (which is good). Effort
> property expects a duration as value. But "3-8" is not a valid duration.
> However, "3" is a valid duration; it means 3 minutes.
The problem is that effort can
Is it possible to create a custom <>:
From: (info "(org) Internal Links")
1. one item
2. <>another item
Here we refer to item [[target]].
That is fine, however, in the HTML output the <> will become
something like: another item
As I am developing finely grained referenced Org
Hello,
"Bruce D'Arcus" writes:
> On Thu, May 20, 2021 at 9:57 AM Denis Maier wrote:
>
>> >> I'm not really sure we need bare substyles at all. At least in biblatex
>> >> it's the basis for the other commands.
>> >
>> > Though see my followup message on autocite config.
>> >
>> > Does that
In columnview mode the estimate is calculated[1] but the dynamic block doesn’t
get updated.
I did some bisecting and the last version where both column view and dynamic
block were working is:
Merge branch 'maint'1aeb958e5 Marco Wahl
12.02.2017, 09:19
In
Use Org duration
Hello,
Denis Maier writes:
> By the way, I have the impression we can easily get rid of the
> bare-variants completely. If we don't need footcitetext (or if we rename
> the variant to note/text as that would be more appropriate, we can
> something like this:
>
>
> | Style | Variant
Hello,
Jean Louis writes:
> Is it possible to create a custom <>:
>
> From: (info "(org) Internal Links")
>
> 1. one item
> 2. <>another item
> Here we refer to item [[target]].
>
> That is fine, however, in the HTML output the <> will become
> something like: another item
>
> As
Hello,
Maxim Nikulin writes:
> The main patch that fixes org-remove-invisible to improve list sorting is
> landed.
>
> Let me remind that there were patches that added more test cases:
> https://orgmode.org/list/s5p88r$go9$1...@ciao.gmane.io
> Is there any interest in them?
>
> In the
Am 20.05.2021 um 16:11 schrieb Bruce D'Arcus:
On Thu, May 20, 2021 at 9:57 AM Denis Maier wrote:
I'm not really sure we need bare substyles at all. At least in biblatex
it's the basis for the other commands.
Though see my followup message on autocite config.
Does that change this
Am 19.05.2021 um 17:23 schrieb Nicolas Goaziou:
\cite could be [cite/bare: ...]
This would be confusing. So far, "bare" is a style variant. Your
suggestion promotes it exceptionally to a full-fledged style. It hurts
my logic. :)
Could "\cite" be [cite/parens/bare:...] instead?
Another
On Thu, May 20, 2021 at 10:29 AM Denis Maier wrote:
>
> Am 20.05.2021 um 16:11 schrieb Bruce D'Arcus:
...
> > 1. I wasn't sure Nicolas was aware of this config option, nor how one
> > would configure it currently (but it seems necessary in general)
>
> No, it's only necessary to configure this if
Hello,
Uwe Brauer writes:
>> The subject is wrong, I am still googling but don't understand why I
>> cannot insert footnotes in all cells in a table.
There was a bug with _empty_ cells.
> It seems that the function org-footnote--allow-reference-p
> is the culprit
Fixed. Thank you.
> but
On Thu, May 20, 2021 at 9:07 AM Denis Maier wrote:
>
> Am 20.05.2021 um 12:36 schrieb Bruce D'Arcus:
> > On Thu, May 20, 2021 at 4:18 AM Denis Maier wrote:
> >> But maybe cite/plain or cite/basic or so?
> >
> > First, are those two suggestions just synonyms for cite/bare?
>
> Yes. Nicolas
On Thu, May 20, 2021 at 9:57 AM Denis Maier wrote:
> >> I'm not really sure we need bare substyles at all. At least in biblatex
> >> it's the basis for the other commands.
> >
> > Though see my followup message on autocite config.
> >
> > Does that change this discussion?
>
> Why?
I put it in
Am 20.05.2021 um 12:36 schrieb Bruce D'Arcus:
On Thu, May 20, 2021 at 4:18 AM Denis Maier wrote:
Could be, but also [cite/text/bare] or cite/foot/bare or cite/super/bare
as they all are essentially just wrappers around the plain cite command
(textcite is a bit different, but parencite and
52 matches
Mail list logo
