From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/2] templates/*-in: tell vim to use Kconfig syntax
Date: Wed, 14 Jun 2017 13:10:30 +0200 [thread overview]
Message-ID: <20170614110941.GP31396@falbala.home.lespocky.de> (raw)
In-Reply-To: <20170614103126.22766-2-r.hieber@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 705 bytes --]
Hei hei,
> +# vim: syntax=kconfig
is there any reason you chose 'syntax' over 'filetype'? I probably did
not fully understand the differences between those two Vim commands,
but the modeline in my custom *.in is like this:
# vim: ft=kconfig noet tw=72
noexpandtab is useful to keep the whitespace like in the other
rules/*.in files and textwidth=72 is my personal choice for easier
wrapping.
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 ***
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2017-06-14 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 10:31 [ptxdist] [PATCH 1/2] ptxd_lib_template: fix indentation Roland Hieber
2017-06-14 10:31 ` [ptxdist] [PATCH 2/2] templates/*-in: tell vim to use Kconfig syntax Roland Hieber
2017-06-14 11:10 ` Alexander Dahl [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170614110941.GP31396@falbala.home.lespocky.de \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox