I don't know if this is crazy. But I was wondering if it is possible
(or worth exploring as an idea) to turn #+print_bibliography into
something that can be evaluated to throw the bibliography as results
in the org file itself.
This would then allow playing with the bibliography using org, and
If you do emacs -Q, can you reproduce the issue? If not, then it is
likely something in your init which is causing this.
Also, what type of export are you attempting (i.e. PDF, ASCII, HTML etc)
Devin Prater writes:
> Okay, so I’ve got a strange problem. Whenever I have blocks, like
>
>
This is very helpful already. Keenly looking forward to how this develops.
Vikas
On Sat, Jul 17, 2021 at 04:52:33PM -0400, John Kitchin wrote:
> I made a video of my current org-cite setup at
> https://www.youtube.com/watch?v=
> 4ta4J20kpmM. You can also find a link to the code to run it in the
Tom Gillespie writes:
> Pinging on this to see if anyone can test it so that it can be merged.
> Tom
I agree with this patch.
Just to make clear the default behavior and the behavior that would
exist with this patch.
The current behavior
1. You have a code block C1 in a buffer B1.
2. You
I made a video of my current org-cite setup at
https://www.youtube.com/watch?v=4ta4J20kpmM. You can also find a link to
the code to run it in the description there.
I don't intend this to be a final video (it is still a little rough!), it
is just to help people see what I am thinking about for
Tom Gillespie writes:
> Pinging on this to see if anyone can test it so that it can be merged.
> Tom
>
> On Wed, Jun 16, 2021 at 4:29 PM Tom Gillespie wrote:
>>
>> Hi,
>>This is a patch that fixes tangling behavior when a block has been
>> ingested into the library of babel and then
Pinging on this to see if anyone can test it so that it can be merged.
Tom
On Wed, Jun 16, 2021 at 4:29 PM Tom Gillespie wrote:
>
> Hi,
>This is a patch that fixes tangling behavior when a block has been
> ingested into the library of babel and then modified. Best!
> Tom
Thanks. This is very useful.
Vikas
On Sat, Jul 17, 2021 at 03:55:18PM +0200, András Simonyi wrote:
> Dear Vikas,
>
> the CSL-based processor is in a bit of a flux in this respect, but as
> for the natbib and biblatex processors I've extracted these
> correspondences from the oc source code,
On Sat, Jul 17, 2021 at 10:20 AM Vikas Rawal wrote:
> Thanks, Bruce and John. Indeed, I used biblatex with natbib=true
> option, which gives me citet and citep in biblatex. But using
> \autocite and \textcite is perfect.
>
> I am noticing a few other issues at this stage.
>
> I have a large
Hi Maxim,
I think the problem is not the fact that I may be inclined towards book
typesetting but that TeX itself and its workflow is inclined towards
book typesetting. This fact is something that must be taken into account
and that many LaTeX users sometimes forget. The concept of a 'fallback
Thanks, Bruce and John. Indeed, I used biblatex with natbib=true
option, which gives me citet and citep in biblatex. But using
\autocite and \textcite is perfect.
I am noticing a few other issues at this stage.
I have a large biblatex database, and loading it using C-c C-x @ to
insert citations
Dear Vikas,
the CSL-based processor is in a bit of a flux in this respect, but as
for the natbib and biblatex processors I've extracted these
correspondences from the oc source code, which you might find useful.
(With the exception of the first, "fully nil" styles, one always has
to use the "/"
Alan Ristow writes:
> Finally, as a newbie here myself, I have a naïve question of my own:
> Provided the patch proves successful, how/when is it applied to the
> official org repo? Is it up to Ihor (or somebody else) to make a pull
> request, for example?
An email with [PATCH] in header is
Bhavin Gandhi writes:
> I was trying to understand your change. So, when we call
> `org-agenda-todo', it calls `org-todo' which adds the
> post-command-hook. This hook is supposed to run when `org-agenda-todo'
> finishes, but instead of that we call it directly. This makes sure that
> the change
"Bruce D'Arcus" writes:
> Could someone with some expertise in this area recommend how I do the
> following?
>
> Load org-cite and it's associated packages (oc-basic, oc-natbib,
> etc.), and set some associated variables, if org-cite is available.
It should be default behaviour:
(use-package
We were posting at the same time :-)
On Sat, Jul 17, 2021 at 8:39 AM John Kitchin wrote:
> There is not currently a way to get \citet and \citep with the biblatex
> backend.
Yes, but \autocite andt \textcite produce the expected output, and
have the advantage they are independent of output
On Sat, Jul 17, 2021 at 7:41 AM Vikas Rawal wrote:
> What is the equivalent here of the various citation commands that something
> like biblatex or bibtex provide? The two most common citation commands I use
> are citet and citep (or parencite). These are used to produce the following
> kind
It sounds like you use natbib/bibtex (citet/citep are natbib commands I
think). In that case, my current understanding is that these are the
syntaxes for what you want, with the natbib exporter selected.
[cite:@key] -> \citep{key}
[cite/t:@key] -> \citet{key}
But, if you use the biblatex
On 17/07/2021 01:34, Juan Manuel Macías wrote:
Maxim Nikulin writes:
I think that low level implementation in browser or in some underlying
library is much faster
LM Roman 12
abc абв…с
LM Roman 12, CMU Serif
abc абв…с
They are two different scenarios:
I have been a long time user of org-ref and am excited to see the
development of org-cite. Thanks a lot for this, Nicholas and others
who have been working on this. I have been wanting to give it a spin
for the last few days and finally got down to doing it.
I am aware that the documentation is
out of curiosity, what did you expect would happen? To me, this seems like
correct/expected
behaviour as there is no way to resolve that link. (I'm wondering if there is
something wrong
or missing in the manual which has given a different expectation?)
Regards,
--
*Tim Cross*
/For gor sake
Kun Liu writes:
> I see error
> user-error: Unable to resolve link: "*B"
This is expected default behaviour. You can customise it using
org-export-with-broken-links.
Best,
Ihor
22 matches
Mail list logo
