From: Henrik Frisk <frisk.h@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: ob-lilypond fontification
Date: Sat, 26 Aug 2023 14:24:22 +0200 [thread overview]
Message-ID: <CAO0LSb7LuX4_o5jKCs6BWyNEaDg1twi6rKW14pz3cN4CMpu7yw@mail.gmail.com> (raw)
In-Reply-To: <CAO0LSb5SkYUOdjTxdfikjT-J3aic_OmHP30x14i1KvSxPFJL5w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
Den ons 23 aug. 2023 kl 08:04 skrev Henrik Frisk <frisk.h@gmail.com>:
>
>
> On Tue, Aug 22, 2023, 6:17 PM Ihor Radchenko <yantar92@posteo.net> wrote:
>
>> Henrik Frisk <frisk.h@gmail.com> writes:
>>
>> > So I grabbed the file ob-lilypond from another inactive install of Emacs
>> > 29.1 and linked to it in my init file. Everythin appears to work fine
>> > except I dont get syntax highlightning unless I hit C-c '
>>
>> I recommend installing Org mode from ELPA to make sure that you are
>> using the latest version.
>>
>> Also, there were possibly relevant changes on development branch. So you
>> might need ELPA devel version.
>>
>
> Makes sense. I will try that, thanks!
>
So I changed to the main branch of
git://git.savannah.gnu.org/emacs/org-mode.git
and the new features you added to ob-lilypond is working (much
appreciated) but I still don' have syntax highlight in source blocks
though it works fine in lilypond-mode.
/Henrik
[-- Attachment #2: Type: text/html, Size: 1905 bytes --]
next prev parent reply other threads:[~2023-08-26 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 16:04 ob-lilypond fontification Henrik Frisk
2023-08-22 16:18 ` Ihor Radchenko
2023-08-23 6:04 ` Henrik Frisk
2023-08-26 12:24 ` Henrik Frisk [this message]
2023-08-26 12:27 ` Ihor Radchenko
2023-08-26 14:08 ` Henrik Frisk
2023-08-26 16:24 ` Ihor Radchenko
2023-08-27 7:29 ` Henrik Frisk
2023-08-27 7:49 ` Ihor Radchenko
2023-08-27 15:19 ` Henrik Frisk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAO0LSb7LuX4_o5jKCs6BWyNEaDg1twi6rKW14pz3cN4CMpu7yw@mail.gmail.com \
--to=frisk.h@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).