From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61268@debbugs.gnu.org, dick <dick.r.chiang@gmail.com>
Subject: bug#61268: 30.0.50; [PATCH] Deprecate called-interactively-p
Date: Sun, 05 Feb 2023 17:57:19 +0800 [thread overview]
Message-ID: <87h6w08mf4.fsf@yahoo.com> (raw)
In-Reply-To: <83mt5ssc6e.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 05 Feb 2023 11:18:17 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: luangruo@yahoo.com
>> From: dick <dick.r.chiang@gmail.com>
>> Date: Sat, 04 Feb 2023 14:03:21 -0500
>>
>> For an individual notorious for mangling interfaces
>> (window-text-pixel-size, set-window-vscroll), why continue
>> to support a method that *reduces* such mangling?
>>
>> git log -p --since="2021-10-01" --author luangruo -- | perl -ne 'chomp; $line = $_;
>> if ($line =~ /^[ -]((DEFUN\s\()|[a-z]\S+\s\()/) {
>> $prim = 1 if $2;
>> $new = "";
>> substr($line,0,1) = "-";
>> $old = "$line\n";
>> } elsif ($old && $line =~ /^[-]/) {
>> $old .= "$line\n" if $line =~ /[(),]/;
>> } elsif ($old && $line =~ /^\+/) {
>> $new .= "$line\n" if $line =~ /[(),]/;
>> if (!$prim && $new =~ /\)\s*$/ ||
>> $prim && $new =~ /\d,\s*\d,\s*\d/) {
>> print $old;
>> print $new;
>> $prim = $old = $new = "";
>> }
>> } else {
>> $prim = $old = $new = "";
>> }'
>
> Is this a bug report? If so, what is the bug, and how to reproduce
> it?
It is a bad attempt at making a personal insult. The next time he comes
back, I suggest replying with the word:
*plonk*
prev parent reply other threads:[~2023-02-05 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 17:19 bug#61268: 30.0.50; [PATCH] Deprecate called-interactively-p dick.r.chiang
2023-02-04 8:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-04 19:03 ` dick
2023-02-05 9:18 ` Eli Zaretskii
2023-02-05 9:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6w08mf4.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=61268@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
/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.