unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean Sieger <sean.sieger@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#7167: 23.2; w32-shell-execute doc
Date: Thu, 07 Oct 2010 16:50:38 -0400	[thread overview]
Message-ID: <87eic1enhd.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTi=v_v1xh=L9GeEQ0RHsAcKg_6ZKRwy+pAxZ=+wm@mail.gmail.com>

Jason Rumney <jasonr@gnu.org> writes:

    It sounds like the problem could be a stale DOC file. Sean, did you run
    make install after building, or did you just copy the exe files into the
    bin directory by hand?

I ran make install.

    When I built the binaries, I always started from a fresh directory, and
    used make install to ensure everything was in place.

While I don't delete /bin, I don't alter the course of make install.

    It could also be caused by the recent changes to the install and
    packaging targets for Windows failing to copy or package all the
    required files.  I'm not sure if those changes went into the Emacs 23
    branch, if so then they may need checking.

I think post 23.2.






  parent reply	other threads:[~2010-10-07 20:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 14:46 bug#7167: 23.2; w32-shell-execute doc Mirko Vukovic
2010-10-06 18:27 ` Juanma Barranquero
2010-10-07  3:42   ` Christoph
2010-10-07  3:57     ` Christoph
2010-10-07 10:15       ` Juanma Barranquero
2010-10-07 10:44         ` Lennart Borgman
2010-10-07 10:46           ` Juanma Barranquero
2010-10-07 10:50             ` Lennart Borgman
2010-10-07 10:56               ` Juanma Barranquero
2010-10-07 11:53                 ` Lennart Borgman
2010-10-07 12:03                   ` Juanma Barranquero
2010-10-07 14:18         ` Jason Rumney
2010-10-07 18:19           ` Eli Zaretskii
2010-10-07 20:50           ` Sean Sieger [this message]
2010-10-07 18:12         ` Eli Zaretskii
2010-10-08  9:52           ` Eli Zaretskii
2010-10-08 10:34             ` Lennart Borgman
2010-10-08 15:08             ` Ken Brown
2010-10-07 20:53         ` Sean Sieger
2010-10-07 15:01 ` Esa Peuha

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=87eic1enhd.fsf@gmail.com \
    --to=sean.sieger@gmail.com \
    --cc=bug-gnu-emacs@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).