This looks like a bug in ob-C.el
Around line 196 we should replace
(org-babel-read results t)
with
results
In this way, ob-C.el will look more like ob-shell.el
Let me see what are the consequences with such a fix.
Thanks Marti
Max Nikulin writes:
> It's pity that this issue has not fix yet. I have tried to implement
> another helper function. It is hardly usable outside of `org-open-file'
> (perhaps it is still suitable to make mailcap commands), but separate
> function makes the code testable. I hope, the attached
alain.coch...@unistra.fr writes:
> Ihor Radchenko writes on Wed 31 Aug 2022 09:57:
>
> > This is not a bug. Just unintuitive syntax:
> > [...]
> > The important part is: It ends at the next footnote definition,
> > headline, or after two consecutive empty lines.
> >
> > So, your example is
Rudolf Adamkovič writes:
> Subject: [PATCH 1/2] Fix incorrectly documented auto-numbering of MathJax
> equations
> Subject: [PATCH 2/2] Fix under-documented MathJax indentation option
Thanks!
Applied onto main via 710b6ca70 and 74d1a8c75.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/com
Ok thanks a lot for your answers, I made the function, if ever it can
interest someone one day
(defun org-get-tags-with-hierarchy-at-point()
"Return the list of tag WITH the sub-tags if they exist at point"
(interactive)
(let ((tags-heading (org-get-tags))
(tags-resu
Eduardo Suarez writes:
> I have lots of tasks (todos) and I would like to create a long backlog based
> on
> my perceived priority.
>
> I was thinking to deal with them in the following way:
>
> - divide them in groups (categories or similar),
> - manually sort priority for every group,
> - merg
Uwe Brauer writes:
>> Timestamp format is hard-coded in Org syntax. See
>> https://orgmode.org/worg/dev/org-syntax.html#Timestamps
>
> I see, but I just learned that also
>
> <2022-09-01>
>
> Is interpreted as a timestamp not only
>
> <2022-09-01 Thu>
Yes. Day name is optional.
> However alth
Sébastien Miquel writes:
> Ihor Radchenko writes:
> > They do not. Tags are only considered inside headlines. Trying to allow
> > tags outside headlines will require major changes across the whole Org
> > codebase and will still make things incompatible with third party
> > packages, like org
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>>> Timestamp format is hard-coded in Org syntax. See
>>> https://orgmode.org/worg/dev/org-syntax.html#Timestamps
>>
>> I see, but I just learned that also
>>
>> <2022-09-01>
>>
>> Is interpreted as a timestamp not only
>>
>> <2022-09
Uwe Brauer writes:
> I see, the question simply is this:
>
> How can I achieve that org-time-stamp inserts the date *without* the day
> name?!
This cannot currently be customized. However, you can change
org-time-stamp-formats constant. Removing the %a should be safe.
--
Ihor Radchenko,
Org mo
Ihor Radchenko writes:
> Sébastien Miquel writes:
>
>> Ihor Radchenko writes:
>> > They do not. Tags are only considered inside headlines. Trying
to allow
>> > tags outside headlines will require major changes across the
whole Org
>> > codebase and will still make things incompatible w
On 02/09/2022 19:08, Ihor Radchenko wrote:
Max Nikulin writes:
Subject: [PATCH] org.el: Fix percent substitutions in `org-open-file'
+(defun org--open-file-format-command
+(mailcap-command file link match-data)
+ "Format MAILCAP-COMMAND to launch viewer for FILE.
+
...
+For example, to
I'm looking at function that handles transcoding inline code and verbatim text
in ox-md:
(defun org-md-verbatim (verbatim _contents _info)
"Transcode VERBATIM object into Markdown format.
CONTENTS is nil. INFO is a plist used as a communication
channel."
(let ((value (org-element-property :v
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.
--
This fix in ob-C.el passes all unit tests, as well as Martin's
example, and some other examples.
If someone get a regression, please tell me!
In a few days, I will commit.
The fix: in ob-C.el line 185, change:
(org-babel-read results t)
t
As I understand it, the bug is in `org-md-item'. It formats the tag portion of
the
description with **%s**, and then simply concatenates the content. This is fine
when the content is a simple string, but when the content includes line breaks
(i.e. when content is itself a list), it doesn't realize
"Rohit Patnaik" writes:
> As I understand it, the bug is in `org-md-item'. It formats the tag portion
> of the
> description with **%s**, and then simply concatenates the content. This is
> fine
> when the content is a simple string, but when the content includes line breaks
> (i.e. when cont
"Rohit Patnaik" writes:
> My question is, why does org-md-verbatim use org-element-property to retrieve
> the text to be transcoded, when org-md-bold and org-md-italic use the contents
> parameter. In other words, couldn't the function be simplified to something
> like
> this:
You can't because
18 matches
Mail list logo
