Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [RFA/NEWS] source is able to load Python scripts.
Date: Mon, 18 Jan 2010 17:51:00 -0000	[thread overview]
Message-ID: <83vdez714r.fsf@gnu.org> (raw)
In-Reply-To: <1263798265-2952-1-git-send-email-brobecker@adacore.com>

> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Joel Brobecker <brobecker@adacore.com>
> Date: Mon, 18 Jan 2010 11:04:25 +0400
> 
> This patch documents the fact that the "source" comment is now able to
> load Python scripts.  It also documents a new setting that was introduced
> to configure the behavior of the "source" command.

Thanks.

> +  Related to this enhancement is also the introduction a new command
> +  "set script-extension" (see below).                 ^^^^^^^^^^^^^^

"of a new command"

> +   If set to off, the debugger does not perform any script language
> +   recognition, and all sourced files are assumed to be GDB scripts.
> +   If set to "soft" (the default), files are sourced according to
> +   filename extension, falling back to GDB scripts if the first
> +   evaluation failed.
> +   If set to "strict", files are sourced according to filename extension.

If it's "strict" and "soft", then it should also be "off", with
quotes, right?

Btw, the patch for the manual that I just approved didn't document
"set script-extension", did I miss something?


  reply	other threads:[~2010-01-18 17:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18  7:04 Joel Brobecker
2010-01-18 17:51 ` Eli Zaretskii [this message]
2010-01-19 10:20   ` Joel Brobecker

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=83vdez714r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox