unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: damien@cassou.me, 72808@debbugs.gnu.org, jaygkamat@gmail.com,
	stefankangas@gmail.com, 8.slashes@gmail.com
Subject: bug#72808: 30.0.90; editorconfig doesn't set tab_width to a default value
Date: Fri, 01 Nov 2024 09:37:22 +0200	[thread overview]
Message-ID: <86jzdn1k25.fsf@gnu.org> (raw)
In-Reply-To: <jwvplnffzpd.fsf-monnier+emacs@gnu.org> (bug-gnu-emacs@gnu.org)

> Cc: Damien Cassou <damien@cassou.me>, 72808@debbugs.gnu.org,
>  jaygkamat@gmail.com, 8.slashes@gmail.com
> Date: Thu, 31 Oct 2024 22:42:31 -0400
> From:  Stefan Monnier via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Note that in response to the very similar request in bug#73991 (where
> I also point out more reasons why I think the EditorConfig spec is just
> poorly thought out in this respect), I (reluctantly🙂) installed in
> `emacs-30` a patch which should make Emacs behave like Damien expects
> for the `.editorconfig` file he provided.

Indeed.  Moreover, people who claim that we must behave like other
editors should also explain how to reconcile that with the fact that
Emacs has a much more complex handling of tab-width wrt indentation,
and in particular we almost completely decoupled these two.  It is
IMNSHO unthinkable that support of EditorConfig will change how Emacs
handles tabs and indentation in its various major modes.

So saying that we should comply is not enough, because everyone here
is in favor of compliance.  The problem, and the reason why Stefan
didn't comply 100% with that single setting, is that there are
significant conceptual problems with providing such compliance without
breaking expectations of Emacs users.  Thus, if you think what we have
is insufficient, please tell how to be more compatible without
breaking traditional Emacs behaviors wrt to tabs and indentation.
Because we cannot possibly allow that tail to wag the dog, can we?





  reply	other threads:[~2024-11-01  7:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pmg-aquar-1261481-87le0mrqpn.fsf@cassou.me>
2024-08-25 19:25 ` bug#72808: 30.0.90; editorconfig doesn't set tab_width to a default value Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-25 20:23   ` Damien Cassou
2024-09-07  7:27     ` Eli Zaretskii
2024-09-08 11:25       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-21  9:07         ` Eli Zaretskii
2024-11-01  2:09     ` Stefan Kangas
2024-11-01  2:42       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-01  7:37         ` Eli Zaretskii [this message]
2024-11-01 10:51           ` Damien Cassou

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=86jzdn1k25.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72808@debbugs.gnu.org \
    --cc=8.slashes@gmail.com \
    --cc=damien@cassou.me \
    --cc=jaygkamat@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefankangas@gmail.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 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).