From: Rustom Mody <rustompmody@gmail.com>
To: Rustom Mody <rustompmody@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: how to enter ==
Date: Wed, 2 Apr 2014 19:58:16 +0530 [thread overview]
Message-ID: <CAJ+TeofvPbOedYHvZzpKonMgmMJKD+76wx-MaTr-T3NRnf9GtQ@mail.gmail.com> (raw)
In-Reply-To: <87ppkzri8e.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On Wed, Apr 2, 2014 at 6:39 PM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> On Wednesday, 2 Apr 2014 at 12:08, Rustom Mody wrote:
> > On Wed, Apr 2, 2014 at 3:11 PM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> >
> >> On Tuesday, 1 Apr 2014 at 02:52, Rustom Mody wrote:
> >> > If I enter code inline that has an == that is taken as an escape for
> code
> >> > So how to enter '==' literally
> >>
> >> How about ~==~?
> >>
> >>
> > In that case the full ~==~ appears on export :-(
>
> ummm, it doesn't for me but I guess you have the == within a larger code
> segment? Maybe post an example? What version of org are you using?
>
>
Heres a file
----------
#+TITLE: Python for Unicode
#+OPTIONS: toc:nil
* Collections
However there is a catch: =⦃1,2,3⦄ ~==~ ⦃1,2,3,1,2⦄= \\
Remember that in python =set([1,2,3,1,2]) ~==~ set([1,2,3])= \\
----------
And now do C-c C-e h o
Do not the tilde's remain?
org-version: 8.2.5e
emacs started with -Q (except for putting this in the path)
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 24.3.1, Org release_8.2.5h-660-gef207f
>
--
http://www.the-magus.in
http://blog.languager.org
[-- Attachment #2: Type: text/html, Size: 2164 bytes --]
next prev parent reply other threads:[~2014-04-02 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 1:52 how to enter == Rustom Mody
2014-04-01 2:04 ` briangpowell .
2014-04-01 2:31 ` Rustom Mody
2014-04-01 3:03 ` Rustom Mody
2014-04-02 9:41 ` Eric S Fraga
2014-04-02 11:08 ` Rustom Mody
2014-04-02 13:09 ` Eric S Fraga
2014-04-02 14:28 ` Rustom Mody [this message]
2014-04-03 13:22 ` Eric S Fraga
2014-07-26 4:38 ` stardiviner
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=CAJ+TeofvPbOedYHvZzpKonMgmMJKD+76wx-MaTr-T3NRnf9GtQ@mail.gmail.com \
--to=rustompmody@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).