From: Kenichi Handa <handa@m17n.org>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Docstring of `decode-coding-string' a bit misleading about insertion in buffer
Date: Mon, 20 Oct 2008 19:43:12 +0900 [thread overview]
Message-ID: <E1KrsEC-0007Fr-RG@etlken.m17n.org> (raw)
In-Reply-To: <f7ccd24b0810200121g7491defcx5b549c7e96d38bf0@mail.gmail.com> (lekktu@gmail.com)
In article <f7ccd24b0810200121g7491defcx5b549c7e96d38bf0@mail.gmail.com>, "Juanma Barranquero" <lekktu@gmail.com> writes:
> On Mon, Oct 20, 2008 at 10:12, Kenichi Handa <handa@m17n.org> wrote:
> > Anyway, if we
> > write "inserted in buffer (after point and markers)", I
> > think it means the text is inserted without moving point and
> > markers.
> I'm sure it means that. I think I would still have missed it, because
> I misread the "inserted" as related to `insert', which moves the
> point.
> I would just add "The point does not move." or somesuch. But I'm not
> good writing docs.
Me neither. Could someone please improve these docstrings?
encode-coding-region
decode-coding-region
encode-coding-string
decode-coding-string
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-10-20 10:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 14:19 Docstring of `decode-coding-string' a bit misleading about insertion in buffer Juanma Barranquero
2008-10-20 7:04 ` Kenichi Handa
2008-10-20 7:18 ` Juanma Barranquero
2008-10-20 8:12 ` Kenichi Handa
2008-10-20 8:21 ` Juanma Barranquero
2008-10-20 10:43 ` Kenichi Handa [this message]
2008-10-21 15:57 ` Eli Zaretskii
2008-10-21 22:47 ` Juanma Barranquero
2008-10-22 1:23 ` Kenichi Handa
2008-10-20 17:04 ` Richard M. Stallman
2008-10-21 2:53 ` Kenichi Handa
2008-10-21 19:40 ` Richard M. Stallman
2008-10-20 17:04 ` Richard M. Stallman
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=E1KrsEC-0007Fr-RG@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.