emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rodrigo Morales <moralesrodrigo1100@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [Q] Is there a convention for the formatting of messages in this mailing list?
Date: Fri, 24 Sep 2021 18:31:17 -0500	[thread overview]
Message-ID: <874ka9sg8q.fsf@gmail.com> (raw)

Let's suppose I want to create a thread in the mailing list that
contains different sections, code blocks and some quotes. I used to use
Org Mode for the format in my messages, but I just read a discussion
where someone mentioned that getting the Org Mode and Org Babel syntax
in the mailing list is annoying.

Because of this, I had some questions

1. Is there some kind of convention for the formatting of the messages
   in this mailing list?
2. If that's not the case, which one should I use (Org Mode, the
   built-in ASCII exporter, Markdown, HTML)?

             reply	other threads:[~2021-09-24 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24 23:31 Rodrigo Morales [this message]
2021-09-25  3:03 ` [Q] Is there a convention for the formatting of messages in this mailing list? Jonathan McHugh
2021-09-25  4:43 ` Timothy

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874ka9sg8q.fsf@gmail.com \
    --to=moralesrodrigo1100@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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.
Code repositories for project(s) associated with this public inbox


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).