From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: contovob@tcd.ie, mattiase@acm.org, 40725@debbugs.gnu.org,
juri@linkov.net
Subject: bug#40725: 27.0.91; Tutorial reports false positive key rebindings
Date: Fri, 24 Apr 2020 18:51:22 +0300 [thread overview]
Message-ID: <83imhoanlx.fsf@gnu.org> (raw)
In-Reply-To: <5d826e4e-bcaf-6d08-7bc9-5c0875db2dfb@yandex.ru> (message from Dmitry Gutov on Fri, 24 Apr 2020 18:38:29 +0300)
> Cc: contovob@tcd.ie, 40725@debbugs.gnu.org, juri@linkov.net
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Fri, 24 Apr 2020 18:38:29 +0300
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39044
>
> It's not insurmountable, of course (I expect we'll fix it for Emacs 28).
> But let's not ignore the problems either.
The problems aren't insurmountable, sure. They just add
complications. In most cases, if you are aware a rename was made, you
can tweak the VCS commands to handle that. But (a) you need to be
aware, and that is not always obvious; and (b) how to tweak the
commands is also not always obvious. If you fail to notice and/or
fail to tweak the command as required, you might very well see
incorrect information and make the wrong decisions. It happened to me
several times, so I'd rather we avoided that if possible.
prev parent reply other threads:[~2020-04-24 15:51 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 23:31 bug#40725: 27.0.91; Tutorial reports false positive key rebindings Basil L. Contovounesios
2020-04-20 14:28 ` Eli Zaretskii
2020-04-20 22:19 ` Basil L. Contovounesios
2020-04-21 13:39 ` Eli Zaretskii
2020-04-22 22:26 ` Basil L. Contovounesios
2020-04-23 14:33 ` Eli Zaretskii
2020-04-23 21:52 ` Juri Linkov
2020-04-24 6:55 ` Eli Zaretskii
2020-04-25 3:31 ` Richard Stallman
2020-04-25 8:54 ` Eli Zaretskii
2020-04-25 20:42 ` Juri Linkov
2020-08-18 13:54 ` Lars Ingebrigtsen
2020-08-18 18:52 ` Basil L. Contovounesios
2020-08-19 10:20 ` Lars Ingebrigtsen
2021-11-12 8:28 ` Lars Ingebrigtsen
2021-11-14 23:24 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-15 5:53 ` Lars Ingebrigtsen
2020-04-24 8:46 ` Mattias Engdegård
2020-04-24 10:20 ` Eli Zaretskii
2020-04-24 10:41 ` Mattias Engdegård
2020-04-24 11:21 ` Eli Zaretskii
2020-04-24 11:35 ` Mattias Engdegård
2020-04-24 12:13 ` Eli Zaretskii
2020-04-24 12:47 ` Mattias Engdegård
2020-04-24 13:32 ` Eli Zaretskii
2020-04-24 16:01 ` Mattias Engdegård
2020-04-25 3:33 ` Richard Stallman
2020-04-25 6:20 ` Eli Zaretskii
2020-04-27 2:18 ` Richard Stallman
2020-04-27 2:37 ` Eli Zaretskii
2020-04-27 6:11 ` Andreas Schwab
2020-04-28 2:49 ` Richard Stallman
2020-04-28 7:02 ` Andreas Schwab
2020-04-29 3:25 ` Richard Stallman
2020-04-29 7:30 ` Eli Zaretskii
2020-04-30 2:32 ` Richard Stallman
2020-04-24 19:48 ` Kévin Le Gouguec
2020-04-24 19:57 ` Eli Zaretskii
2020-04-24 15:38 ` Dmitry Gutov
2020-04-24 15:51 ` Eli Zaretskii [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=83imhoanlx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40725@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=dgutov@yandex.ru \
--cc=juri@linkov.net \
--cc=mattiase@acm.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 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).