* lisp/ox-ascii.el (org-ascii--justify-lines): Ensure that
`indent-tabs-mode' is nil when applying indentation to justify lines.
This prevents tab characters from appearing in the export when
`indent-tabs-mode' still has its default value of t. TINYCHANGE
---
Hi,
I've attached a patch to fix an
Timothy writes:
> Hi Morgan,
>
>> I’ve attached a patch to fix an issue where tab characters are generated by
>> the ASCII exporter when `indent-tabs-mode’ has its default value of t.
>
> Thanks for finding this bug, fixing it, and sending us it . I was able to
> reproduce your test case with
* lisp/ox-ascii.el (org-ascii--justify-lines): Ensure that
`indent-tabs-mode' is nil when applying indentation to justify lines.
This prevents tab characters from appearing in the export when
`indent-tabs-mode' still has its default value of t. TINYCHANGE
---
Hi,
I've attached a patch to fix an
Timothy writes:
> Hi Morgan,
>
> I’ve just taken a look at your patch (it `git am's just fine), since nobody
> else
> seems to have had the time to look at your patch as of late. There’s one thing
> which I now realise completely slipped by me last time — why are tabs bad?
> Maybe I’m missing
Jean-Christophe Helary writes:
> I'm trying to work with SourceHut (sr.ht) and right now they only accept
> Markdown syntax for their readme/wiki files.
Hi Jean-Christophe,
If this is just for SourceHut you can use an HTML export and upload it
via the API instead of committing a Markdown
Tim Cross writes:
> Based on your report of having org 9.3, my suspicion is that your org
> version is too old for the current Emacs versions (since the change in
> 2019 to use default-indent-new-line for C-M-j and M-j. I don't think
> this is a bug in current Org or Emacs.
Just for reference,
c's "markdown" format is not the same format which is
described at daringfireball.net:
https://pandoc.org/MANUAL.html#pandocs-markdown
--
Morgan Willcock
s specification in order to inter-operate.
For Pandoc, the matching specification needs to be selected to ensure
that the correct one is used, but nothing based on Markdown.pl can be
unambiguous in this scenario because Markdown.pl has no unambiguous
specification.
--
Morgan Willcock
I've managed to trigger this a couple of times over the last few days,
both times the backtrace began by calling flyspell functions. I'm not
sure how to re-create the problem, but I thought it best to report it
just in case anyone else is seeing the same thing.
⛔ Warning (org-element-cache):
hould work if the asterisk is outside of the
quotes. I've attached an (untested) patch to explain what I mean.
--
Morgan Willcock
>From b5f52034b693175df2ec057cb5e9e4de55e70078 Mon Sep 17 00:00:00 2001
From: Morgan Willcock
Date: Sat, 10 Feb 2024 21:02:30 +
Subject: [PATCH] org-ctags.el
Ihor Radchenko writes:
> Morgan Willcock writes:
>
>> I've managed to trigger this a couple of times over the last few days,
>> both times the backtrace began by calling flyspell functions. I'm not
>> sure how to re-create the problem, but I thought it best to report i
n of
cmd.exe, although I wouldn't expect it to be 100% compatible with the
real thing.
--
Morgan Willcock
Ihor Radchenko writes:
> Morgan Willcock writes:
>
>>> Would you be able to upgrade to the development version of Org mode and
>>> test if the warning disappear?
>>
>> I would be willing to for diagnostic purposes (presumably I would just
>> ma
13 matches
Mail list logo
