unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <jmbarranquero@wke.es>
Cc: emacs-devel@gnu.org
Subject: Re: Malformed interactive spec in replace.el
Date: Tue, 06 Jul 2004 13:05:06 +0200	[thread overview]
Message-ID: <20040706125523.5883.JMBARRANQUERO@wke.es> (raw)
In-Reply-To: <x5wu1hpgu4.fsf@lola.goethe.zz>


On 06 Jul 2004 12:31:31 +0200
David Kastrup <dak@gnu.org> wrote:

> It wasn't here as far as I was able to discern.

I've not followed the replace thread (my message was just to report a
tiny bug which caused a miscompilation), so I don't have an opinion
about that.

> You mean that when a team trainer or team mate is telling his players
> to try harder, the conclusion should be that they all stop trying
> because it appears it would take an effort to succeed?

No.  I mean what it would be good to know whether the team players are
all interested in playing the same game, at the same time, with the same
motivation :)

> Reminding people of things we all agreed on is not "pushing" in my
> book.

Perhaps I read this kind of things differently.  Every time I see a post
saying (with gentler wording, of course) "OK, I get what you're doing,
but, BTW, shouldn't you be doing such and such other thing" I feel the
pushing.

> If I had not already documented all of this in the manual, I'd be
> sorely tempted to rip everything except the basic \, out again since
> it would appear that I have been setting a bad example, even though I
> tried to reach consensus on the list about the immediate desirability
> of those changes before checking them in.

I don't think you've set a bad or good example.  More like you've done
what most of us are doing: concentrate on the release, but finding a bit
of trouble leaving aside our own pet projects or improvements.  But
that's only how I interpret it, of course.

                                                                Juanma

  reply	other threads:[~2004-07-06 11:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06  8:15 Malformed interactive spec in replace.el Juanma Barranquero
2004-07-06  8:35 ` David Kastrup
2004-07-06  8:45   ` Juanma Barranquero
2004-07-06  9:26     ` David Kastrup
2004-07-06  9:46       ` Juanma Barranquero
2004-07-06 10:31         ` David Kastrup
2004-07-06 11:05           ` Juanma Barranquero [this message]
2004-07-06 11:42             ` David Kastrup
2004-07-06 12:33               ` Juanma Barranquero
2004-07-06 12:17   ` Stefan
2004-07-06 12:50     ` David Kastrup
2004-07-06 13:08       ` Stefan
2004-07-06 14:13         ` David Kastrup
2004-07-06 14:39           ` David Kastrup
2004-07-06 15:26             ` Stefan
2004-07-06 17:18               ` David Kastrup
2004-07-07 13:28                 ` Stefan
2004-07-07 13:45                   ` David Kastrup
2004-07-07 14:22                     ` Stefan
2004-07-07 14:28                       ` David Kastrup

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040706125523.5883.JMBARRANQUERO@wke.es \
    --to=jmbarranquero@wke.es \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).