From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: Org to Markdown programmatically
Date: Thu, 6 May 2021 00:14:48 +0300 [thread overview]
Message-ID: <YJMKyLOcG35rGdES@protected.localdomain> (raw)
In-Reply-To: <878s4s7va9.fsf@zoho.eu>
* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2021-05-05 23:58]:
> > `while' is giving me more clarity.
>
> When you grow custom to other, better methods they are
> actually much clearer to you, and everyone else.
Phenomena is that that my subjective viewpoint changed. I did not know
Emacs Lisp, I knew only Common Lisp and used all kinds of loops. And
now it changed.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/
https://rms-support-letter.github.io/
next prev parent reply other threads:[~2021-05-05 21:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 8:48 Org to Markdown programmatically Jean Louis
2021-05-04 9:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-04 10:09 ` Colin Baxter
2021-05-04 17:29 ` Jean Louis
2021-05-04 20:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 6:56 ` Jean Louis
2021-05-05 7:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 8:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 11:58 ` Jean Louis
2021-05-05 15:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 19:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 20:41 ` Jean Louis
2021-05-05 20:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 21:14 ` Jean Louis [this message]
2021-05-05 20:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-05 21:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 21:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 21:46 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-05 22:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 23:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 23:54 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-05 21:50 ` Jean Louis
2021-05-05 21:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 22:56 ` Jean Louis
2021-05-05 23:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 20:11 ` Jean Louis
2021-05-05 20:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 20:54 ` Jean Louis
2021-05-05 21:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 21:33 ` Jean Louis
2021-05-05 21:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 22:51 ` Jean Louis
2021-05-05 23:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-06 3:46 ` Jean Louis
2021-05-22 8:26 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YJMKyLOcG35rGdES@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).