From: Alan J Third <alan@idiocy.org>
To: 2203@debbugs.gnu.org
Cc: Alan Mackenzie <acm@muc.de>
Subject: bug#2203: C Mode: C-M-a fails at BOD re_comp, src/regex.c L6534
Date: Fri, 15 Jan 2016 20:40:31 +0000 [thread overview]
Message-ID: <m2ziw637b4.fsf@galloway.idiocy.org> (raw)
In-Reply-To: <20090205113645.GA3213@muc.de> (Alan Mackenzie's message of "Thu, 5 Feb 2009 11:36:45 +0000")
Alan Mackenzie <acm@muc.de> writes:
> In .../src/regex.c put point at BOL6534, "char *" here:
>
> }
> WEAK_ALIAS (__re_compile_pattern, re_compile_pattern)
> ^L
> /* Entry points compatible with 4.2 BSD regex library. We don't define
> them unless specifically requested. */
>
> #if defined _REGEX_RE_COMP || defined _LIBC
>
> /* BSD has one and only one pattern buffer. */
> static struct re_pattern_buffer re_comp_buf;
>
> char * <=================================
> # ifdef _LIBC
> /* Make these definitions weak in libc, so POSIX programs can redefine
> these names if they don't use our functions, and still use
> regcomp/regexec below without link errors. */
> weak_function
> # endif
> re_comp (s)
> const char *s;
> {
>
>
> Do C-M-a. Point doesn't move.
>
> Preliminary investigation: With point on the 'h' of "char *",
> (c-beginning-of-decl-1 nil) should move point one character backwards.
> Instead, it moves to BOL "WEAK_ALIAS".
I just tested this in Emacs 25 and it seems that in every case point
moves back to "WEAK_ALIAS". That is, C-M-a, c-beginning-of-defun,
behaves the same way as (c-beginning-of-decl-1 nil).
I guess that makes it more broken, if more consistent, than when the bug
was raised.
--
Alan Third
next prev parent reply other threads:[~2016-01-15 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 11:36 bug#2203: C Mode: C-M-a fails at BOD re_comp, src/regex.c L6534 Alan Mackenzie
2016-01-15 20:40 ` Alan J Third [this message]
[not found] ` <mailman.2414.1452890468.843.bug-gnu-emacs@gnu.org>
2016-01-17 22:31 ` Alan Mackenzie
2016-01-22 23:06 ` Alan Mackenzie
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=m2ziw637b4.fsf@galloway.idiocy.org \
--to=alan@idiocy.org \
--cc=2203@debbugs.gnu.org \
--cc=acm@muc.de \
/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.