From: Oleh Krehel <ohwoeowho@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: Is it time to remove INTERNAL_FIELD?
Date: Thu, 23 Apr 2015 14:05:28 +0200 [thread overview]
Message-ID: <87fv7rqcc7.fsf@gmail.com> (raw)
In-Reply-To: <83oamf12ax.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 23 Apr 2015 15:01:26 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> It shows up as unrecognized command for me. I see it defined in
>> .gdbinit, but it's automatically sourced. How can I source it?
>
> You can source it manually like this:
>
> (gdb) source .gdbinit
>
> If you start GDB from the src directory, it should read that file
> automatically. However, latest versions of GDB refuse to do that, for
> security reasons, unless you customize GDB to countermand that (the
> message GDB displays when it refuses to load the file hints on these
> customizations; read the GDB manual to know more).
>
> See etc/DEBUG for more about debugging Emacs on the C level.
Thanks.
>> I saw that there was a change 3 years ago adding "_" to ends of some
>> symbols. This change was subsequently reverted, and it supposedly worked
>> fine for 3 years. So I'm guessing that there is a mechanism that makes
>> it work without modifying with symbols with "_".
>
> No, there is no such mechanism. You will find "name_" in .gdbinit.
> Those changes you mention are probably about changes in the sources
> that were reverted later.
OK, I see it now. The only two occurences that I found for
"_\([^a-z]\|$\)" were "name_". I've pushed the change.
Is there anything else that needs to be done before merging?
Oleh
next prev parent reply other threads:[~2015-04-23 12:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 9:55 Is it time to remove INTERNAL_FIELD? Oleh Krehel
2015-04-23 10:08 ` Paul Eggert
2015-04-23 10:10 ` Oleh Krehel
2015-04-23 10:17 ` Paul Eggert
2015-04-23 10:56 ` Eli Zaretskii
2015-04-23 10:56 ` Oleh Krehel
2015-04-23 11:17 ` Eli Zaretskii
2015-04-23 11:32 ` Oleh Krehel
2015-04-23 12:01 ` Eli Zaretskii
2015-04-23 12:05 ` Oleh Krehel [this message]
2015-04-23 12:37 ` Eli Zaretskii
2015-04-25 10:57 ` Oleh Krehel
2015-04-25 11:28 ` Eli Zaretskii
2015-04-25 14:28 ` Stefan Monnier
2015-04-25 14:41 ` Eli Zaretskii
2015-04-28 7:39 ` Oleh Krehel
2015-04-28 13:20 ` Stefan Monnier
2015-04-28 15:07 ` Eli Zaretskii
2015-04-28 15:11 ` Oleh Krehel
2015-04-28 15:23 ` Eli Zaretskii
2015-04-28 18:58 ` Oleh Krehel
2015-04-28 19:21 ` Eli Zaretskii
2015-04-23 11:00 ` Eli Zaretskii
2015-04-23 13:24 ` Stefan Monnier
2015-04-23 13:30 ` Oleh Krehel
2015-04-23 13:53 ` Eli Zaretskii
2015-04-23 14:07 ` Oleh Krehel
2015-04-23 14:50 ` Nicolas Richard
2015-04-23 15:34 ` Eli Zaretskii
2015-04-24 10:44 ` Nicolas Richard
2015-04-23 15:29 ` Eli Zaretskii
2015-04-23 16:32 ` Oleh Krehel
2015-04-23 17:00 ` Eli Zaretskii
2015-04-23 17:09 ` Oleh Krehel
2015-04-23 17:29 ` Eli Zaretskii
2015-04-23 17:14 ` Stefan Monnier
2015-04-23 17:31 ` Eli Zaretskii
2015-04-23 13:30 ` Stefan Monnier
2015-04-23 13:33 ` Oleh Krehel
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=87fv7rqcc7.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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).