From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: linux-kbuild@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"John (Warthog9) Hawley" <warthog9@kernel.org>
Subject: [PATCH 0/2] streamline_config.pl: Fix Perl spacing
Date: Mon, 22 Mar 2021 17:38:06 -0400 [thread overview]
Message-ID: <20210322213806.089334551@goodmis.org> (raw)
Talking with John Hawley about how vim and emacs deal with Perl files
with respect to tabs and spaces, I found that some of my Perl code in
the kernel had inconsistent spacing. The way emacs handles Perl by default
is to use 4 spaces per indent, but make all 8 spaces into a single tab.
Vim does not do this by default. But if you add the vim variable control:
# vim: softtabstop=4
to a perl file, it makes vim behave the same way as emacs.
The first patch is to change all 8 spaces into a single tab (mostly from
people editing the file with vim). The next patch adds the softtabstop
variable to make vim act like emacs by default.
Steven Rostedt (VMware) (2):
streamline_config.pl: Make spacing consistent
streamline_config.pl: Add softtabstop=4 for vim users
----
scripts/kconfig/streamline_config.pl | 80 ++++++++++++++++++------------------
1 file changed, 41 insertions(+), 39 deletions(-)
next reply other threads:[~2021-03-22 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 21:38 Steven Rostedt [this message]
2021-03-22 21:38 ` [PATCH 1/2] streamline_config.pl: Make spacing consistent Steven Rostedt
2021-03-22 21:38 ` [PATCH 2/2] streamline_config.pl: Add softtabstop=4 for vim users Steven Rostedt
2021-03-24 6:01 ` Masahiro Yamada
2021-03-24 13:54 ` Steven Rostedt
2021-03-25 0:06 ` Steven Rostedt
2021-03-25 6:20 ` Masahiro Yamada
2021-03-25 13:50 ` Steven Rostedt
2021-03-25 14:09 ` Masahiro Yamada
2021-03-25 15:10 ` Steven Rostedt
2021-03-26 7:51 ` Joe Perches
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210322213806.089334551@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=warthog9@kernel.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.