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: Sun, 29 Aug 2021 22:21:58 +0200	[thread overview]
Message-ID: <87tuj8c87t.fsf@gnus.org> (raw)
In-Reply-To: <874kc98nt2.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 01 Aug 2021 12:24:57 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Alessio Vanni <vannilla@firemail.cc> writes:
>
>> Unfortunately I can't really provide anything else. The file being
>> edited doesn't seem to be related and neither seem to be the major mode
>> (as long as it's for a programming language), as I had it happen in
>> different modes, some of which being shipped with Emacs (i.e. are not
>> being installed by third-party packages.)
>
> When this happens, does it happen consistently?  If that's the case, can
> you do a `C-h k M-j' to confirm that the key binding hasn't been changed
> to something else?  And also examine the value of the
> `comment-line-break-function' variable.

This was a month ago, so I'm guessing it'll be difficult to make further
progress here, and I'm closing this bug report.  If further progress can
be made, please respond to this email and we'll reopen the bug report.

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





  reply	other threads:[~2021-08-29 20:21 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
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 [this message]
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=87tuj8c87t.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.