From: "HIROSHI OOTA" <nil@mad.dog.cx>
To: emacs-devel@gnu.org
Subject: Re: Emacs 23.4 release candidate 1
Date: Tue, 24 Jan 2012 10:46:53 +0900 [thread overview]
Message-ID: <op.v8ke8g1vb34bpo@lenovo-b0c22c0d> (raw)
In-Reply-To: <87sjjb4rju.fsf@gnu.org>
On Fri, 20 Jan 2012 00:53:41 +0900, Chong Yidong <cyd@gnu.org> wrote:
> The release candidate for Emacs 23.4 is now available for download at:
>
> ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-23.4rc1.tar.gz
>
> Note that although the version number has been bumped to 23.4 in the
> tarball and in the emacs-23 branch, I have not tagged the release yet,
> in case there are last minute changes.
>
> If no serious problem surfaces in the next couple of days, I'll release
> this as Emacs 23.4. So please help give it as much testing as possible.
> Thank you.
the ecoding.c:encode_designation_at_bol shuld return EMACS_INT.
--
Hiroshi Oota
--- src/coding.c (revision 868)
+++ src/coding.c (working copy)
@@ -944,7 +948,7 @@
static unsigned char *alloc_destination P_ ((struct coding_system *,
EMACS_INT, unsigned char *));
static void setup_iso_safe_charsets P_ ((Lisp_Object));
-static int encode_designation_at_bol P_ ((struct coding_system *,
+static EMACS_INT encode_designation_at_bol P_ ((struct coding_system *,
int *, int *, unsigned char *));
static int detect_eol P_ ((const unsigned char *,
EMACS_INT, enum coding_category));
@@ -4509,7 +4513,7 @@
If the current block ends before any end-of-line, we may fail to
find all the necessary designations. */
-static int
+static EMACS_INT
encode_designation_at_bol (coding, charbuf, charbuf_end, dst)
struct coding_system *coding;
int *charbuf, *charbuf_end;
next prev parent reply other threads:[~2012-01-24 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 15:53 Emacs 23.4 release candidate 1 Chong Yidong
2012-01-24 1:46 ` HIROSHI OOTA [this message]
2012-01-24 7:18 ` Kenichi Handa
2012-01-24 11:51 ` Juanma Barranquero
2012-01-25 0:56 ` Kenichi Handa
2012-01-25 5:56 ` Chong Yidong
2012-01-26 0:37 ` Kenichi Handa
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=op.v8ke8g1vb34bpo@lenovo-b0c22c0d \
--to=nil@mad.dog.cx \
--cc=emacs-devel@gnu.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://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).