From: Yngve Svendsen <yngve.svendsen@clustra.com>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>,help-gnats@gnu.org
Cc: Rick Macdonald <rickm@vsl.com>
Subject: Re: tkgnats patch to work with GNATS4
Date: Sat, 06 Oct 2001 12:19:00 -0000 [thread overview]
Message-ID: <5.1.0.14.2.20011119092847.043fa540@mail.trd.clustra.com> (raw)
In-Reply-To: <200111190343.fAJ3h2s03547@marajade.sandelman.ottawa.on.ca>
At 22:43 18.11.2001 -0500, Michael Richardson wrote:
> Also, rather than storing the query types in the dbconfig, why not have
>that stuff simply uploaded by QFMT or something? Unless we are going to
>have gnatsd, etc. compile the dbconfig file, the processing time would be the
>same, and then one can keep the query formats with the clients. Also, is
>there a solution to fields which have seperator characters in them?
First of all, let me say a big thank you for working on a TkGnats port.
Query expressions can indeed be uploaded by QFMT. The format strings are
exactly the same as those that can be given to the query-pr tool. Quoting
page 82 of the GNATS 4 manual:
QFMT query format
Use the specified query format to format the output of the QUER command.
The query format may be either the name of a query format known to the
server, or an actual query format. See "Formatting query-pr output", page 25.
I guess the main reason why the dbconfig file contains a few predefined
query formats is in order to make query-pr easier to use. Otherwise, one
would have to provide a complete query format specification on each
invocation of query-pr.
Yngve Svendsen
GNATS 4 doc guy
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
prev parent reply other threads:[~2001-11-19 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 6:41 Michael Richardson
2001-10-06 12:19 ` Yngve Svendsen [this message]
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=5.1.0.14.2.20011119092847.043fa540@mail.trd.clustra.com \
--to=yngve.svendsen@clustra.com \
--cc=help-gnats@gnu.org \
--cc=mcr@sandelman.ottawa.on.ca \
--cc=rickm@vsl.com \
/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).