all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alessio Vanni <vannilla@firemail.cc>
To: 43007@debbugs.gnu.org
Subject: bug#43007: 27.1; M-j doesn't behave properly in comments
Date: Mon, 24 Aug 2020 13:47:00 +0200	[thread overview]
Message-ID: <878se4xo3v.fsf@firemail.cc> (raw)
In-Reply-To: <87imd8es7j.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 24 Aug 2020 03:41:04 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> This happens for me, too, if I have point behind the "//" characters.
> But that seems like a natural behaviour?

When the point is at the end of the line, as it's normal after writing
something, the new line is still being opened above.

I should add that after testing it some more after sending the bug
report, it managed to create a new line above a paragraph that was
disconnected to the one I was currently editing, like so (the |
character is the point):

// Paragraph one.
// With some other lines.

normal(text);

// Another paragraph
// begins here.|

Which became:

// |
// Paragraph one.
// With some other lines.

normal(text);

// Another paragraph
// begins here.

> I'm unable to reproduce this in Emacs 28.  Where is point when you hit M-j?

The point is always in the spot placed by M-j.  In the case of //, it's
after the space (so 3 characters after the beginning of the line), in
case of *, it's right after the star without any spaces.  The first time
I press the keybinding the point is at the end of the line, as shown in
the example above.

This is happening consistently, both in my customized session and with
emacs -Q.  The end result is relatively random and sometimes it doesn't
break immediately, but it happens eventually after a while that I'm
editing a file.





  reply	other threads:[~2020-08-24 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 21:53 bug#43007: 27.1; M-j doesn't behave properly in comments Alessio Vanni
2020-08-24  1:41 ` Lars Ingebrigtsen
2020-08-24 11:47   ` Alessio Vanni [this message]
2021-07-31 13:12     ` Lars Ingebrigtsen
2021-07-31 19:19       ` Alessio Vanni
2021-08-01 10:24         ` Lars Ingebrigtsen
2021-08-29 20:21           ` Lars Ingebrigtsen
2020-11-23 17:23 ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878se4xo3v.fsf@firemail.cc \
    --to=vannilla@firemail.cc \
    --cc=43007@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.