From: Bastien Guerry <bzg@gnu.org>
To: Daniel Kraus <daniel@kraus.my>
Cc: Ihor Radchenko <yantar92@posteo.net>,
numbchild@gmail.com, emacs-orgmode@gnu.org
Subject: Re: indent-tabs-mode in org
Date: Mon, 31 Oct 2022 10:49:11 +0100 [thread overview]
Message-ID: <874jvkz5k8.fsf@bzg.fr> (raw)
In-Reply-To: <8735b68jxc.fsf@kraus.my> (Daniel Kraus's message of "Sat, 29 Oct 2022 22:13:06 +0200")
Hi Daniel and Ihor,
Daniel Kraus <daniel@kraus.my> writes:
> So that clarifies it for me and I do NOT indent with tabs in the
> future :)
We can progressively replace tab chars with spaces, thus re-indenting
correctly all files in the repository.
The Emacs convention is to *not* commit space-only changes as they may
create merge conflicts.
For files that do not have pending patches, we can do the replacement
with the next code-related change.
2 cts,
--
Bastien
prev parent reply other threads:[~2022-10-31 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 4:08 ob-clojure eval error when has comment at end of code line Christopher M. Miles
2022-10-26 7:30 ` Ihor Radchenko
2022-10-27 12:25 ` Daniel Kraus
2022-10-27 14:17 ` Max Nikulin
2022-10-28 4:05 ` Ihor Radchenko
2022-10-28 9:40 ` ob-clojure session support (was: ob-clojure eval error when has comment at end of code line) Daniel Kraus
2022-10-28 10:20 ` ob-clojure session support Bastien Guerry
2022-10-29 3:03 ` ob-clojure session support (was: ob-clojure eval error when has comment at end of code line) Ihor Radchenko
2022-10-29 8:07 ` ob-clojure session support Bastien Guerry
2022-10-30 11:33 ` ob-clojure session support (was: ob-clojure eval error when has comment at end of code line) Daniel Kraus
2022-10-30 12:45 ` Ihor Radchenko
2022-10-29 20:13 ` indent-tabs-mode in org " Daniel Kraus
2022-10-31 9:49 ` Bastien Guerry [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jvkz5k8.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=daniel@kraus.my \
--cc=emacs-orgmode@gnu.org \
--cc=numbchild@gmail.com \
--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/org-mode.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).