Re: bug#59882: Multiple versions of Org in load-path problem

Max Nikulin writes: > I found just single commit to lisp/emacs-lisp/package.el between > emacs-27.1 and emacs-27.2: > > 1fc9de4b81c 2020-10-30 19:20:24 -0700 Glenn Morris: Improve > reproducibility of generated -pkg.el files > > So I am still surprised that you can not reproduce the issue. Can

Re: [BUG] org-block face not working for "non-default" languages

duskhorn writes: > This works perfectly! > I get both fixed pitch and syntax highlight! > Thank you so much for your work, Ihor! Applied onto bugfix. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=ecfb55af0 -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about

Re: bug#59882: Multiple versions of Org in load-path problem

On 27/12/2022 16:47, Ihor Radchenko wrote: Can you then try to test using Emacs 28? The main question if whether this has been fixed in newer Emacs releases or it is also something to do with OS environment. I see quite the same issue with Emacs-28.2 in Debian testing. Compile buffer displays

Re: 'C-c a s' sometimes gives as result the END of an inelinetask

alain.coch...@unistra.fr writes: > Here is a minimal example: file debug2.org which contains > >* foo >*** inlt >ininlt >*** END >bar > > ... > Then I do > >M-x org-agenda < s bar Thanks for reporting! Fixed on bugfix. https://git.savannah.gnu.org

Re: CSV agenda export formats some day and month values as single digits

