From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: jcs090218@gmail.com, bjorn.bidar@thaodan.de,
Eli Zaretskii <eliz@gnu.org>,
8slashes+git@gmail.com, 70105@debbugs.gnu.org
Subject: bug#70105: 30.0.50; Emacs should support EditorConfig out of the box
Date: Tue, 18 Jun 2024 16:07:15 -0400 [thread overview]
Message-ID: <jwvh6dq9fwa.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87jzimqb4c.fsf@localhost> (Ihor Radchenko's message of "Tue, 18 Jun 2024 19:55:31 +0000")
>>> (I also considered let-binding `tab-width' when Org parser the file, but
>>> lists will then look funny visually)
>> If you use the `tab-width` set by the user then you have the advantage
>> that you parse the code in a way that is consistent with what the users
>> see (so the problem only bites the users who don't look at their code).
> Indeed, but what if an Org file comes from another user, with different
> tab-width? Parsing it differently is simply wrong.
Exactly: there's no way to win in all cases. Which is why I think it's
important to see the real cases so we can have a better idea of the
origin of the problem and how best to mitigate it.
Stefan
next prev parent reply other threads:[~2024-06-18 20:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 13:44 bug#70105: 30.0.50; Emacs should support EditorConfig out of the box Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-31 14:25 ` Eli Zaretskii
2024-03-31 20:40 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-31 22:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-06 23:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 12:50 ` Eli Zaretskii
2024-06-09 4:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-18 6:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-18 6:21 ` Ihor Radchenko
2024-06-18 13:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-18 16:21 ` Ihor Radchenko
2024-06-18 19:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-18 19:55 ` Ihor Radchenko
2024-06-18 20:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-18 9:10 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87v826hb13.fsf@>
2024-06-18 12:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-18 19:26 ` Stefan Kangas
2024-06-18 19:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-18 23:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 5:48 ` Rudolf Schlatte
2024-06-19 6:01 ` Stefan Kangas
2024-06-19 8:18 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 15:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 15:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 16:52 ` Stefan Kangas
2024-06-19 17:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 19:31 ` Stefan Kangas
2024-06-19 19:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 20:51 ` Stefan Kangas
2024-06-21 14:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 15:52 ` Ihor Radchenko
2024-06-19 15:57 ` Eli Zaretskii
2024-06-20 16:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-09 11:49 ` Stefan Kangas
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=jwvh6dq9fwa.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=70105@debbugs.gnu.org \
--cc=8slashes+git@gmail.com \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=jcs090218@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=yantar92@posteo.net \
/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).