public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Keith Seitz <keiths@redhat.com>
Cc: archer@sourceware.org
Subject: Re: [Archer] New linespec error messages
Date: Sat, 17 Mar 2012 03:36:00 -0000	[thread overview]
Message-ID: <CAN9gPaFvouqgoE4AcppPdZ0sG61H+uNsLUtMfqgwtMPYGgXgjA@mail.gmail.com> (raw)
In-Reply-To: <4F634A31.4000105@redhat.com>

On Fri, Mar 16, 2012 at 10:12 AM, Keith Seitz <keiths@redhat.com> wrote:
> On 03/16/2012 06:38 AM, Daniel Jacobowitz wrote:
>>
>> On Tue, Mar 13, 2012 at 4:17 PM, Joel Brobecker<brobecker@adacore.com>
>>  wrote:
>>>
>>>
>>>> Does anyone have any input on the text of these error messages? Any
>>>> changes that maintainers might like?
>>>
>>>
>>> I say, this looks pretty nice! The error message "unexpected EOF"
>>> might be a little cryptic to a newcomer, but overall, neat!
>>
>>
>> I agree; it's not an EOF, anyway.  "unexpected end of line"?
>
>
> I wasn't either. I have already committed a change to this for "unexpected
> end of input".
>
> So the question of the minute is, "line" or "input"? [I figure to try to get
> at least some of the trivia mostly settled by the time I submit the patch
> Very Soon Now (TM).

I like both options :-)

-- 
Thanks,
Daniel

      reply	other threads:[~2012-03-17  3:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 19:27 Keith Seitz
2012-03-13 20:18 ` [Archer] " Joel Brobecker
2012-03-16 13:38   ` Daniel Jacobowitz
2012-03-16 14:12     ` Keith Seitz
2012-03-17  3:36       ` Daniel Jacobowitz [this message]

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=CAN9gPaFvouqgoE4AcppPdZ0sG61H+uNsLUtMfqgwtMPYGgXgjA@mail.gmail.com \
    --to=drow@false.org \
    --cc=archer@sourceware.org \
    --cc=keiths@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).