emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Slight misbehaviour with `C-x r t' in Org
Date: Fri, 17 Jan 2014 20:25:07 -0500	[thread overview]
Message-ID: <87txd29j4c.fsf@iro.umontreal.ca> (raw)

Hi, Org people.

I hope you're all doing fine, and wish you much enjoy this new year! :-)

Let me report a little strange behaviour I observed a few times.  Here
is the textual content of an Org file:

--8<---------------cut here---------------start------------->8---
* Trying
a
=b=
*c*
/d/
--8<---------------cut here---------------end--------------->8---

It is displayed like this, with org-hide-emphasis-markers to nil:

,----
| * Trying         blue
|   a              normal
|   =b=            grey
|   *c*            bold
|   /d/            italics
`----

But, as I keep org-hide-emphasis-markers to t, what I see is:

,----
| * Trying         blue
|   a              normal
|   b              grey
|   c              bold
|   d              italics
`----

Now, in this mode, if I put the mark on the `a' letter and the point on
the `d' letter, and type `C-x r t SPC SPC RET', I then see:

,----
| * Trying         blue
|     a            normal
|   =  b=          normal
| *  c*            blue
|   /  d/          normal
`----

So, the spaces are inserted after the opening marker, while I would have
expected to see them inserted before it.  My actual examples are of
course bigger than the toy example above, but even then, this is easily
corrected with some light edition.  But yet, I find it inconvenient
having to always revise text after shifting it (I often use `C-x r t'),
in case of inline markup randomly happening at the beginning of a line.

François

next             reply	other threads:[~2014-01-18  1:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-18  1:25 François Pinard [this message]
2014-01-19 16:26 ` Slight misbehaviour with `C-x r t' in Org Bastien

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=87txd29j4c.fsf@iro.umontreal.ca \
    --to=pinard@iro.umontreal.ca \
    --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

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).