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

Alessio Vanni <vannilla@firemail.cc> writes:

> I normally use M-j to continue a long comment over multiple lines.
> Recently, this feature broke in a rather weird way: new lines are opened
> as a comment, but the new line is placed above the line with the point,
> rather than below.  In some other cases, the line appears in the correct
> place, but opening a new line results in a '*' character instead of a
> comment (the character is used on modes where '*' is part of a comment,
> like `js-mode' or `cc-mode'.)
>
> This happens when running "emacs -Q" too.
>
> Example:
>
> // some comment.
>
> Becomes:
>
> //
> // some comment.

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

> Alternatively:
>
> // some comment.
> //
> //
>   *
>   *
>   *
>   *
>
> (the '*' just keeps happening for every M-j.)

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

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-08-24  1:41 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 [this message]
2020-08-24 11:47   ` Alessio Vanni
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=87imd8es7j.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=43007@debbugs.gnu.org \
    --cc=vannilla@firemail.cc \
    /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.