From: Richard Stallman <rms@gnu.org>
To: Christian <cnngimenez@disroot.org>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: SachaC-news
Date: Sat, 30 Dec 2023 22:13:34 -0500 [thread overview]
Message-ID: <E1rJmGc-0008PF-5L@fencepost.gnu.org> (raw)
In-Reply-To: <877cmereoa.wl-cnngimenez@disroot.org> (message from Christian on Sat, 18 Nov 2023 17:26:29 -0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
Please forgive me for taking so long to see your reply.
> Mmm... I suppose... I can add a customization to show an
> exported buffer instead the Org-mode buffer. For example, if
> sachac-news-show-plain-text is set to t, it will do the
> overall process, but add an extra step to export the Org file
> into plain text... or even generalize this idea to use any
> export dispatch function... I believe it can be
> implemented... what do you think?
That is a good approach, but one detail should be different.
The variable should be sachac-news-show-org, and default to nil.
Org format is text with its own kind of markup -- it is not plain text.
The point is that, in designing other parts of Emacs, we should not
treat Org format as if it were a standard. Org is an extension
package in Emacs; some people use it, and some don't.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2023-12-31 3:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 19:32 [ELPA] New package: SachaC-news Christian
2023-11-14 2:56 ` Richard Stallman
2023-11-15 23:56 ` Björn Bidar
2023-11-14 2:56 ` Richard Stallman
2023-11-18 20:26 ` Christian
2023-11-21 16:07 ` Sacha Chua
2023-11-25 22:40 ` Christian
2023-12-31 3:13 ` Richard Stallman [this message]
2023-12-31 18:13 ` Adam Porter
2023-12-31 19:32 ` Eli Zaretskii
2023-12-31 21:36 ` Adam Porter
2023-12-31 22:33 ` Christopher Dimech
2023-12-31 22:57 ` Emanuel Berg
2024-01-01 12:01 ` Eli Zaretskii
2024-01-02 3:19 ` Richard Stallman
2024-01-02 5:08 ` Emanuel Berg
2024-01-04 4:01 ` Richard Stallman
2024-01-02 18:05 ` Christian
2024-01-02 0:04 ` Stefan Kangas
2024-01-05 4:23 ` Richard Stallman
2024-01-02 17:40 ` Christian Gimenez
2023-11-17 7:28 ` Philip Kaludercic
2023-11-18 20:30 ` Christian
2023-11-18 21:10 ` Philip Kaludercic
2023-11-25 22:07 ` Christian
2023-11-25 22:50 ` Philip Kaludercic
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=E1rJmGc-0008PF-5L@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=cnngimenez@disroot.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).