unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mirko <mvukovic@nycap.rr.com>
To: help-gnu-emacs@gnu.org
Subject: Re: hideshow docstring in elisp or common lisp code
Date: Thu, 8 Nov 2018 05:57:04 -0800 (PST)	[thread overview]
Message-ID: <917d89da-2bea-4f67-b820-9b670632e84b@googlegroups.com> (raw)
In-Reply-To: <86o9b2auxh.fsf@zoho.eu>

On Tuesday, November 6, 2018 at 2:05:17 PM UTC-5, Emanuel Berg wrote:
> Mirko Vukovic wrote:
> 
> > I would like to hide/show docstrings of my
> > common lisp code.
> 
> Sorry for a non-answer, but why do you want to
> do that? Instead, practice to write really
> short and to-the-point instructions :)
> 
> There are formal rules, which are good to stick
> to. Probably you are aware of them, and the
> facilities to formally check the formalities,
> but I tell you/everyone else anyway how to do
> it:
> 
>     (defun check-package-style ()
>       (interactive)
>       (checkdoc-current-buffer t) ; TAKE-NOTES
>       (message "Style check done.") )
> 
> Good luck!
> 
> -- 
> underground experts united
> http://user.it.uu.se/~embe8573

Emanuel,

First thanks for pointing to checkdoc.  I was not
aware of it.

My intent is to keep the function's documentation
close to the function itself.  

For my Common Lisp code I follow the layout used in
the official documentation (the Hyperspec), which
while verbose, starts with a single line brief
explaining the function.  Hideshow on that would work
very nicely on that convention.

One benefit (for me) is the documentation generator 
(HeLambdaP) that parses the lisp file and the docstring,
and generates the html documentation straight from the
docstring.

To summarize:
- keeping documentation close to the code makes 
  maintenance easy
- Following hyperspec convention allows for generation
  of html documentation.

Mirko


  reply	other threads:[~2018-11-08 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3529.1541470097.1284.help-gnu-emacs@gnu.org>
2018-11-06 19:05 ` hideshow docstring in elisp or common lisp code Emanuel Berg
2018-11-08 13:57   ` Mirko [this message]
2018-11-05 22:33 Mirko Vukovic
2018-11-09  2:12 ` Michael Heerdegen
2018-11-11  9:03   ` Andreas Röhler
2018-11-13  3:34 ` Drew Adams
2018-11-13 15:11   ` Drew Adams

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=917d89da-2bea-4f67-b820-9b670632e84b@googlegroups.com \
    --to=mvukovic@nycap.rr.com \
    --cc=help-gnu-emacs@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).