[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Docstrings and literate programming (good practices?)
From: |
Dr. Arne Babenhauserheide |
Subject: |
Re: Docstrings and literate programming (good practices?) |
Date: |
Wed, 02 Nov 2022 08:53:48 +0100 |
User-agent: |
mu4e 1.8.11; emacs 28.1 |
Ihor Radchenko <yantar92@posteo.net> writes:
> Juan Manuel Macías <maciaschain@posteo.net> writes:
>
>> #+NAME: docstring1
>> #+begin_src org :post format-docstring(*this*) :results replace :exports
>> results :tangle no
>> Lorem ipsum dolor sit amet.
>>
>> Consectetuer adipiscing elit. "Donec hendrerit tempor tellus". Donec
>> pretium posuere
>> tellus. Proin quam nisl, tincidunt et, mattis eget, convallis nec, purus.
>> Cum sociis
>> natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.
>> #+end_src
>
> You can also have
>
> #+name: docstring1
> : Lorem ipsum dolor sit amet.
>
> :
> : Consectetuer adipiscing elit. "Donec hendrerit tempor tellus". Donec
> pretium posuere
> : tellus. Proin quam nisl, tincidunt et, mattis eget, convallis nec, purus.
> Cum sociis
> : natoque penatibus et magnis dis parturient montes, nascetur ridiculus
> mus.
>
>> #+begin_src emacs-lisp :noweb strip-export :exports code
>> (defun foo ()
>> <<docstring1()>>
>> (message "hello world"))
>> #+end_src
Both of these options look awesome! Thank you for sharing!
The first (org-block) for long-form text (like official javadoc), the
second (just verbatim) for shorter docstrings.
They finally solve a long-standing problem for me.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
signature.asc
Description: PGP signature
Re: Docstrings and literate programming (good practices?), Rudolf Adamkovič, 2022/11/03