Max Nikulin writes: >> The reason I suggest using the default value is that >> `calendar-iso-date-display-form' is a defcustom. > > Thank you, I did not noticed that it is a user option. I should think > more on this. If a user has a reason to override the ISO format, perhaps > it should be res

Re: Export Org with Org concept -- Re: Problems with C-c C-e file.org,

Jean Louis writes: > If you mean formatting of the text, how it looks like, then retain > formatting of text. That is choice. That is not part of the offered > concept. Yes, that's what I was referring to. I am not against non-blocking interface per se. > QUESTION: Should I now add the ordinar

Re: [PATCH] lisp/ob-tangle.el, lisp/ob-core.el: Add strip-tangle noweb option

Ihor Radchenko writes: > Also, several small comments about the commit message. For the record, an amended version of this patch have been applied. See https://orgmode.org/list/87leona2r1.fsf@localhost -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

copying text from links makes it with a starting [[

Hi all, I'm not sure this is an org problem, rather a clipboard problem or what else, but when I select an org link in Emacs and I copy into my Firefox browser, the link has always a starting pair of square brackets (e.g. [[https://...). What puzzles me is that there are no ending brackets, as it w

Problem with multi-occur search when restricted to region

Tested with Org mode version 9.6 (release_9.6-149-g554935.dirty @ /home/cochard/Org/Coch-git/org-mode/lisp/) I have the file debug.org containing * h1 foo * h2 foo bar I make the 1st two lines the region. Then I do M-x org-agenda << / foo and I see 2 matches for "f

Re: copying text from links makes it with a starting [[

Luca Ferrari writes: > I'm not sure this is an org problem, rather a clipboard problem or > what else, but when I select an org link in Emacs and I copy into my > Firefox browser, the link has always a starting pair of square > brackets (e.g. [[https://...). > What puzzles me is that there are no

Re: Problem with multi-occur search when restricted to region

alain.coch...@unistra.fr writes: >* h1 >foo >* h2 >foo bar > > I make the 1st two lines the region. Then I do > >M-x org-agenda << / foo > > and I see > >2 matches for "foo" in buffer: debug.org >2:foo >4:foo bar Thanks for reporting! Can you try the attac

Re: [BUG] ox-html does not export captions of source blocks without language

Johan Bolmsjö writes: > ** Description > > The caption "Caption 1" is not exported by ox-html in the following > source block. > > #+caption: Caption 1 > #+begin_src > foo bar baz > #+end_src > > The caption "Caption 2" is exported by ox-html in the following source > block. > > #+caption: Captio

[FR] Present list of errors in separate buffer when running org-export, similar to what org-lint does (was: [Syntax discussion] Should we treat src blocks without LANG as paragraphs?)

As Max proposed, it may be a good idea to extend the concept of org-lint to export. We may unify the LaTeX errors, some errors/warnings potentially signalled by export backend, and maybe some warnings from org-lint during the export process. These errors can ideally be displayed just like in org

Re: copying text from links makes it with a starting [[

El 2022-12-27 08:06, Luca Ferrari escribió: > Hi all, > I'm not sure this is an org problem, rather a clipboard problem or > what else, but when I select an org link in Emacs and I copy into my > Firefox browser, the link has always a starting pair of square > brackets (e.g. [[https://...). > What

Re: ob-groovy.el must be hand-loaded?

Galaxy Being writes: > form. I've renamed it apache-groovy and it errored out specifically not > finding ob-groovy.el. But again, if I don't specifically load the org-9.6 > ob-groovy.el, I get "can't find program groovy" upon block C-c C-c. This error sounds like ob-groovy has been loaded (you c

Re: copying text from links makes it with a starting [[

El 2022-12-27 09:34, Esteban Ordóñez escribió: > As Ighor wrote, please post the exact details of what you did so we can > do it the same way as you do in our own environment. Sorry for the typo, Ihor!

Re: [PATCH] lisp/ob-octave.el, was [PATCH] rfc: using ert-deftest with side-effects

Leo Butler writes: >> Note that the tests are failing only partially. The graphics file does >> get created, but it has 0 size for some reason. Maybe something to do >> with non-graphical CI environment. > > There is a race condition between writing the contents of the graphics > file to disk and

Re: copying text from links makes it with a starting [[

On 27/12/2022 20:06, Luca Ferrari wrote: I'm not sure this is an org problem, rather a clipboard problem or what else, but when I select an org link in Emacs and I copy into my Firefox browser, the link has always a starting pair of square brackets (e.g. [[https://...). Selecting link to copy i

Expand macros in links

Hi, I do not understand why links are excluded from macro expansion. I would see it as very valuable to have macros for links too. The change would be as simple as inserting (eq type 'link) into org-macro-replace-all. May I recommend this patch. Thanks, Michael

Re: Expand macros in links

Michael Dauer writes: > I do not understand why links are excluded from macro expansion. I would > see it as very valuable to have macros for links too. Are they? Could you please provide an example? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: Expand macros in links

I mean something like: * Heading [[http:abc{{{input-file}}}] When exporting it to html then the link is not replaced. I'm talking about expansion when exporting. But I also implemented macro expansion for following links within emacs quite a while ago. Different story but also very powerful espe

Re: Expand macros in links

Michael Dauer writes: > I mean something like: > * Heading > [[http:abc{{{input-file}}}] > > When exporting it to html then the link is not replaced. This is to be expected, and I do think that Org is doing it right by not replacing macros in links. You cannot exactly control what is inside lin

Re: Expand macros in links

I'm aware of this theoretical conflict. But I see the risk as very low compared to the value of not having to make a lot of customizations for export and internal link handling. It should just work out of the box. If you deem necessary there would still be the possibility to define a global switch

Re: Expand macros in links

Michael Dauer writes: > I'm aware of this theoretical conflict. But I see the risk as very low > compared to the value of not having to make a lot of customizations for > export and internal link handling. It should just work out of the box. Even low risk does not justify impossible-to-use links

Re: Expand macros in links

Agree. How do you run such feature polls? Ihor Radchenko schrieb am Di., 27. Dez. 2022, 17:20: > Michael Dauer writes: > > > I'm aware of this theoretical conflict. But I see the risk as very low > > compared to the value of not having to make a lot of customizations for > > export and internal

[FR] Please add writing to existing heading in org-bibtex

The default behavior of org-bibtex-write is to insert a new heading with the bibliographic data in the properties. But an alternative workflow would just update the properties of the heading at point, rather than creating a new one. The below patch is a simple implementation I’ve been using for a m

Re: Expand macros in links

Michael Dauer writes: > Agree. How do you run such feature polls? Change subject to something like [FR] [POLL] Allow expanding macros in link path like [[https://site-{{{macro}}}.com]] Then see how many people reply. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Or

Re: Bug? org-assert-version does not prevent mixed install

On 18/12/2022 21:26, Ihor Radchenko wrote: Max Nikulin writes: We might do something like (eval-and-compile (org-assert-version)) This will give obscure error during compiling since `org-assert-version' is not defined. Yes, but we will at least abort the compilation this way. You are rig

