public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Radisson <Radisson97@gmx.de>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, GNU C Library <libc-alpha@sourceware.org>
Subject: Re: new:mbrtoc32.3: convert from to c32
Date: Tue, 6 Jul 2021 12:57:14 +0200	[thread overview]
Message-ID: <56b23daf-16af-dd55-ba93-5250ee3a1fc6@gmail.com> (raw)
In-Reply-To: <11286132-a911-bfb4-784d-b0326c8132eb@gmx.de>

Hi,

On 7/5/21 10:31 PM, Radisson wrote:
>>
> I am no expert on the differences i will make contact with Bruno Haible,
> i hope he can help (he wrote already).

Okay.

>>>         void toc32( char *in,  int in_len, char32_t **outbuf, int *len)
>> Please, follow the style of other existing pages (it's similar to the
>> kernel coding style with some exceptions).
>> Especially, regarding spaces around parentheses and commas (and other
>> operators).
>> Also, please use a consistent indentation of 4 spaces.
>>
>> https://www.kernel.org/doc/html/v4.10/process/coding-style.html#spaces
>      can i use:    indent -i4 -linux ?

I don't know.  I guess that's an emacs thingy.  I use vim.
I don't have vim configured for that, but I'll do now (I use tabs for 
everything else, except YAML).  I don even have vim configured for man, 
because in my manual pages (for my code), I also use tabs.
But based on my vimrc, adapting it for 4-spaces in man, it could be 
something like:

set		nocindent
set		nosmartindent
set		noautoindent
set		indentexpr=
filetype	indent off
filetype	plugin indent off

" YAML only works with spaces :(
au filetype yaml	setlocal expandtab
au filetype yaml	setlocal shiftwidth=8
au filetype yaml	setlocal softtabstop=8
au filetype yaml	setlocal tabstop=8

au filetype man		setlocal expandtab
au filetype man		setlocal shiftwidth=4
au filetype man		setlocal softtabstop=4
au filetype man		setlocal tabstop=4


I hope it helps.

Regards,

Alex

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-07-06 10:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-20 20:29 new:mbrtoc32.3: convert from to c32 Radisson97
2021-07-03 17:40 ` Alejandro Colomar (man-pages)
2021-07-03 18:01   ` Alejandro Colomar (man-pages)
2021-07-05 20:31     ` Radisson
2021-07-06 10:57       ` Alejandro Colomar (man-pages) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-04 10:26 Bruno Haible
2021-07-05 19:07 ` Alejandro Colomar (man-pages)
2021-07-05 21:09   ` Radisson
2021-07-06 11:06     ` Alejandro Colomar (man-pages)
2021-06-20 20:28 Radisson97

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=56b23daf-16af-dd55-ba93-5250ee3a1fc6@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=Radisson97@gmx.de \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox