From: "Topi Mäenpää" <firstname.lastname@example.org>
To: Eric S Fraga <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>
Subject: Re: Bug report
Date: Thu, 02 Jun 2022 15:30:43 +0000 [thread overview]
Message-ID: <JHyMYuKMcqac89ptA4V8eTtX_ix0XxqJGYEWnslE-qfG1cCMTq1uo6aekXZVQQHhKlQq2JKuR7WvNU3_1QhGCs4ZTDTmvREOcvf_PQdE8Q8firstname.lastname@example.org> (raw)
Looks like I was trying to be too clever. :)
I used org-mode to write the bug report. The problem isn't that the formatting fails in source code blocks. I put it in one so that it would appear verbatim. If you copy the contents of the block into a normal paragraph, you should be able to see the problem.
I'm running Emacs 29.0.50 (from git) and org 9.5.3.
Sent with Proton Mail secure email.
------- Original Message -------
On Wednesday, June 1st, 2022 at 6:37 PM, Eric S Fraga <email@example.com> wrote:
> On Wednesday, 1 Jun 2022 at 07:53, Topi Mäenpää wrote:
> > I have trouble escaping a dollar sign in org-mode documents. I
> > tried to enter the following:
> > #+begin_src
> > A (14 G$) B (6 G$)
> > #+end_src
> I have no problem with this. What version of org are you using?
> Out of curiosity, what language is this? I ask because #+begin_src
> expects a language argument normally. Otherwise, I would use an example
> block, e.g.:
> A (14 G$) B (6 G$)
> which may also help with your problem.
> : Eric S Fraga, with org release_9.5.3-520-g4dda0d in Emacs 29.0.50
next prev parent reply other threads:[~2022-06-02 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 7:53 Bug report Topi Mäenpää
2022-06-01 15:37 ` Eric S Fraga
2022-06-01 16:24 ` Max Nikulin
2022-06-01 16:49 ` Eric S Fraga
2022-06-02 15:30 ` Topi Mäenpää [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-01 7:02 Dan
2016-06-01 17:45 ` Nicolas Goaziou
2009-10-06 9:12 Otto Pichlhoefer
2009-10-07 6:17 ` Carsten Dominik
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).