unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: Sebastian Lipp <bacuh@riseup.net>
Cc: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: add missing paren to fix defun in notmuch-address.el.
Date: Mon, 07 Jul 2014 12:40:35 -0500	[thread overview]
Message-ID: <87y4w5jcdo.fsf@ktab.red-bean.com> (raw)
In-Reply-To: <87bnt2dy0b.fsf@verb.i-did-not-set--mail-host-address--so-tickle-me> (Sebastian Lipp's message of "Sun, 06 Jul 2014 22:37:40 +0200")

Sebastian Lipp <bacuh@riseup.net> writes:
>> I think it's good to include an initial value (even an invalid
>> placeholder one, if the real initialization has not happened yet), and a
>> doc string.  C-h f defvar RET will say more about how to do that.
>
>I hope I got that right now. (I've got no real clue of Lisp yet because
>I just recently switched to emacs partly because of notmuch. :)
>
>How about
>
>    (defvar bbdb-get-addresses-headers nil
>      "List of Addresses to import into bbdb")

That's interesting -- from seeing the variable's name, I would not have
guessed that it is a list.

Can the doc string describe the exact format of the list, and something
about how the list is initialized and used?

In other words, if you were a programmer seeing this variable for the
first time, and you had only a basic working knowledge of what the
notmuch Elisp code does, what would you want to see in this doc string
to give you a good understanding of what this variable is, how it gets
set, and how it's used?

One test I often use for myself is that if after I've read the doc
string, I can look at any value and say whether or not it is a valid
value that this variable might hold (when the code is running), then the
doc string has done its job.

Best,
-Karl

  reply	other threads:[~2014-07-07 17:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 18:33 [PATCH] emacs: add missing paren to fix defun in notmuch-address.el Karl Fogel
2013-04-07 13:52 ` David Bremner
2013-04-07 21:50   ` Karl Fogel
2013-04-08  8:16     ` Tomi Ollila
2013-04-08  8:40       ` Jani Nikula
2013-04-08 10:50         ` David Bremner
2013-04-09  1:12           ` Jed Brown
2013-04-09  6:32             ` Tomi Ollila
2013-04-09 11:50               ` David Bremner
2013-04-09 12:12                 ` Tomi Ollila
2014-07-04  0:38                   ` Sebastian Lipp
2014-07-04  0:56                     ` Karl Fogel
2014-07-04  9:25                       ` Sebastian Lipp
2014-07-05 18:18                         ` Karl Fogel
2014-07-06 20:41                           ` Sebastian Lipp
2014-07-07 17:35                             ` Karl Fogel
2014-07-06 20:37                       ` Sebastian Lipp
2014-07-07 17:40                         ` Karl Fogel [this message]
2014-07-08  8:56                         ` Tomi Ollila
2014-07-08 17:59                           ` Karl Fogel
2014-07-04 16:31                     ` Tomi Ollila

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://notmuchmail.org/

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

  git send-email \
    --in-reply-to=87y4w5jcdo.fsf@ktab.red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=bacuh@riseup.net \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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).