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 based
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, I
doc's "markdown" format is not the same format which is
described at daringfireball.net:
https://pandoc.org/MANUAL.html#pandocs-markdown
--
Morgan Willcock
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
tation of
cmd.exe, although I wouldn't expect it to be 100% compatible with the
real thing.
--
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): or
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 t
ell expansion should 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:
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
>> make sure
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
---
/linkremark/
I took the easy option and just use the default "integration" which uses
the clipboard, but I think org-protocol is supported as well.
--
Morgan Willcock
rawer))
nil)
...but why should the location of the note matter to the spell-checker?
Is there any way to re-enable spell-checking of the notes without adding
advice to org-mode-flyspell-verify to hijack the result?
Thanks,
Morgan
--
Morgan Willcock
ded, I cannot see any
obvious issues, although I imagine some people may see a difference if
their todo-keywords are spelled in a way that doesn't match the
dictionary being used by Flyspell, e.g. CANCELED vs. CANCELLED.
--
Morgan Willcock
piling .dir-locals.el.
I don't think there is any upstream bug. The solution would be to add
the missing header to the .dir-locals.el file.
--
Morgan Willcock
* 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 i
* 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 i
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 “e
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 s
t; I do not see any downside of adding this to .dir-locals.el file.
> Would you mind submitting a patch?
I've attached a patch.
(To be fully transparent, I have not verified that applying the patch
will prevent errors during native compilation of the ELPA package, but I
am pretty confide
19 matches
Mail list logo
