Org lint and Haskell source code blocks

Hi, whenever I have a Haskell source code block in my Org mode file, and I execute =org-lint=, I get the following error: #+begin_quote Debugger entered--Lisp error: (wrong-type-argument listp :any) #+end_quote (This was obtained with a minimal file just having: #+BEGIN_SRC haskell inc n = n+1 #

Re: Advice for new feature 'image block` for new `sketch-mode` package

Also, I already looked at the org source to see how to add e.g. a #+BEGIN_IMAGE block, but I found the 'api' quite overwhelming. So I am hoping that some experienced developer could maybe give some advice/explain (for) how to approach/implement this. On Mon, 20 Sept 2021 at 20:19, dalanicolai wro

Advice for new feature 'image block` for new `sketch-mode` package

Hello, I am developing a new package for quickly sketching svg images, (see, and try out, sketch-mode at https://elpa.gnu.org/devel/). With the package, I can already quickly create a sketch and subsequently quickly save it and insert a link in some org-mode buffer (using the `b` transient suffix)

Re: Emacs-orgmode Digest, Vol 187, Issue 19

On 20/09/2021 00:16, Ypo wrote: Then I think I will behave like grown people and use LaTeX syntax, previewing it on HTML exports, cause it gives no errors compared to the problematic PDF exports. I never considered HTML as a viable preview option for LaTeX equation, so thanks for the idea.

Re: Internal link broken when publishing (was org-id with ox-html)

On Monday, 20 September 2021 16:13:24 CEST Max Nikulin wrote: > On 20/09/2021 07:05, chris wrote: > > On Tuesday, 14 September 2021 18:33:43 CEST Max Nikulin wrote: > >> As a kind of summary: > >> > >> During publishing of a project > >> - "id:" links to headings from the same file are exported as

Re: [PATCH] ox.el: add smart quotes for Greek

On 19/09/2021 23:30, Juan Manuel Macías wrote: I attach here a tiny patch to add Greek smart quotes. Finally, I apply the second level quotation marks that Protesilaos Stavrou proposed in this previous thread: https://orgmode.org/list/87o89yv1mz@cnu407c2zx.nsn-intra.net/#r Since the choice

Re: [PATCH] org-cite: Use citeproc-el to create CSL processor itemgetters

Hi Timothy, > Regarding the content of this patch and the few you have planned that follow — > would it be fair to say that overall you’re trying to update `oc-csl' based on > changes you’ve made to `citeproc-el' since `oc-csl' was written? yes exactly, basically all of my patches are directed to

Re: Internal link broken when publishing (was org-id with ox-html)

On 20/09/2021 07:05, chris wrote: On Tuesday, 14 September 2021 18:33:43 CEST Max Nikulin wrote: As a kind of summary: During publishing of a project - "id:" links to headings from the same file are exported as short generated anchors like #org032777e or as anchors to custom ids when the latter

Re: [PATCH] org-cite: Use citeproc-el to create CSL processor itemgetters

Hi András, Great to see this patch from you 🙂. > this is the first item in a series of oc-csl patches which I’ve > accumulated and am planning to send this week. (My first attempt to > send a patch, so please be patient and forgiving :-) ) This may be your first attempt sending a patch, but it

[PATCH] org-cite: Use citeproc-el to create CSL processor itemgetters

Dear All, this is the first item in a series of oc-csl patches which I've accumulated and am planning to send this week. (My first attempt to send a patch, so please be patient and forgiving :-) ) This particular change removes the itemgetter constructor function defined in oc-csl.el and uses the

