emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michal Politowski <mpol@meep.pl>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: c++ code block automatically adds comma [8.2.10 (release_8.2.10 @ c:/Users/Louis/home/bin/emacs-24.5/share/emacs/24.5/lisp/org/)]
Date: Mon, 23 Oct 2017 11:25:42 +0200	[thread overview]
Message-ID: <20171023092542.utt55h7qpwgjqr5m@meep.pl> (raw)
In-Reply-To: <87efpvrsxc.fsf@nicolasgoaziou.fr>

On Sun, 22 Oct 2017 19:30:55 +0200, Nicolas Goaziou wrote:
> Hello,
> 
> Louis Strous <louis@quae.nl> writes:
> 
> > When I edit a c++ code block using C-c ' and then finish the edit using
> > C-c ' again, then org-mode sometimes adds a comma to the code.
[...]
> >     Note the appearance of a comma in front of the "*".
> >
> > 7. Press "C-c '" to edit the code block again.  The code displayed in
> >     the "*Org Src *scratch*[ c++ ]*" buffer does not contain the comma:
> >
> > if (foo)
> >    *foo = 3;
> >
> > 8. Press "C-c '" to finish the editing.  The code in the *scratch*
> >     buffer still contains the comma.
> >
> > End of reproduction scenario.
> 
> See (info "(org) Literal examples"), fourth footnote

Interesting, even if not very likely to hit anyone, that lines
intentionally starting with ,,* are not escaped and thus
lose one comma on the next edit.

-- 
Michał Politowski
Talking has been known to lead to communication if practiced carelessly.

  reply	other threads:[~2017-10-23  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 11:12 Bug: c++ code block automatically adds comma [8.2.10 (release_8.2.10 @ c:/Users/Louis/home/bin/emacs-24.5/share/emacs/24.5/lisp/org/)] Louis Strous
2017-10-22 17:30 ` Nicolas Goaziou
2017-10-23  9:25   ` Michal Politowski [this message]
2017-10-23 10:15     ` Nicolas Goaziou
2017-10-23 13:00       ` Michal Politowski
2017-10-24  7:57         ` Nicolas Goaziou

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=20171023092542.utt55h7qpwgjqr5m@meep.pl \
    --to=mpol@meep.pl \
    --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).