From: Anders Johansson <mejlaandersj@gmail.com>
To: emacs-orgmode@gnu.org
Subject: org-entities: why \lang instead of \langle?
Date: Sun, 23 Feb 2014 10:36:41 +0100 [thread overview]
Message-ID: <5309C129.3030309@gmail.com> (raw)
Hi,
I noticed that in org-entities these symbols are defined:
("lang" "\\langle" t "⟨" "<" "<" "⟨")
("rang" "\\rangle" t "⟩" ">" ">" "⟩")
But nothing for "langle" and "rangle". I guess it seems pretty confusing
when you try to use the latex-macros you are used to.
Maybe these aliases could also be added, like what is done for e.g. "clubs":
("langle" "\\langle" t "⟨" "<" "<" "⟨")
("rangle" "\\rangle" t "⟩" ">" ">" "⟩")
Cheers,
Anders Johansson
next reply other threads:[~2014-02-23 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 9:36 Anders Johansson [this message]
2014-03-13 15:46 ` org-entities: why \lang instead of \langle? Bastien
2014-03-25 13:45 ` org-entities: Another issue [was: org-entities: why \lang instead of \langle?] Anders Johansson
2014-03-25 14:02 ` Aaron Ecay
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=5309C129.3030309@gmail.com \
--to=mejlaandersj@gmail.com \
--cc=emacs-orgmode@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/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).