unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sean Sieger <sean.sieger@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: use of minibuffer in interactive spec code
Date: Wed, 19 May 2010 19:16:21 +0300	[thread overview]
Message-ID: <83hbm3rhnu.fsf@gnu.org> (raw)
In-Reply-To: <878w7fj2t0.fsf@gmail.com>

> From: Sean Sieger <sean.sieger@gmail.com>
> Date: Wed, 19 May 2010 12:04:27 -0400
> 
>     > I cannot reproduce this problem on the trunk.  Can you?
> 
>     I don't have a trunk. ;-) The latest Windows binary I have is
>     23.2. If a more recent binary becomes available I can check that.
> 
> Is this a good reason for publishing Windows binaries at
> ftp.gnu.org/gnu/emacs/windows? like a weekly build, with a name
> `emacs-2010xxxx-bin-i386.zip'?  I'd be willing to do that.

If you do this, alpha.gnu.org would be a better place, as that's where
development snapshots and alpha-quality versions are usually put.

Thanks.



  reply	other threads:[~2010-05-19 16:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 17:11 use of minibuffer in interactive spec code Drew Adams
2010-05-18 17:27 ` Drew Adams
2010-05-18 20:39 ` Stefan Monnier
2010-05-19  3:27 ` Stefan Monnier
2010-05-19 12:44   ` Drew Adams
2010-05-19 15:39     ` Stefan Monnier
2010-05-19 16:40       ` Drew Adams
2010-05-19 17:41         ` Stefan Monnier
2010-05-19 16:04     ` Sean Sieger
2010-05-19 16:16       ` Eli Zaretskii [this message]
2010-05-19 16:21       ` posting Windows binaries of latest trunk dev code [was: use of minibuffer in interactive spec code] Drew Adams
2010-05-19 17:25         ` Eli Zaretskii
2010-05-19 17:48           ` Drew Adams
2010-05-20 21:19           ` posting Windows binaries of latest trunk dev code Sean Sieger

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=83hbm3rhnu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sean.sieger@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. 
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).