From: Lars Ingebrigtsen <larsi@gnus.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 47784@debbugs.gnu.org
Subject: bug#47784: 27.2: ses-header-row [PATCH INCLUDED]
Date: Thu, 06 May 2021 10:17:01 +0200 [thread overview]
Message-ID: <87im3w2s5e.fsf@gnus.org> (raw)
In-Reply-To: <20210505164034.ri6mp7gefhz64ca2@E15-2016.optimum.net> (Boruch Baum's message of "Wed, 5 May 2021 12:40:34 -0400")
Boruch Baum <boruch_baum@gmx.com> writes:
>> So I fixed that up, but I've seen that in other patches -- could you
>> have a look and see what's causing this mixture of tab and spaces?
>
> I could use a suggestion to automate that workflow: I never use tabs,
> but often find myself editing files that have them. As soon as it gets
> annoying, I remember to perform untabify on the buffer, but there's
> probably an accepted automated method to respect the tab/space
> preferences of everyone.
With the default Emacs settings, you should never end up with a space
before a tab -- have you perhaps customised what the TAB key does here?
In general, the default TAB function tries to respect the indentation
style. (But it'll never insert a space before a tab.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-06 8:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 3:31 bug#47784: 27.2: ses-header-row [PATCH INCLUDED] Boruch Baum
2021-04-17 19:30 ` Eli Zaretskii
2021-04-19 9:24 ` Boruch Baum
2021-04-19 13:03 ` Eli Zaretskii
2021-04-19 13:27 ` Boruch Baum
2021-04-21 0:02 ` Stefan Kangas
2021-04-21 9:23 ` Eli Zaretskii
2021-05-05 13:08 ` Lars Ingebrigtsen
2021-05-05 16:40 ` Boruch Baum
2021-05-05 19:15 ` Eli Zaretskii
2021-05-05 19:40 ` Boruch Baum
2021-05-05 19:46 ` Eli Zaretskii
2021-05-06 8:10 ` Robert Pluim
2021-05-06 11:05 ` Boruch Baum
2021-05-06 8:17 ` Lars Ingebrigtsen [this message]
2021-05-06 10:16 ` Boruch Baum
2021-05-07 11:14 ` Lars Ingebrigtsen
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=87im3w2s5e.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47784@debbugs.gnu.org \
--cc=boruch_baum@gmx.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).