Re: citations: org-cite vs org-ref 3.0

On Sun, Mar 20, 2022 at 9:57 PM Timothy wrote: > Hi John, > > Thanks for your considered response. > > When you contrast org-cite and org-ref, you say: > > > With org-ref, bib(la)tex export is almost fully supported, and is easy, > > I find this odd as org-cite supports bib(la)tex export, and

Re: citations: org-cite vs org-ref 3.0

Bruce and I looked into this UI approach in https://github.com/jkitchin/org-ref-cite/issues/9. Bruce and I discussed and worked on this for almost two weeks. There are 70 comments in this issue. There are opportunities now to annotate completion targets, which you can see in the link above. The

Re: citations: org-cite vs org-ref 3.0

chris writes: > On Sunday, 20 March 2022 20:44:50 CET Bruce D'Arcus wrote: >> On Sun, Mar 20, 2022 at 9:42 AM Ihor Radchenko wrote: >> > For citar, why not simply using ivy-bibtex? It supports org-cite, AFAIK. >> >> Not really; or rather minimally. > > I use `org-cite` with a very minimal

=org-cite= links do not work in the =#+title=

━━━ NOTES ON ━━━ When using a citation in the title, it does not seem to work when exporting to LaTeX. For example (in the .org file): Exports to (in the .tex file): \title{Notes on }

Re: =org-cite= links do not work in the =#+title=

There are restrictions on where citations are allowed, and this is one of them. Citar, and I think the oc-basic, insert processors won't allow you to insert citations in those places. Usually there are technical reasons for the restrictions (IIRC having to do with fontification?), but sometimes

Re: citations: org-cite vs org-ref 3.0

On Mon, Mar 21, 2022 at 10:41 AM Max Nikulin wrote: ... > A bit of routine work will alleviate some user issues: > - add missed styles The initial list of style-command mappings was pretty comprehensive, but we left out some of the more obscure biblatex commands because unsure if they were

Re: citations: org-cite vs org-ref 3.0

On Mon, Mar 21, 2022 at 8:41 AM Dominik Schrempf wrote: > > Thank you, I can use `citar-insert-edit` to perform this action. You can actually just use org-cite-insert, which is context aware. > Now, I failed to create a full citation in the text. This corresponds to the > `\fullcite{}' command

Re: citations: org-cite vs org-ref 3.0

“Bruce D’Arcus” writes: > On Mon, Mar 21, 2022 at 8:41 AM Dominik Schrempf > wrote: >> >> Thank you, I can use `citar-insert-edit` to perform this action. > > You can actually just use org-cite-insert, which is context aware. > >> Now, I failed to create a full citation in the text. This

Re: citations: org-cite vs org-ref 3.0

Vikas Rawal writes: > Dear John, > > Thanks very much for taking time to write a detailed reply. > > I do not think it is productive for the community to say or consider it > is a sad situation. > > From the perspective of a user, this was only meant to express a > sentiment that one finds

Re: citations: org-cite vs org-ref 3.0

Thank you, I can use `citar-insert-edit` to perform this action. Now, I failed to create a full citation in the text. This corresponds to the `\fullcite{}' command in LaTeX. Is there an option for this? In summary, it is a bit painful to use `org-cite` compared to using `org-ref`. In my opinion,

Re: citations: org-cite vs org-ref 3.0

On Mon, Mar 21, 2022 at 8:23 AM John Kitchin wrote: >> A package could be created, say `org-cite-literal-biblatex' which is just a >> copy >> of `oc-biblatex.el' with a different default `org-cite-biblatex-styles' and >> `org-cite-biblatex-style-shortcuts' (or just sets those variables in >>

Re: citations: org-cite vs org-ref 3.0

Disclaimer: I am neither org-cite no org-ref user. In the past I used LaTeX and BibTeX directly though, and it is a reason why I am reading the discussions. On 20/03/2022 20:19, Nicolas Goaziou wrote: Vikas Rawal writes: This obviously creates many problems including that two people using

Re: citations: org-cite vs org-ref 3.0

On Mon, Mar 21, 2022 at 9:13 AM Dominik Schrempf wrote: > > “Bruce D’Arcus” writes: > > > On Mon, Mar 21, 2022 at 8:41 AM Dominik Schrempf > > wrote: > >> > >> Thank you, I can use `citar-insert-edit` to perform this action. > > > > You can actually just use org-cite-insert, which is context

Re: citations: org-cite vs org-ref 3.0

"Bruce D'Arcus" writes: > On Sun, Mar 20, 2022 at 9:42 AM Ihor Radchenko wrote: > >> For citar, why not simply using ivy-bibtex? It supports org-cite, AFAIK. > > Not really; or rather minimally. > > Ivy-bibtex supports, for example, inserting of org-cite citations, but > not via

Re: citations: org-cite vs org-ref 3.0

Am Sun, Mar 20, 2022 at 08:31:29PM -0400 schrieb John Kitchin: > For those who need high fidelity LaTeX export like I do, I think > org-ref is still a superior solution. For everyone else, and > especially if you do not need sophisticated cross-references and don't > want the dependencies of

Re: [BUG] Agenda no longer works for timestamps inside properties drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

>> What you see in the new Org version is not a bug. Property values are >> treated as plain text by Org. >> >> I was unable to find a place in manual describing that timestamps cannot >> be placed inside property values: >> I personally see allowing timestamps (and links) inside property values

RE: [BUG] Agenda no longer works for timestamps inside properties drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

Ihor writes: > I personally see allowing timestamps (and links) inside property values as a > useful feature. > Would it be of interest for other users? Yes, it's a quite useful feature. For years, via my Capture templates, I've been adding a property named :Created: to the properties drawer

Re: [PATCH] Re: [BUG] org-cite: 10 second hang opening a ~4k org file with 10MB bibtex library

Hello, On So, Mär 20 2022 at 12:20:42 +0800, Ihor Radchenko wrote: I have seen your email. Persisting the cache between sessions is a more tricky. It will require a dedicated effort - significantly more than the few-liner patch here. Ah, I am not programmer and made an uneducated

Re: citations: org-cite vs org-ref 3.0

> > > > I don't think you have to choose. You can use org-cite for > citations, and org-ref for cross-references. The citation syntax is > orthogonal, you just should not mix them. That is excellent then. Thanks for clarifications. Best, Vikas

[PATCH] Re: Prompt when resolving clocks [9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)]

Hello, After some discussion on the subject on another topic (see https://lists.gnu.org/archive/html/emacs-orgmode/2022-03/msg00233.html), I have a small patch that prevents the prompt for disappearing on unwanted events, using `read-char-exclusive'. You will find it enclosed. Regards, Romeo

