emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: yoctocell <public@yoctocell.xyz>
To: emacs-orgmode@gnu.org
Subject: Bug: Unexpected movement of cursor when commenting code blocks
Date: Wed, 13 Jan 2021 13:36:50 +0100	[thread overview]
Message-ID: <874kjlm2sd.fsf@elephant.i-did-not-set--mail-host-address--so-tickle-me> (raw)

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See


Your bug report will be posted to the Org mailing list.
When I am inside a code block like this:

#+begin_src emacs-lisp
(use-package org
  (setq blahblah t)) ; cursor on this line

and I hit "C-x C-;" to comment the line, the cursor automatically jumps
to the second line of the code block after the comment is made.  I would
expect the cursor to move forward one line like it usually does and this
only happens in Org-mode, not when I edit the code block in a separate
buffer with "C-c C-'".

#+begin_src emacs-lisp
(use-package org
  :defer ; cursor jumps to this line
  ;; (setq blahblah t))

This happens no matter how big the code block is, and it always jumps to
the second line of the code block.  I was able to reproduce this with
the "minimal-org.el" file.

Emacs  : GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.23, cairo version 1.16.0)
Package: Org mode version 9.4.4 (9.4.4-3-gbd1c31-elpaplus @ /nix/store/ybfrs7h4byc03f963flgc845n3m1dkhi-emacs-packages-deps/share/emacs/site-lisp/elpa/org-plus-contrib-20201228/)

             reply	other threads:[~2021-01-14 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 12:36 yoctocell [this message]
2021-01-15 18:48 ` Bug: Unexpected movement of cursor when commenting code blocks Sébastien Miquel
2021-01-15 20:27   ` yoctocell

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:

  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=874kjlm2sd.fsf@elephant.i-did-not-set--mail-host-address--so-tickle-me \
    --to=public@yoctocell.xyz \
    --cc=emacs-orgmode@gnu.org \


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