unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: contovob@tcd.ie, 40725@debbugs.gnu.org, juri@linkov.net
Subject: bug#40725: 27.0.91; Tutorial reports false positive key rebindings
Date: Fri, 24 Apr 2020 15:13:50 +0300	[thread overview]
Message-ID: <83v9lp9j41.fsf@gnu.org> (raw)
In-Reply-To: <37969D02-FD67-4563-BD01-A2F483999D79@acm.org> (message from Mattias Engdegård on Fri, 24 Apr 2020 13:35:52 +0200)

> From: Mattias Engdegård <mattiase@acm.org>
> Date: Fri, 24 Apr 2020 13:35:52 +0200
> Cc: juri@linkov.net, contovob@tcd.ie, 40725@debbugs.gnu.org
> 
> 24 apr. 2020 kl. 13.21 skrev Eli Zaretskii <eliz@gnu.org>:
> 
> > Like I said: I would prefer not to rename files at all, if we can
> > solve the mode issue in some other way.
> 
> I agree, let's not rename files without a good reason. Here we have multiple good reasons.

I didn't say "a good reason", I said "if we can solve the issue in
some other way".

> The file names cause more inconvenience than just the mode problem.

What problems are those?  You mentioned grepping the files, which can
be easily handled by excluding the tutorials directory from the
search.  Are there any other problems we should consider?

> Git handles renames gracefully.

"Gracefully" is in the eyes of the beholder.  It's true the support
for renames improved in the recent years, but there are still commands
that either fails or need special invocation methods to work across
renames.  So it's still a source of inconvenience and occasional
failure or mistaken conclusions, and I'd like to avoid that if
possible.





  reply	other threads:[~2020-04-24 12:13 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 [this message]
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

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=83v9lp9j41.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=40725@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --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).