Re: citations: org-cite vs org-ref 3.0

"Bruce D'Arcus" writes: > On Mon, Mar 21, 2022 at 10:41 AM Max Nikulin wrote: > > ... > >> A bit of routine work will alleviate some user issues: >> - add missed styles > > The initial list of style-command mappings was pretty comprehensive, > but we left out some of the more obscure biblatex

Re: [BUG] Agenda no longer works for timestamps inside properties drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

this is merely intuition, but i can - understand why planning line tses should not be matched in various places; they are closely tied to real org entries - not quite grasp why bare active and inactive tses should not be matched by ts agenda almost anywhere including blocks. perhaps the idea is

RE: [BUG] Agenda no longer works for timestamps inside properties drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

Ignacio writes: > I've located the line in org-agenda.el responsible of the new behavior, > and the following patch seems to fix it. I suggest it is incorporated > into the repository, maybe with a variable org-agenda-skip-timestamps- > in-properties-drawer defaulting to t if not everyone

Re: [PATCH] org-agenda: Skip formatting if format string is ""

Samim Pezeshki writes: > Is there anything I need to do for this to be merged? Applied. I took a freedom to push your patch to bugfix amending the indentation changes. (847e33230) Note that your total contribution to Org is approaching 15 LOC - a legal threshold for insignificant changes. If

Re: [BUG] error after reading in contents of other file [9.6 (9.6-??-e7ea951 @ /home/user/.emacs.d/.local/straight/build-28.0.50/org/)]

Mark Edgington writes: > Yes, I'm still getting the following: > > Emacs : GNU Emacs 28.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ Version > 3.24.20, cairo version 1.16.0) of 2022-01-15 > Package: Org mode version 9.6 (9.6-??-e7ea951ac @ > /home/user/.emacs.d/.local/straight/build-28.0.50/org/)

Re: citations: org-cite vs org-ref 3.0

Hi, I am trying out `org-cite' right now. It works much better than the last time (I am using the `biblatex' backend right now). However, I can not find any documentation about the available /styles/. They are mentioned here: But no styles are

Re: [RFC] DOCT: Declarative Org Capture Templates (easier template syntax)

Mark Barton writes: > I was concerned about long term support and if I would be left with templates > I would have to rewrite again, plus I was too busy at the time to adopt it > and it stays in my list of TODOs that are not scheduled. To clarify, I do not think that we need to switch to doct

Re: Problems with babel reading Japanese paths in Windows

Jonathan Nogueira writes: > I did and it seems to work fine, I also tested this using plantuml-mode's > normal compliation procedure. > > This seems to specifically be a problem with org-mode and babel's > compilation Then, could you provide an example source block and the command line emitted

Re: [RFC] DOCT: Declarative Org Capture Templates (easier template syntax)

Nicolas Goaziou writes: > I think there should be a direct mapping between Customize interface and > values. Adding this macro as a band-aid to simply configuration is not, > IMO, a solution. I think that current customize interface for org-capture-template is perfectly fine. doct aids users

Re: How do you manage complex project with Org-mode

Tim Cross writes: > My point was not that you don't need to review on a regular basis. > Reviewing your tasks and projects regularly is essential. My point was > that creating a todo task telling you to review your tasks/projects is > an example of a 'noise' task. I guess that it depends on

Re: org-contacts.el use lexical-let not defined in cl-lib

Michael Eliachevitch writes: > [[PGP Signed Part:Undecided]] > Dear all, > > I'm not sure if this is the correct mailinglist for org-contrib bugs. I found > that org-contacts.el uses `lexical-let*` which is defined in `cl`, but it > only requires `cl-lib` where it is not defined. > > I found

Re: citations: org-cite vs org-ref 3.0

On Mon, Mar 21, 2022 at 4:24 AM Dominik Schrempf wrote: > I am trying out `org-cite' right now. It works much better than the last time > (I > am using the `biblatex' backend right now). However, I can not find any > documentation about the available /styles/. > > They are mentioned here:

[org-contrib] Take over maintaining of org-contacts.el

Hi Danjou, Since the package org-contacts.el is not maintained for a long time. I would like to take over maintaining of org-contacts.el. What do you think? I used to send you an email with asking. But got no response. Hi Bastien, If org-contacts.el author is not response for a long time, can