From: Aaron Ecay <aaronecay@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>,
Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: small caps
Date: Thu, 29 Oct 2015 17:25:49 +0000 [thread overview]
Message-ID: <87a8r1y4bm.fsf@gmail.com> (raw)
In-Reply-To: <87si4toc4g.fsf@nicolasgoaziou.fr>
Hi Nicolas,
2015ko urriak 29an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Matt Price <moptop99@gmail.com> writes:
>
>> do we have a syntax for the "small caps" text attribute in Org?
>
> No, we don't.
>
>> If not, should we?
>
> We cannot have a syntax for everything. A macro can probably replace
> missing syntax.
This is true. But small-caps are meaningful in a variety of contexts,
and they are not a truly new syntax (requiring extra code in the parser),
but rather can be handled exactly as the other emphasis markers. (They
would require support from the exporters of course.)
There’s also no rush. Maybe we could revisit the question of adding
small caps after the emphasis changes you indicated in the roadmap
thread are decided on. Those might change the cost:benefit evaluation
for adding this feature.
(FWIW, I’d be in favor of the addition unless some major new consideration
is introduced by the emphasis changes. A good proportion of the documents
I write in Org use small caps somehow. It would be good to know for how
many other users that is the case.)
--
Aaron Ecay
next prev parent reply other threads:[~2015-10-29 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 16:39 small caps Matt Price
2015-10-29 16:47 ` Nicolas Goaziou
2015-10-29 16:55 ` Thomas S. Dye
2015-10-29 20:17 ` Matt Price
2015-10-29 20:42 ` Thomas S. Dye
2015-10-30 13:10 ` Christian Moe
2015-10-31 16:16 ` Matt Price
2015-10-29 17:25 ` Aaron Ecay [this message]
2015-10-29 17:39 ` Thomas S. Dye
2015-10-29 17:46 ` Nicolas Goaziou
2015-10-29 17:44 ` Nicolas Goaziou
2015-10-29 20:37 ` Rasmus
2015-10-29 21:18 ` Robert Klein
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=87a8r1y4bm.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=moptop99@gmail.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).