unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Deniz Dogan'" <deniz.a.m.dogan@gmail.com>, <6493@debbugs.gnu.org>
Subject: bug#6493:
Date: Sun, 27 Jun 2010 06:52:47 -0700	[thread overview]
Message-ID: <F221D7D1A0244043A93D2D08E27B955C@us.oracle.com> (raw)
In-Reply-To: <AANLkTimfum-SIHtxsuaQLGZ9gvktH-rc9Nx--QOtctFT@mail.gmail.com>

> How about this? (See attached patch.)

1. Thanks for working on this.

2. Please cc the bug submitter, and please put the bug subject line in the
Subject line.  It was only by searching old mails for "6493" that I sent that I
was able to find that this was a bug I submitted. Now I must search similarly
for the other bugs you replied to with no Subject line other than the bug #.
Multiply my experience by that of others.

3. What's important about these functions is the return value. The doc string
needs to be explicit about what is _returned_. There is no need to repeat info
that follows from definitions (e.g. that point and mark are the region limits).

Example:

"Returns point or mark, whichever is larger."

Thx.







  reply	other threads:[~2010-06-27 13:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 16:13 bug#6493: 24.0.50; doc strings of region-beginning, region-end Drew Adams
2010-06-27 12:26 ` bug#6493: Deniz Dogan
2010-06-27 13:52   ` Drew Adams [this message]
2010-06-27 14:02     ` bug#6493: Deniz Dogan
2010-06-27 14:18       ` bug#6493: Drew Adams
2010-06-27 14:29         ` bug#6493: Deniz Dogan
2010-06-27 14:33           ` bug#6493: Drew Adams
2010-07-10 23:41             ` bug#6493: Deniz Dogan
2010-07-11  4:20               ` bug#6493: Drew Adams
2010-07-23  0:12                 ` bug#6493: Juanma Barranquero
2010-07-23  9:10                   ` bug#6493: Deniz Dogan
2010-07-23  9:30                     ` bug#6493: Juanma Barranquero
2010-07-23 15:45                       ` bug#6493: Chong Yidong
2010-07-23 16:16                         ` bug#6493: Drew Adams
2010-07-23 17:02                         ` bug#6493: Stephen Berman
2010-07-23 17:26                           ` bug#6493: Drew Adams
2010-07-23 17:32                             ` bug#6493: Juanma Barranquero
2010-07-29 11:44                               ` bug#6493: Juanma Barranquero
2010-07-29 15:16                                 ` bug#6493: Johan Bockgård
2010-08-01 19:01                                   ` bug#6493: Juanma Barranquero
2010-08-01 21:17                                     ` bug#6493: Drew Adams
2010-08-02  3:30                                       ` bug#6493: Juanma Barranquero
2010-08-02  5:09                                         ` bug#6493: Drew Adams
2010-08-02  5:34                                         ` bug#6493: Drew Adams
2010-08-02  6:43                                           ` bug#6493: Juanma Barranquero
2010-07-29 15:58                                 ` bug#6493: Chong Yidong

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=F221D7D1A0244043A93D2D08E27B955C@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=6493@debbugs.gnu.org \
    --cc=deniz.a.m.dogan@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).