Dear All,
my 2c on this issue: citeproc-el supports per cite author suppression
under the hood, but citeproc-org always maps "suppress author" mode
citations to suppressing only the first cite, because my impression
was also that this is a citation-level option. This is how the
proposal on the
Dear Bastien,
Thank you for your well-thought-out reply.
With regards to the question your email ends with:
> What do you think? Would you be willing to take this role?
> If not, that's perfectly okay, I'll send a call for help.
The short answer is "yes, mostly". The long answer follows :P
Bastien,
> You might want to write another one for the public-inbox archive:
>
> E.g. https://orgmode.org/list/?q=Juan+Manuel+Mac%C3%ADas
okay, i'll bite: what *is* the difference between
https://orgmode.org/list and
https://lists.gnu.org/archive/html/emacs-orgmode/ ?
cheers, Greg
Hi Juan,
Juan Manuel Macías writes:
> I have written some elvis for my
> personal use, among them this simple script to search this mailing list,
> which I share here in case someone finds it useful:
Neat!
You might want to write another one for the public-inbox archive:
E.g.
Hi Bithov,
we *do* care a lot about backward compatibility*.
We cannot make a strong commitment for contributed libraries and
external ones, though, otherwise Org would not evolve.
org-drill.el was removed from the contrib/ directory 1 year ago:
Dear Timothy,
thanks for raising this points so carefully, they are important.
I see three distinct problems:
1. The lack of response and/or follow-up when people contribute by
sending bug reports or patches on the list.
2. The lack of maintainance on documenting the contribution process
I'm afraid it looks like I either made a typo while doing this, or
something odd happened. Regardless it didn't work correctly.
Take 2, sorry for the noise --- but at least the patch section on
updates.orgmode.org should be more useful now as it only shows pending
patches again.
Timothy
Marking as closed on updates.orgmode.org via the X-Woof-Patch header.
Leo Okawa Ericson writes:
> I can't think of a reason either (now that I know that jit-lock exists)
> so I will retract my patch.
Marking as closed on updates.orgmode.org via the X-Woof-Patch header.
Leo Okawa Ericson writes:
> I can't think of a reason either (now that I know that jit-lock exists)
> so I will retract my patch.
Marking as closed on updates.orgmode.org via the X-Woof-Patch header.
Leo Okawa Ericson writes:
> I can't think of a reason either (now that I know that jit-lock exists)
> so I will retract my patch.
As you have said you'll start a new thread for your revised proposal,
I'll mark this as closed on updates.orgmode.org via the X-Woof-Patch
header.
Juan Manuel Macías writes:
> Ok, I agree. Next week I will start a new thread for submit this new
> proposal.
>
> Best regards,
>
> Juan Manuel
This was not marked as applied on updates.orgmode.org.
Doing so with the X-Woof-Patch header.
ian martins writes:
> Thanks. And thanks for taking the time to fix issues that you find. It
> continues to improve because of your contributions.
> The patch looks good. Applied.
This was not marked as applied on updates.orgmode.org.
Doing so with the X-Woof-Patch header.
ian martins writes:
> It's no problem. Didn't mean to rush you. Thanks again for the patch. Applied.
This was not marked as applied on updates.orgmode.org.
Doing so with the X-Woof-Patch header.
miles christopher writes:
> Applied, I think this should be the final version.
This was not marked as applied on updates.orgmode.org.
Doing so with the X-Woof-Patch header.
Kyle Meyer writes:
> Pushed (00b4de329).
For some reason updates.orgmode.org registered this as a new patch??
Marking as closed via X-Woof-Patch header.
Greg Minshall writes:
> Timothy,
>
>> This is a quick patch to use the Emacs manual CSS with our generated Org
>> manual.
>
> that's certainly visually pleasing. nice!
>
> Greg
This was not marked as applied on updates.orgmode.org.
Doing so with the X-Woof-Patch header.
Bastien writes:
> I made this change and tested it online, the HTML Org manual now looks
> like the Emacs manual: https://orgmode.org/manual/
>
> Thanks for the suggestion!
> In any cas, the Emacs
This was not marked as applied on updates.orgmode.org.
Doing so with the X-Woof-Patch header.
Bastien writes:
> Of course, done (c822c80ef).
>
> Sorry I forgot about this patch, and thanks for your reply.
This was not marked as applied on updates.orgmode.org.
Doing so with the X-Woof-Patch header.
Jack Kamm writes:
> Thanks, I've fixed the remaining issues you pointed out and pushed this
> in 5371b30fe.
>
> Cheers,
> Jack
This was not marked as applied. Doing so with the X-Woof-Patch header.
Kyle Meyer writes:
> Christopher Miles writes:
>
>> Subject: [PATCH] org.el: Complete tags from both global and buffer local
>
> Thanks. Applied (86ad8d279)...
Marking this patch as cancelled for updates.orgmode.org.
On Sat, Apr 24, 2021 at 4:09 PM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > I also came across this post from 2018 from Andras ...
> >
> > https://orgmode.org/list/87in8jaywk@all.hu/
> >
> > ... which includes a link to his proposal on what we now call styles,
> > but
Hi all,
(Resending after messing up the first time.)
The included patch adds a new property :refile-to to org capture
templates, allowing each template to have its own set of refile targets.
I find this really useful in practice and thought others might too.
Richard
>From
Sorry, messed up the patch attachment, will resend in a new thread.
Richard
Richard Garner writes:
> Hi all,
>
> The included patch adds a new property :refile-to to org capture
> templates, allowing each template to have its own set of refile targets.
> I find this really useful in
Hi all,
The included patch adds a new property :refile-to to org capture
templates, allowing each template to have its own set of refile targets.
I find this really useful in practice and thought others might too.
Richard
---
>From 829c1ba4805327645fcb75b35b73ecb3a1700b2f Mon Sep 17 00:00:00
Hello,
"Bruce D'Arcus" writes:
> I also came across this post from 2018 from Andras ...
>
> https://orgmode.org/list/87in8jaywk@all.hu/
>
> ... which includes a link to his proposal on what we now call styles,
> but there he calls (a la the TeX world) commands:
>
>
I also came across this post from 2018 from Andras ...
https://orgmode.org/list/87in8jaywk@all.hu/
... which includes a link to his proposal on what we now call styles,
but there he calls (a la the TeX world) commands:
On Sat, Apr 24, 2021 at 1:47 PM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > Some sentence with a concluding citation [cite:@key].
> >
> > ... that should end up like this:
> >
> > Some sentence with a concluding citation.[1]
> >
> > Aside: looking through the CSL spec, it
Hello,
"Bruce D'Arcus" writes:
> Some sentence with a concluding citation [cite:@key].
>
> ... that should end up like this:
>
> Some sentence with a concluding citation.[1]
>
> Aside: looking through the CSL spec, it doesn't seem this is
> documented. It obviously should be.
>
> And I don't
Am 23. April 2021 um 09:24 Uhr -0400 schrieb Bruce D'Arcus:
> It can be that not only does the space get removed, but the note mark
> is moved outside the period.
>
> So if you have ...
>
> Some sentence with a concluding citation [cite:@key].
>
> ... that should end up like this:
>
> Some
On Sat, Apr 24, 2021, 1:08 PM Nicolas Goaziou
wrote:
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > This distinction is wrong, and we should treat "suppress-author" as a
> > citation style instead.
> >
> > The result would be:
> >
> > [cite/supress-author:doe19;doe20]
> >
> > Or even can keep the
Hello,
"Bruce D'Arcus" writes:
> This distinction is wrong, and we should treat "suppress-author" as a
> citation style instead.
>
> The result would be:
>
> [cite/supress-author:doe19;doe20]
>
> Or even can keep the shorthand:
>
> [cite/-:doe19;doe20]
>
> In fact, with the change, could even
On 21/04/2021 22:45, Juan Manuel Macías wrote:
I have tried the Nicolas' patch (latest version) and I see that the
items with emphasis are already ordered well. However, it seems that the
problem with identical items with or without emphasis still persists:
which items should go before and in
Hello,
András Simonyi writes:
> Thank you, this is very promising! I've checked the behaviour of
> citeproc-org with and without a note style now and there is only one
> additional minor difference which I forgot to mention, I don't know
> how difficult would it be to implement it: When a
Correction, though it doesn't change the conclusion.
On Sat, Apr 24, 2021 at 6:52 AM Bruce D'Arcus wrote:
> So to get "Doe (2019) argues" you would need to write "Doe [@doe19]"
> in pandoc, for example.
Incorrect: the pandoc syntax for citet-like rendering is:
@doe19
So to drop the brackets.
On Sat, Apr 24, 2021 at 3:53 AM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > Nicolas,
> >
> > Quick syntax question:
> >
> > On Wed, Apr 21, 2021 at 7:34 PM Nicolas Goaziou
> > wrote:
> >
> >> As a reminder, the full citation syntax is
> >>
> >> [cite/style:common
Hi Nicolas,
As I was working on adding a function to generate the new cite syntax,
an idea occurred to me that I'd like to raise, that would simplify
this model and syntax.
I ran the idea by the pandoc list just to confirm my thinking was
reasonable, since that has a lot of experience using
Yes, the issue is due to using an older version of Org.
I searched the change log and saw that the compact form is introduced in
Org 9.4, while mine is 9.3.
Thanks for your help!
Sincerely,
Johnson
On 4/20/2021 9:42 PM, NicolasGoaziou wrote:
Hello,
Johnson writes:
I'm contributing to
Hello,
M. ‘quintus’ Gülker writes:
> I sometimes use emphasis around citations, but since my citation
> styles all use footnotes, I think there should be no problem with
> this. For example, I would write something like this (I hope I got the
> syntax right):
>
> This is a test
Hello,
"Bruce D'Arcus" writes:
> Nicolas,
>
> Quick syntax question:
>
> On Wed, Apr 21, 2021 at 7:34 PM Nicolas Goaziou
> wrote:
>
>> As a reminder, the full citation syntax is
>>
>> [cite/style:common prefix ;prefix -@key suffix; ... ; common suffix]
>
> Is the space you have here before
> Uwe Brauer writes:
Hi
> With this backtrace alone (which involves org-capture catching the
> internal error), I think it's going to be hard for anyone to guess
> what's going on here. It sounds like once you encounter this error,
> subsequent calls reliably trigger it. Next time you run
41 matches
Mail list logo
