unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenta USAMI <zonuexe@zonu.me>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 73991@debbugs.gnu.org
Subject: bug#73991: EditorConfig bundled with Emacs 30 does not set tab-width
Date: Sun, 27 Oct 2024 01:20:13 +0900	[thread overview]
Message-ID: <CAJB2i6Y8FfiEW45+YtK2jgcK1bDtR6LwEZ2jBk_5a_AHzdhSzQ@mail.gmail.com> (raw)
In-Reply-To: <jwvsesisxs6.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

I agree with your point, but since EditorConfig is meant for editor
interoperability,
it would be more productive to discuss this with other text editor
developers on
the EditorConfig mailing list than with Emacs editorconfig-mode users.

I think that bundling a built-in EditorConfig in Emacs will help many Emacs
users
and potential Emacs beginners. I'm very grateful for your work.

2024年10月27日(日) 0:21 Stefan Monnier <monnier@iro.umontreal.ca>:

> >>> You can get the same behavior with
> >>>
> >>>    indent_size = tab
> >>>    tab_width = 4
> >>
> >> The settings mean the same thing,
> >
> > Do they?  If so, why prefer the above formulation?
>
> The weird thing about this insistence that indent_size == tab_width and
> that exclusively TAB chars should be used for indentation, is that the
> whole point of that style of indentation is that it looks correct
> regardless of `tab-width`, making the `tab-width` into a user-preference
> that does not need to be enforced in the coding convention (and thus
> shouldn't be set by `.editorconfig`).
>
> In clear, I think the `.editorconfig` file should say just
>
>     indent_size = tab
>
> and then every user would set tab-width to the value they like in their
> favorite editor's personal settings.
>
> Anyway, I pushed the last patch, combined with the previous one, to
> `emacs-30`, which I believe should fix the problem you reported.
>
>
>         Stefan
>
>

[-- Attachment #2: Type: text/html, Size: 1898 bytes --]

  reply	other threads:[~2024-10-26 16:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 17:49 bug#73991: EditorConfig bundled with Emacs 30 does not set tab-width Kenta USAMI
2024-10-24 18:05 ` Eli Zaretskii
2024-10-24 19:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-25  3:44   ` Kenta USAMI
2024-10-25  7:37     ` Eli Zaretskii
2024-10-25  9:07       ` Kenta USAMI
2024-10-25 10:18         ` Eli Zaretskii
2024-10-25 10:49           ` Kenta USAMI
2024-10-25 17:27         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-25 17:25     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-26 15:20       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-26 16:20         ` Kenta USAMI [this message]
2024-10-25  6:18   ` 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=CAJB2i6Y8FfiEW45+YtK2jgcK1bDtR6LwEZ2jBk_5a_AHzdhSzQ@mail.gmail.com \
    --to=zonuexe@zonu.me \
    --cc=73991@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).