From: Randy Dunlap <randy.dunlap@oracle.com>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
Johannes Weiner <hannes@saeurebad.de>,
Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH] Documentation: update CodingStyle tips for Emacs users
Date: Mon, 26 Jan 2009 08:38:25 -0800 [thread overview]
Message-ID: <497DE701.5050005@oracle.com> (raw)
In-Reply-To: <87priaumal.fsf@iki.fi>
Teemu Likonen wrote:
> Teemu Likonen (2009-01-18 19:18 +0200) wrote:
>
>> With the previous Emacs tips example the kernel style was made available
>> for files in the kernel-tree only. This patch updates the tip to add
>> separate cc-mode indent style; it makes the kernel style easily
>> available for any filetype mode that is managed by the Emacs cc-mode.
>>
>> We also fix the filename regexp in the example: Elisp function
>> buffer-file-name returns full pathname, not a path relative to user's
>> home directory. Hence a tilde (~) can't be used to refer to home
>> directory (as the previous code did).
>>
>> Signed-off-by: Teemu Likonen <tlikonen@iki.fi>
>> ---
>> Documentation/CodingStyle | 19 +++++++++++++------
>> 1 files changed, 13 insertions(+), 6 deletions(-)
>
>
> Exactly what I expected: nobody pays any attention. :-) Well, it's not a
> problem, I'm not even a kernel coder. I just happen to think that this
> patch introduces the right way to configure Emacs for kernel coding
> style. Adding a custom style like this ("linux-tabs-only") makes it much
> easier to switch between different indent styles and also to use the
> kernel style elsewhere.
>
> So, I'll just ping the lists and maintainers this one more time to see
> if someone is interested. Here's my original message:
>
> http://article.gmane.org/gmane.linux.documentation/442
>
OK, I see it. I'm not an emacs user and I have no idea how correct
the patch is.
There is another emacs CodingStyle patch from Dan Carpenter that
expands the "~" part of the filename to the user directory:
see http://lkml.org/lkml/2009/1/21/62
so I would be tempted to merge/apply both patches.
Any other comments on these patches?
>
>> diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
>> index 1875e50..2cda242 100644
>> --- a/Documentation/CodingStyle
>> +++ b/Documentation/CodingStyle
>> @@ -483,20 +483,27 @@ values. To do the latter, you can stick the following in your .emacs file:
>> (* (max steps 1)
>> c-basic-offset)))
>>
>> +(add-hook 'c-mode-common-hook
>> + (lambda ()
>> + ;; Add kernel style
>> + (c-add-style
>> + "linux-tabs-only"
>> + '("linux" (c-offsets-alist
>> + (arglist-cont-nonempty
>> + c-lineup-gcc-asm-reg
>> + c-lineup-arglist-tabs-only))))))
>> +
>> (add-hook 'c-mode-hook
>> (lambda ()
>> (let ((filename (buffer-file-name)))
>> ;; Enable kernel mode for the appropriate files
>> (when (and filename
>> - (string-match "~/src/linux-trees" filename))
>> + (string-match "src/linux-trees" filename))
>> (setq indent-tabs-mode t)
>> - (c-set-style "linux")
>> - (c-set-offset 'arglist-cont-nonempty
>> - '(c-lineup-gcc-asm-reg
>> - c-lineup-arglist-tabs-only))))))
>> + (c-set-style "linux-tabs-only")))))
>>
>> This will make emacs go better with the kernel coding style for C
>> -files below ~/src/linux-trees.
>> +files which pathname matches src/linux-trees.
>>
>> But even if you fail in getting emacs to do sane formatting, not
>> everything is lost: use "indent".
>> --
Thanks.
--
~Randy
next prev parent reply other threads:[~2009-01-26 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 17:18 [PATCH] Documentation: update CodingStyle tips for Emacs users Teemu Likonen
2009-01-26 15:20 ` Teemu Likonen
2009-01-26 16:38 ` Randy Dunlap [this message]
2009-01-26 16:56 ` Teemu Likonen
2009-01-26 17:01 ` [PATCH v2] " Teemu Likonen
2009-01-26 17:13 ` Randy Dunlap
2009-01-26 17:21 ` Teemu Likonen
2009-01-26 17:23 ` Randy Dunlap
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=497DE701.5050005@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=error27@gmail.com \
--cc=hannes@saeurebad.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=tlikonen@iki.fi \
/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