On 13/04/21 4:08 am, Nicolas Goaziou wrote:
> Hello,
>
> Ramesh Nedunchezian writes:
>
>> See the attached files. Export works fine with html and odt, btw.
>
> Fixed. Thank you.
Verified. Thank you.
Nicolas Goaziou writes:
> Hello,
>
> Ramachandran Lakshmanan writes:
>
>> I have been wanting to include a number of small Common Lisp snippets in
>> individual files which I then include into a "master" .org file using:
>>
>> #+include: "snippet.org" src lisp
>>
>> Within snippet.org I have a
probably not a relevant non-confirmation but in recent maint, my config:
- a
- /a/
- b
On 4/12/21, Juan Manuel Macías wrote:
> Hi Ypo,
>
> Ypo writes:
>
>> This is my result after doing "org-sort-list a":
>>
>> - /a/
>> - /v/
>> - a
>> - b
>>
>> Regards
>
> Thanks for trying. So it seem
Hi Ypo,
Ypo writes:
> This is my result after doing "org-sort-list a":
>
> - /a/
> - /v/
> - a
> - b
>
> Regards
Thanks for trying. So it seems that you can reproduce the problem as
well... I wonder if anyone else is able to reproduce it, preferably in a
minimal emacs.
Best regards,
Ju
Hello,
Ramesh Nedunchezian writes:
> See the attached files. Export works fine with html and odt, btw.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Thanks!
---
On Mon, Apr 12 2021, Nicolas Goaziou wrote:
Hello,
Dave Marquardt writes:
> After I filed this I got the bright idea to try exporting to Github
> Flavored Markdown and ASCII text. In all cases, src_c{*foo} was
> exported as ",*foo". So this has something to do
Hello,
Ramachandran Lakshmanan writes:
> I have been wanting to include a number of small Common Lisp snippets in
> individual files which I then include into a "master" .org file using:
>
> #+include: "snippet.org" src lisp
>
> Within snippet.org I have a src block such as:
>
[...]
> I read s
Hello,
Dave Marquardt writes:
> After I filed this I got the bright idea to try exporting to Github
> Flavored Markdown and ASCII text. In all cases, src_c{*foo} was
> exported as ",*foo". So this has something to do with export C code or
> code in general. It could still be a backend issue if t
I have been wanting to include a number of small Common Lisp snippets in
individual files which I then include into a "master" .org file using:
#+include: "snippet.org" src lisp
Within snippet.org I have a src block such as:
#+NAME: hello_test
#+BEGIN_SRC lisp :tangle yes
(defun hello () :hello)
After I filed this I got the bright idea to try exporting to Github
Flavored Markdown and ASCII text. In all cases, src_c{*foo} was
exported as ",*foo". So this has something to do with export C code or
code in general. It could still be a backend issue if these backends
share code.
-
I have been using upper-case TAGs and just noticed that
'org-agenda-show-tags' is reporting them in lower-case which is not
right since I have another TAG that is the lower-case version of the
upper-case TAG (sort of a visual importance indicator).
--
David Masterson
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.
Dear All,
thank you very much for bringing this forward and thanks to Nicholas
for his work and detailed write-up on the API! Unfortunately, I'm
extremely busy right now, but will try to comment in detail on the
coming days, most probably on Thursday. I'm very excited by the new
developments!
bes
This is my result after doing "org-sort-list a":
- /a/
- /v/
- a
- b
Regards
Nicolas Goaziou writes:
> I cannot reproduce it. With your initial list, and a minimal init file,
> I get:
>
> - /a/
> - a
> - b
> - /v/
>
> Could you try with a minimal Emacs, too?
That's weird ... I have tried launching emacs -q in a virtual machine,
and I keep getting the wrong result
See the attached files. Export works fine with html and odt, btw.
Here is the relevant node.
(info "(texinfo) Footnotes")
lists-in-footnote.texi:4: warning: @settitle missing argument
lists-in-footnote.texi:11: warning: @title missing argument
lists-in-footnote.texi:33: misplaced }
lists-in
(Resending my earlier mail. My internet connection flip-flopped while sending
the previous email.)
See the attached files. Export works fine with html and odt, btw.
Here is the relevant node.
(info "(texinfo) Footnotes")
lists-in-footnote.texi:4: warning: @settitle missing argument
lists
Hello,
"Bruce D'Arcus" writes:
> Maybe since Nicolas has been around lately, he can weigh in?
I guess I can make a summary about the current state of the citations
branch, i.e., what is done, what is missing.
There are three major steps to complete in order to add citations in
Org: defining the
Hello,
Tarjei Bærland writes:
> Something seems to go wrong during the export, however, where a new
> attachment directory is created. Is my assumption that the export will
> run with =point= at the link incorrect?
Yes, this assumption is incorrect. The export process operates on
a parse tree, a
Hi!
I am having some trouble adding a link via =org-link-set-parameters=.
I want to have a custom =xournalpp=-link type that behaves as follows:
- follow :: Open attached file
- exists :: open the file
- don't exist :: create attachment directory and copy template file into it
- export :: Use
20 matches
Mail list logo