Re: [kisara.moe] Re: [kisara.moe] Re: [kisara.moe] Re: [kisara.moe] Re: [kisara.moe] Re: Bug: async latex export fails due to post-process lambda [9.4.4 (release_9.4.4-188-ga8df76 @ /home/mohkale/.con

Sébastien Miquel writes: > Are you using native compilation ? I think this must be the cause, > though no one Yes I was on the native compile branch and now on mainline emacs with native-compile enabled. -- Mohsin

Re: Suggestions for improved suffix parsing in oc-biblatex

Bump Am 08.09.2021 um 15:37 schrieb Denis Maier: Hi, I think the suffix parsing in oc-biblatex could be improved. Consider this example: #+cite_export: biblatex authoryear [cite:@doe 4] [cite:@doe 4, with some more text]

Re: Spurious spaces with oc-biblatex

Bump. Am 08.09.2021 um 16:36 schrieb Denis Maier: Update 2: This also happens with #+cite_export: csl Maybe this is useful for tracking this down. Denis Am 08.09.2021 um 16:30 schrieb Denis Maier: Ok, it looks like this also happens with: .[cite:@doe] => . \autocite{doe} Is that on purpo

Re: Switching to new Git repositories

Bastien, thank you. My bad: I tried to simply change the url in the .git/config but hadn't realised that the branch information etc. was different. I've cloned anew and everything is fine. -- : Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-637-gd70f28 : Latest paper written in org: https:/

Re: Switching to new Git repositories

Thanks you both! Thanks to you I use a suitable reference to the repo now! My first tiny commit landed in the new repo AFAICS. Note that I had wrongly filled out the form for the ssh-key on the savannah platform. Clearly this is my fault. BTW the documentation is all there on the savannah page

Re: Switching to new Git repositories

Hi Éric, Eric S Fraga writes: > On Monday, 20 Sep 2021 at 11:27, Bastien wrote: >> You need to create an account on https://savannah.gnu.org and have >> your username there being accepted in the Emacs group: > > What about those of us that do not wish to have write access but do want > to simply

Re: Switching to new Git repositories

On Monday, 20 Sep 2021 at 11:27, Bastien wrote: > You need to create an account on https://savannah.gnu.org and have > your username there being accepted in the Emacs group: What about those of us that do not wish to have write access but do want to simply track the development? Neither of the li

Re: Switching to new Git repositories

Hi Marco, Marco Wahl writes: > My first attempt to commit to the new repo > https://git.savannah.gnu.org/cgit/emacs/org-mode.git failed. You need to create an account on https://savannah.gnu.org and have your username there being accepted in the Emacs group: https://savannah.gnu.org/git/?group

Re: Switching to new Git repositories

Hi Marco, > My first attempt to commit to the new repo > failed. > > Would you mind to describe what preconditions are needed to be able to > commit? Is it just a question of using the right URL at clone time? > > Would you even update file

Re: Switching to new Git repositories

Hi Bastien, Thanks for all! > from now on, here are the official Org repositories: > > - org-mode: https://git.savannah.gnu.org/cgit/emacs/org-mode.git > - worg: https://git.sr.ht/~bzg/worg > - orgweb: https://git.sr.ht/~bzg/orgweb > > org-contrib will continue to be on https://git.sr.ht/~bzg/org

Re: [PATCH] Add faces to improve contextuality of agenda views

On 2021-09-19, 21:23 +0800, Timothy wrote: > Hi Protesilaos, Hello Timothy, > Thanks for sending this patch in, and sorry it’s taken a while for you to hear > anything back. No worries. I understand this is a voluntary effort. > I see the utility of org-imminent-deadline, but am fairly indi

Re: BUG Visibility Cycling with inline tasks

Michael Dauer writes: > What I get after the first org-cycle is: > * Example > ** heading 1 > ** heading 2 > * ** TODO Test access with provided credentials > ** heading 3 > x > * ** END > ** heading 4 > x > I cannot reproduce on latest master and with Org 9.4.4

version-to-list: Invalid version syntax: ‘9.5-dev’

Hello, I moved to the new repo and rebuild org. Now I get the following error message: version-to-list: Invalid version syntax: ‘9.5-dev’ It seems someone checks for the version number and can’t handle the ´-dev´. When I change org-version.el to ’9.5’ (which I shouldn’t do) the problem is gon

Re: DONE headlines take a different color

Jim Porter wrote: On 9/19/2021 9:09 AM, Giovanni Gigante wrote: As per the subject: TODO states mantain the headline color (as expected), but DONE states change it (not expected). As shown in lines 2, 5, 8, 11, 14 of the following screenshot (emacs 27.2 on MacOS launched with -q,  org mode

Re: BUG Visibility Cycling with inline tasks

What I get after the first org-cycle is: * Example ** heading 1 ** heading 2 * ** TODO Test access with provided credentials ** heading 3 x * ** END ** heading 4 x So it also shows part of the following heading. This "garbage" can be max more if the following subt