From: Andy Wingo <wingo@pobox.com>
To: "Jose A. Ortega Ruiz" <jao@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Add new debug meta-command ,error
Date: Mon, 30 Aug 2010 18:54:35 -0700 [thread overview]
Message-ID: <m3r5hfwnqc.fsf@unquote.localdomain> (raw)
In-Reply-To: <8762yr6d9v.fsf@newton.homeunix.net> (Jose A. Ortega Ruiz's message of "Mon, 30 Aug 2010 22:45:00 +0200")
On Mon 30 Aug 2010 13:45, "Jose A. Ortega Ruiz" <jao@gnu.org> writes:
> On Mon, Aug 30 2010, Andy Wingo wrote:
>
>> On Mon 30 Aug 2010 12:39, "Jose A. Ortega Ruiz" <jao@gnu.org> writes:
>>
>>> changed the name of the command from `error' to `message'
>>
>>> I'm not specially happy with the new name, but couldn't think of
>>> anything better. Suggestions welcome.
>>
>> How about "error-message" ? Perhaps abbreviated as ,error ?
>
> yeah, that was my first idea, but i thought you'd find it too long :)
> i'm for it if you like it, though -- perhaps we could abbreviate it as
> ,e to compensate?
I would prefer ,error-message and ,error, I think; I feel like we could
use ,e for other things (eval, expand, ...).
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-08-31 1:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 4:52 [PATCH] Add new debug meta-command ,error Jose A. Ortega Ruiz
2010-08-30 15:01 ` Andy Wingo
2010-08-30 19:39 ` Jose A. Ortega Ruiz
2010-08-30 20:44 ` Andy Wingo
2010-08-30 20:45 ` Jose A. Ortega Ruiz
2010-08-31 1:54 ` Andy Wingo [this message]
2010-08-31 2:30 ` Jose A. Ortega Ruiz
2010-08-31 3:23 ` Andy Wingo
2010-08-31 11:56 ` Jose A. Ortega Ruiz
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r5hfwnqc.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=jao@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.
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).