Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Simon Marchi <simon.marchi@efficios.com>,
	Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] gdb: remove TYPE_NAME macro
Date: Sat, 16 May 2020 15:33:35 -0400	[thread overview]
Message-ID: <64764e03-c3e5-ff00-8825-8794e2044ed1@simark.ca> (raw)
In-Reply-To: <87tv0f65ri.fsf@tromey.com>

On 2020-05-16 3:26 p.m., Tom Tromey wrote:
> Simon> I'd be curious to run it.  This is what I get, it's probably not expected:
> 
> Simon> $ emacs --script gdb-refactoring-scripts/rewriter.el method TYPE_NAME name
> Simon> Loading 00debian-vars...
> Simon> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Simon> Loading /etc/emacs/site-start.d/50cmake-data.el (source)...
> 
> This output is from your system site-lisp and unfortunately can't be
> suppressed.
> 
> Simon> Symbol's function definition is void: directory-files-recursively
> 
> Simon> My cwd is gdb's source directory.  Any idea what's going wrong?
> 
> You probably have an older Emacs.
> I think this was introduced in Emacs 25 though I'm not 100% sure.

Ah that's it, I was using emacs 24.  With emacs 26 it ran fine.  It works
pretty well!

Simon


  reply	other threads:[~2020-05-16 19:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 18:18 [PATCH 1/2] gdb: add type::name / type::set_name Simon Marchi
2020-05-14 18:18 ` [PATCH 2/2] gdb: remove TYPE_NAME macro Simon Marchi
2020-05-16 16:00   ` Tom Tromey
2020-05-16 16:35     ` Simon Marchi
2020-05-16 18:18       ` Tom Tromey
2020-05-16 19:10         ` Simon Marchi
2020-05-16 19:26           ` Tom Tromey
2020-05-16 19:33             ` Simon Marchi [this message]
2020-05-16 15:58 ` [PATCH 1/2] gdb: add type::name / type::set_name Tom Tromey

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=64764e03-c3e5-ff00-8825-8794e2044ed1@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.com \
    --cc=tom@tromey.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox