From: Jani Nikula <jani@nikula.org>
To: notmuch@notmuchmail.org
Subject: [PATCH v4 1/5] sprinter: clarify separator documentation
Date: Mon, 17 Dec 2012 00:05:09 +0200 [thread overview]
Message-ID: <7a846b6eaf0f7bc6a479b740d1678a6dac2b7323.1355695036.git.jani@nikula.org> (raw)
In-Reply-To: <cover.1355695036.git.jani@nikula.org>
In-Reply-To: <cover.1355695036.git.jani@nikula.org>
For text printers, the separator is a syntactic element.
---
sprinter.h | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/sprinter.h b/sprinter.h
index 59776a9..f43a844 100644
--- a/sprinter.h
+++ b/sprinter.h
@@ -42,10 +42,11 @@ typedef struct sprinter {
*/
void (*map_key) (struct sprinter *, const char *);
- /* Insert a separator (usually extra whitespace) for improved
- * readability without affecting the abstract syntax of the
- * structure being printed.
- * For JSON, this could simply be a line break.
+ /* Insert a separator (usually extra whitespace). For the text
+ * printers, this is a syntactic separator. For the structured
+ * printers, this is for improved readability without affecting
+ * the abstract syntax of the structure being printed. For JSON,
+ * this could simply be a line break.
*/
void (*separator) (struct sprinter *);
--
1.7.10.4
next prev parent reply other threads:[~2012-12-16 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 22:05 [PATCH v4 0/5] add --format=text0 to notmuch search Jani Nikula
2012-12-16 22:05 ` Jani Nikula [this message]
2012-12-16 22:05 ` [PATCH v4 2/5] sprinter: add text0 formatter for null character separated text Jani Nikula
2012-12-16 22:05 ` [PATCH v4 3/5] cli: add --format=text0 to notmuch search Jani Nikula
2012-12-16 22:05 ` [PATCH v4 4/5] test: notmuch search --format=text0 Jani Nikula
2012-12-16 22:05 ` [PATCH v4 5/5] man: document " Jani Nikula
2012-12-17 1:06 ` [PATCH v4 0/5] add --format=text0 to notmuch search Tomi Ollila
2012-12-17 1:09 ` Tomi Ollila
2012-12-18 21:07 ` David Bremner
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=7a846b6eaf0f7bc6a479b740d1678a6dac2b7323.1355695036.git.jani@nikula.org \
--to=jani@nikula.org \
--cc=notmuch@notmuchmail.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.
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).