From: Stefan Kangas <stefan@marxist.se>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: 16655@debbugs.gnu.org
Subject: bug#16655: 24.3.50; M-q on a command line does mix up commands and comments
Date: Thu, 26 Sep 2019 14:55:15 +0200 [thread overview]
Message-ID: <CADwFkmmXPWx9EPZ35+ZHV7sDTYNY9Tks=eJ-MvZSUt_C4bA_Bw@mail.gmail.com> (raw)
In-Reply-To: <86fvnxa5tf.fsf@somewhere.org>
tags 16655 + confirmed
found 16655 25.1
found 16655 26.1
quit
Marcin Borkowski <mbork@mbork.pl> writes:
> I'm writing to confirm that this is still present in GNU Emacs
> 25.1.50.1. To make it a bit more precise: the OP means M-q with point
> on either the 3rd line of the script (i.e., the line beginning with "#
> display"), which works fine, and then M-q on the fourth line (i.e., the
> line beginning with "echo"), which breaks as described below.
[...]
>> With such a shell script file:
>>
>> #!/bin/sh
>>
>> # display symbol definitions, as found in the relevant manual (for AWK, C, Emacs Lisp, and other languages that have documentation in Info)
>> echo Some text
>>
>>
>> We can observe that:
>>
>> - `M-q' done on the first line will correctly refill the comment into
>> 2 lines
>>
>> # display symbol definitions, as found in the relevant manual (for AWK, C,
>> # Emacs Lisp, and other languages that have documentation in Info)
>> echo Some text
>>
>>
>> - `M-q' done on the second line will completely break the code:
>>
>> # display symbol definitions, as found in the relevant manual (for AWK, C,
>> Emacs Lisp, and other languages that have documentation in Info) echo Some text
>>
>> See http://screencast.com/t/XGs10gmz0m2.
I can reproduce this on Emacs 26.1 and current master.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2019-09-26 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 16:21 bug#16655: 24.3.50; M-q on a command line does mix up commands and comments Sebastien Vauban
2016-02-04 21:00 ` Marcin Borkowski
2019-09-26 12:55 ` Stefan Kangas [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmmXPWx9EPZ35+ZHV7sDTYNY9Tks=eJ-MvZSUt_C4bA_Bw@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=16655@debbugs.gnu.org \
--cc=mbork@mbork.pl \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).