From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: [Patch] ob-tangle.el: New value 'ascii' for the header argument ':comments'
Date: Mon, 13 Jun 2022 10:22:55 +0000 [thread overview]
Message-ID: <87k09ksw00.fsf@posteo.net> (raw)
In-Reply-To: <m2r13tx97j.fsf@me.com> ("Rudolf Adamkovič"'s message of "Mon, 13 Jun 2022 10:24:00 +0200")
Hi, Rudolph,
Rudolf Adamkovič writes:
> Oh, I see. Thank you for the explanation. I can see myself using such
> new tangle comments all the time! But then, I use UTF-8 and not the
> standard 7-bit ASCII for my Org documents. Hence, I would want to see
> ':comments plain' or ':comments plain-text' instead.
What you comment makes sense, because `ascii' can lead to confusion. I
chose the term `ascii' because the backend used to convert the text is
called `ascii', although if I evaluate something like
(org-export-string-as "αβγδ" 'ascii t)
the result is utf8.
I think it might be a good idea to use `plain' for the value name, as
you say, instead of `ascii'...
Best regards,
Juan Manuel
prev parent reply other threads:[~2022-06-13 10:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 18:28 [Patch] ob-tangle.el: New value 'ascii' for the header argument ':comments' Juan Manuel Macías
2022-06-11 5:39 ` Ihor Radchenko
2022-06-11 11:20 ` Juan Manuel Macías
2022-06-14 3:58 ` Ihor Radchenko
2022-06-14 11:11 ` Juan Manuel Macías
2022-06-14 11:55 ` Ihor Radchenko
2022-06-15 10:30 ` Juan Manuel Macías
2022-07-21 13:44 ` Juan Manuel Macías
2022-07-25 13:34 ` Ihor Radchenko
2022-07-25 17:13 ` Juan Manuel Macías
2022-07-26 5:35 ` Ihor Radchenko
2022-06-12 19:18 ` Rudolf Adamkovič
2022-06-12 19:55 ` Juan Manuel Macías
2022-06-13 8:24 ` Rudolf Adamkovič
2022-06-13 10:22 ` Juan Manuel Macías [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k09ksw00.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=salutis@me.com \
/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/org-mode.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).