Re: org-bibtex manual

Ypo writes: > And ChatGPT offers me this alternative, which doesn't seem to work (BTW, > I am not able to install asoc.el): You do not need asoc.el.. `assoc' is the built-in function. > #+begin_src emacs-lisp > (defun my-org-bibtex-headline-format (entry) >   "Custom function to generate the

Re: org-bibtex manual

Ypo writes: > I would like to customize the name of the heading. I think it should be > customized this function: "Org Bibtex Headline Format Function". > > Is there a guide to do this? > > I can see the default is: > > #[257 "\300.\236A\207" >   [:title] >   3 "\n\n(fn ENTRY)"] >

Re: org-bibtex manual

Thanks, Ihor. I would like to customize the name of the heading. I think it should be customized this function: "Org Bibtex Headline Format Function". Is there a guide to do this? I can see the default is: #[257 "\300
\236A\207"   [:title]   3 "\n\n(fn ENTRY)"] But I don't know

Re: [TASK] Ensure built-in babel backend consistency (standard header support) and ad documentation to the manual (was: [Pre-PATCH v2] Add the capability to specify lexical scope in tangled files (was

Ihor Radchenko writes: "Thomas S. Dye" writes: AFAIK, most people assume that built-in backends are stable. If they are not, it is a bug anyway. Or we should declare that we do not maintain them. I thought "declare that we do not maintain them" meant "move them to org-contrib". I'm

Re: [TASK] Ensure built-in babel backend consistency (standard header support) and ad documentation to the manual (was: [Pre-PATCH v2] Add the capability to specify lexical scope in tangled files (was

"Thomas S. Dye" writes: >> AFAIK, most people assume that built-in backends are stable. >> If they are not, it is a bug anyway. Or we should declare that >> we do not >> maintain them. >> > I thought "declare that we do not maintain them" meant "move them > to org-contrib". I'm not sure what

Re: [TASK] Ensure built-in babel backend consistency (standard header support) and ad documentation to the manual (was: [Pre-PATCH v2] Add the capability to specify lexical scope in tangled files (was

Ihor Radchenko writes: "Thomas S. Dye" writes: IIRC, there wasn't much discussion. The current situation doesn't seem ripe for documentation in the manual. Here are some potential hurdles: - there are likely too many built-in backends; ... One way forward might distinguish between

[BUG] [PATCH] Avoid interaction in test ~ob-tangle/detangle-false-positive~

Test ~ob-tangle/detangle-false-positive~ asks for confirmation to kill the buffer, connected to testing/examples/babel.org file, that is modified during the couse of the test. Way to reproduce the bug (from projects main dir): #+BEGIN_SRC sh :dir (expand-file-name ".") emacs -Q \ -L lisp/

Re: [BUG] WORG example for ob-lilypond is no longer working as described

Graham King writes: > I'm late to this thread, and I might be missing some crucial aspect of the > problem, but if you just want to integrate lilypond scores and fragments into > a LaTeX document, and you're able to choose to use Luatex, the lyluatex and > lilyglyphs packages work beautifully

Re: [PATCH] Testing: Add tests for 'org-agenda-skip-if'

Morgan Smith writes: > * testing/lisp/test-org-agenda.el (test-org-agenda/skip-if): New test. > (test-org-agenda/non-scheduled-re-matces): Fix typo by changing name > to 'test-org-agenda/non-scheduled-re-matches'. Thanks! Applied, onto main.

Re: org-bibtex manual

Ypo writes: > Now... I would like to start using it. I have seen it has a kind of > org-capture template (M-x org-bibtex-create-in-current-entry). > > If I wanted to add more properties: > > - How should the different properties be named and filled to work correctly? In general, the types of

Re: [ANN] lisp/ob-tangle-sync.el

Apologies, this patch has been burning in the back of mind for a while now, but I keep getting distracted with other random side projects. I appreciate the wake up call, and I will refocus my efforts next week in my free time. Best, Mehmet

Re: [Pre-PATCH v2] Add the capability to specify lexical scope in tangled files (was: Add new :lexical header argument)

Timothy writes: >> I do not think that setting `lexical-binding’ file-local variable in an >> Org file makes much sense. I am sure that we can do better. > > I suppose part of the question is what sort of way we treat it? In my mind, > considering the current way lexical scope is seen in Emacs

Re: [Pre-PATCH v2] Add the capability to specify lexical scope in tangled files (was: Add new :lexical header argument)

"Berry, Charles" writes: >> IIRC, there wasn't much discussion. The current situation doesn't seem >> ripe for documentation in the manual. > > Agreed. Maybe it would suffice to use enhanced docstrings for the > org-babel-execute: functions and point to them in the manual. IMHO, this is

[TASK] Ensure built-in babel backend consistency (standard header support) and ad documentation to the manual (was: [Pre-PATCH v2] Add the capability to specify lexical scope in tangled files (was: Ad

"Thomas S. Dye" writes: > IIRC, there wasn't much discussion. The current situation > doesn't seem ripe for documentation in the manual. > > Here are some potential hurdles: > - there are likely too many built-in backends; > ... > One way forward might distinguish between babel backends for

Re: [PATCH] Keep the link if the command was cancelled

Max Nikulin writes: > On 03/07/2023 22:28, Ihor Radchenko wrote: >> If necessary, removing stored links without inserting can be made as an >> effect of negative prefix argument in `org-insert-link' or in >> `org-insert-all-links'. > > I do not think it would be a noticeable improvement. It

Re: [PATCH 2/2] doc/org-manual.org: Document org-clock-{in,out}-switch-to-state

Canceled. See https://orgmode.org/list/875y6kjmfb.fsf@localhost -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at

Re: [PATCH v2 2/2] doc/org-manual.org: Document org-clock-{in,out}-switch-to-state

"Samuel W. Flint" writes: > * doc/org-manual.org (Clocking commands): Document operation of > org-clock-{in,out}-switch-to-state. Canceled. See https://orgmode.org/list/875y6kjmfb.fsf@localhost -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: [PATCH v2 1/2] lisp/org-clock.el: Make switching states on clock-in/-out easier

Ihor Radchenko writes: > Before we continue, could you please confirm if you have FSF copyright > assignment? My records show that you have made two commits to Org mode > previously, and they total LOC is 15, which is maximum allowed > contribution that does not require copyright assignment. See