Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Taylor <dtaylor@usendtaylorx2l.lss.emc.com>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org, eliz@gnu.org
Subject: Re: Fwd: Delivery Status Notification (Failure)
Date: Thu, 20 Nov 2014 14:58:00 -0000	[thread overview]
Message-ID: <12971.1416495464@usendtaylorx2l> (raw)
In-Reply-To: <CAP9bCMRJr4Fbunbnt-93FYnWUgDqjaLWZ731_rZp-JP8qkKf=w@mail.gmail.com>

Doug Evans <xdje42@gmail.com> wrote:

> Hi.
> This didn't go through for some strange reason.
> I'm hoping this does.

Bizarre.

> Delivery to the following recipient failed permanently:
> 
>      dtaylor@usendtaylorx2l.lss.emc.com
> 
> Technical details of permanent failure:
> DNS Error: Address resolution of usendtaylorx2l.lss.emc.com. failed:
> Domain name not found

Groan.  IT must have changed something.  usendtaylorx2l is my desktop.
Outgoing mail should show an address of either dtaylor@emc.com or
david.taylor@emc.com.

> Subject: Re: RFA info macro [-at LOCATION,] (v2)
> From: Doug Evans <xdje42@gmail.com>
> 
> On Wed, Nov 19, 2014 at 1:00 PM, David Taylor
> <dtaylor@usendtaylorx2l.lss.emc.com> wrote:

> > The following patch adds the option [-at LOCATION,] to 'info macro' to
> > enable the use of a user selected location as a documented feature.
> 
> Hi.

Hello.

> The "," in "-at LOCATION," seems a bit random, relative to other commands.
> 
> Maybe it is the best way to go.
> If so, I'd like to see the reasons why it exists documented in the code.
> 
> Can we just remove the , and require -- when necessary?

It marks the end of the location and the start of the macro.  It is
patterned after

    maint agent [-at location,] EXPRESSION
and
    maint agent-eval [-at location,] EXPRESSION

I did it the same way for consistency.

It seems unnecessary, but the location parsing code stops at comma but
not at space.  Presumably that is so that file names can contain spaces.
But, that is just a guess on my part.  I personally dislike file names
containing spaces.

David


  parent reply	other threads:[~2014-11-20 14:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 21:41 RFA: info macro [-at LOCATION,] David Taylor
2014-11-11  3:44 ` Eli Zaretskii
2014-11-11 14:01   ` David Taylor
2014-11-11 15:41     ` Eli Zaretskii
2014-11-19 21:00   ` RFA info macro [-at LOCATION,] (v2) David Taylor
2014-11-19 21:20     ` Eli Zaretskii
2014-11-20  2:38     ` Doug Evans
     [not found]       ` <001a1132e59ca4575e0508413955@google.com>
     [not found]         ` <CAP9bCMRJr4Fbunbnt-93FYnWUgDqjaLWZ731_rZp-JP8qkKf=w@mail.gmail.com>
2014-11-20 14:58           ` David Taylor [this message]
2014-11-23 19:18             ` Fwd: Delivery Status Notification (Failure) Doug Evans
2014-11-23 20:00               ` Doug Evans

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=12971.1416495464@usendtaylorx2l \
    --to=dtaylor@usendtaylorx2l.lss.emc.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@gmail.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