From: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>, guile-user@gnu.org
Subject: Re: How to write documentation comments for procedures?
Date: Tue, 7 Aug 2018 00:58:08 +0200 [thread overview]
Message-ID: <3ac96df4-1577-5912-ae9f-21e6ba7ef009@gmail.com> (raw)
In-Reply-To: <c4921326.AM0AABISyFkAAAAAAAAAAARRGgcAAAACwQwAAAAAAAW9WABbaBRO@mailjet.com>
Ha, I did not know that one. It still makes the second and later lines
not indented though (starting at position 0, while the first line is
indented, not starting at 0). Anyway, knowing this shortcut would have
saved me soooo much time in many cases … Thanks.
On 06.08.2018 11:26, Arun Isaac wrote:
>> However, when I have a longer explanation for a procedure, longer than a
>> single line of certain length, then the line will softly wrap in editors
>> and the explanation will continue on the next line at the beginning
>> usually.
> In emacs, I find `fill-paragraph' (default keybinding of M-q) to be very
> useful for wrapping long lines.
next prev parent reply other threads:[~2018-08-06 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 13:27 How to write documentation comments for procedures? Zelphir Kaltstahl
2018-08-05 16:22 ` tomas
2018-08-06 9:26 ` Arun Isaac
[not found] ` <c4921326.AM0AABISyFkAAAAAAAAAAARRGgcAAAACwQwAAAAAAAW9WABbaBRO@mailjet.com>
2018-08-06 22:58 ` Zelphir Kaltstahl [this message]
2018-08-07 5:58 ` Arun Isaac
2018-08-21 21:41 ` Arne Babenhauserheide
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ac96df4-1577-5912-ae9f-21e6ba7ef009@gmail.com \
--to=zelphirkaltstahl@gmail.com \
--cc=arunisaac@systemreboot.net \
--cc=guile-user@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).