When I run org-store-link inside a .bib file, I get the cache error below.
If somebody's interested, I can send the log separately in a zip file.
It's too big for my email client to send uncompressed, and I believe I
can't send compressed files to this list.
This is using:
Emacs : GNU Emacs
Ihor Radchenko writes:
> So, we should probably override `org-export-coding-system', even when it
> is set. iCalendar demands UTF8 anyway.
Also, ox-icalendar already sets ":ascii-charset utf-8" in the ext-plist
during export.
> We likely want (according to 34.10.1 Basic Concepts of Coding
On Thu, 30 Mar 2023 04:55:32 -0400 Ihor Radchenko wrote ---
> Matt m...@excalamus.com> writes:
>
> > I think this approach will work fine. I tried examples for each shell
> > type and keywords like if/then/else and function names are highlighted.
>
> Even for posh
Ihor Radchenko writes:
> I finally managed to fix the tests.
Thank you! I have had this on my to-do list since you brought it up,but
I could not find the time to fix it.
Rudy
--
"'Contrariwise,' continued Tweedledee, 'if it was so, it might be; and
if it were so, it would be; but as it
>>> "JK" == John Kitchin writes:
> there isn't enough information to tell what you are trying to do or if it
> is the right thing to do. I don't think that is how org-ref exports to HTML
> anymore, now it uses CSL. There is something like that syntax for
> bibtex-completion-display-formats.
>
On 29/03/2023 23:52, Ihor Radchenko wrote:
Max Nikulin writes:
Sorry, I have not tried to compile Emacs myself and I am really puzzled
why you was not able to reproduce the issue.
I was able to reproduce on Debian using virtual machine.
To be precise, I am surprised that you are unable to
On 01/04/2023 18:38, Daniel Mendler wrote:
From my side, the change looks good. The current Compat version 29.1.4.x
is stable with no known issues.
Debian Bookworm and Ubuntu 23.04 (currently frozen testing and beta
accordingly) have elpa-compat-29.1.3.4 and 29.1.3.2. Are some issues
there isn't enough information to tell what you are trying to do or if it
is the right thing to do. I don't think that is how org-ref exports to HTML
anymore, now it uses CSL. There is something like that syntax for
bibtex-completion-display-formats.
You should file an issue at
Hi,
I was wondering if anyone had any new ideas on this question (or an explanation
on what Timothy meant by a :dir parameter).
Right now I'm having to use a search and replace back on the whole generated
html buffer, which is fragile and inefficient.
Thanks,
Omid
Original Message
On 4/1/23 12:31, Ihor Radchenko wrote:
> Ihor Radchenko writes:
>
>> I have recently been contacted by the current compat.el maintainer
>> asking if we are willing to adapt compat.el in Org.
>
> See the attached patch set adding support of compat.el.
>
> I had to update Org's build system to
Ihor Radchenko writes:
> I have recently been contacted by the current compat.el maintainer
> asking if we are willing to adapt compat.el in Org.
See the attached patch set adding support of compat.el.
I had to update Org's build system to handle third-party packages.
Please, give it a close
Jack Kamm writes:
> For issue 1, what `org-icalendar-fold-string' does when string already
> contains \r\n, you can see that it produces \r\r\n as follows:
>
> emacs -Q -l ox-icalendar
> M-:
> (org-icalendar-fold-string (org-icalendar-fold-string "Line1\nLine2"))
>
> This is why the patch
Corwin Brust writes:
>> Thanks, but you cannot put language as example block argument.
>>
>
> When I remove the language argument ("org"), org resumes thinking it
> is a link: it becomes a button and hides the markup we are giving an
> example of.
This is just a visual fontification glitch
13 matches
Mail list logo