Re: [FR] Please add writing to existing heading in org-bibtex

Sterling Hooten writes: > The default behavior of org-bibtex-write is to insert a new > heading with the bibliographic data in the properties. But an > alternative workflow would just update the properties of the heading at > point, rather than creating a new one. The below patch is a simple > im

Re: [FR] Present list of errors in separate buffer when running org-export, similar to what org-lint does (was: [Syntax discussion] Should we treat src blocks without LANG as paragraphs?)

Ihor Radchenko writes: > As Max proposed, it may be a good idea to extend the concept of org-lint > to export. > > We may unify the LaTeX errors, some errors/warnings potentially signalled > by export backend, and maybe some warnings from org-lint during the > export process. These errors can i

[Bug] isearch errors when org-fold-core-style is 'overlays

I'm finding that isearch fails to unfold the correct region or to search in the correct region when there are folded regions in a buffer and `org-fold-core-style` is set to 'overlays. Here is a minimal recipe for reproducing the bug: Use a minimal emacs startup file: --8<---cut here-

Re: Problem with multi-occur search when restricted to region

Ihor Radchenko writes on Tue 27 Dec 2022 13:43: > Can you try the attached patch? It did not work with the version I initially used: release_9.6-149-g554935.dirty but it works OK with release_9.6-149-g554935 Thanks -- EOST (École et Observatoire des Sciences de la Terre) ITE (I

Re: ob-shell intentions and paperwork (was Bash results broken?)

On Wed, 21 Dec 2022 01:17:50 -0500 Matt wrote --- > Currently, though, I'm refactoring the ob-shell tests to remove dependency > on ob-shell-test.org and to stop the suite from littering. Done. Branched off bugfix, 12e10eb0d, and refactored test-ob-shell.el. See attached patches.

Re: [PATCH] oc-csl: Improve LaTeX bibliography formatting

Dear All, I have attached a new version of the patch with added ascii "illustrations". best wishes, András On Tue, 13 Dec 2022 at 20:03, András Simonyi wrote: > > Dear All, > > On Tue, 13 Dec 2022 at 17:07, Timothy wrote: > > > Perhaps an ASCII approximation in an example block could work? Even

Re: [OT] org and diff

hi marcin, thanks for your blog post on my crash-proof editing idea. more below On 12/17/22, Marcin Borkowski wrote: > > On 2022-12-17, at 03:06, Samuel Wales wrote: > >> marcin> One question I'd ask is: how important a legible diff is to >> you? I keep my Org files in Git, too, but if /I/ kn

Re: [OT] org and diff

well well. my habit of always hitting reply to all bit me. it was meant for the poster only, not for the list. apologies. it bites me once every 12 years or so. list members please disregard the message.

Re: [OT] org and diff

On 2022-12-28, at 03:30, Samuel Wales wrote: > hi marcin, > > thanks for your blog post on my crash-proof editing idea. You're welcome! :-) In fact, it was an interesting exercise. > > more below > > On 12/17/22, Marcin Borkowski wrote: >> >> On 2022-12-17, at 03:06, Samuel Wales wrote: >>