GNU bug report logs - #70105
30.0.50; Emacs should support EditorConfig out of the box

Previous Next

Full log

Message #83 received at 70105 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: jcs090218 <at> gmail.com, bjorn.bidar <at> thaodan.de, 8slashes+git <at> gmail.com,
 70105 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca
Subject: Re: bug#70105: 30.0.50; Emacs should support EditorConfig out of
 the box
Date: Wed, 19 Jun 2024 18:57:43 +0300

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: Eli Zaretskii <eliz <at> gnu.org>, jcs090218 <at> gmail.com,
>  bjorn.bidar <at> thaodan.de, 8slashes+git <at> gmail.com, 70105 <at> debbugs.gnu.org
> Date: Wed, 19 Jun 2024 15:52:29 +0000
> 
> Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
> text editors" <bug-gnu-emacs <at> gnu.org> writes:
> 
> > +The @code{indent_size} setting of the EditorConfig standard does not
> > +correspond to a fixed variable in Emacs, but instead needs to set
> > +different variables depending on the major mode.  Ideally all major
> > +modes should set the corresponding @code{editorconfig-indent-size-vars},
> > +but if you use a major mode in which @code{indent_size} does not take
> > +effect because the major mode does not yet support it, you can customize
> > +the @code{editorconfig-indentation-alist} variable to tell Emacs which
> > +variables need to be set in that major mode.
> 
> Reading this as a major mode maintainer, I have not the slightest clue
> about EditorConfig standard. So, I have no idea what indent_size is all
> about and what I am supposed to do with it.

This is from the Emacs user manual, not from the ELisp reference
manual.  So the intended audience is users, and in particular those
who have .editorconfig files and thus already know about indent_size.

Guidance and recommendations for mode developers are of course also
needed, but they will go into the other manual, and (AFIU) we don't
yet fully know what to write there, because this is still a moving
target.  When we figure that out, it would be good to document the
conventions and recommended practices.  But we are not there yet.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.