From: Eli Carter <eli.carter@inet.com>
To: jbradford@dial.pipex.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stupid luser question
Date: Tue, 01 Oct 2002 13:29:30 -0500 [thread overview]
Message-ID: <3D99E98A.2020002@inet.com> (raw)
In-Reply-To: 200210011814.g91IEEY5007979@darkstar.example.net
jbradford@dial.pipex.com wrote:
> Just wondering, what is the purpose of the comment /* { */ which is found in various seemingly random places in the kernel:
>
> # grep -F -r "/* { */" *
>
> drivers/video/font_acorn_8x8.c:/* 7B */ 0x0C, 0x18, 0x18, 0x70, 0x18, 0x18, 0x0C, 0x00, /* { */
[snip]
Probably folding... possibly from vim/gvim.
If you're curious, look at: http://vim.sourceforge.net/htmldoc/fold.html
:set foldmethod=marker
:set foldmarker={,}
:set foldcolumn=6
Gets folding "mostly right" for C/C++ code. Manually added folds add in
a C comment containing the foldmarker, in this case "/* { */"
and "/* } */"
emacs probably has this feature as well, but I'm a vim person myself. :)
If you are not familiar with folding, look into it. I find it very
useful when dealing with unfamiliar code or looking at program structure.
HTH,
Eli
--------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------
next prev parent reply other threads:[~2002-10-01 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 18:14 Stupid luser question jbradford
2002-10-01 18:29 ` Eli Carter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 18:30 Petr Vandrovec
2002-10-01 18:36 John Hall
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=3D99E98A.2020002@inet.com \
--to=eli.carter@inet.com \
--cc=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox