Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David Fisher <fishboy@SPAMredSPAMpeanutSPAM.com
Subject: Re: error: w32-shell-execute is void
Date: Fri, 18 Jun 2004 18:39:35 GMT	[thread overview]
Message-ID: <84vfhoso5q.fsf@redpeanut.com> (raw)
In-Reply-To: <ur7scrj6k.fsf@isisSEND.vanderbiltME.eduSPAM>

David Hanak <dhanakDONT@isisSEND.vanderbiltME.eduSPAM> writes:

> On Thu, 17 Jun 2004, David Fisher <fishboy@SPAMredSPAMpeanutSPAM.com wrote:
> 
> > David Hanak <dhanakDONT@isisSEND.vanderbiltME.eduSPAM> writes:
> >
> >> w32-shell-execute should be built-in a function, not a variable:
> >
> [...]
> >
> > Thanks, I'm using Cygwin.  A post I found searching google
> > sugested the (setq solution and I got it stuck in my head that it
> > was a variable.  I'll just have to dig up a function definition
> > now.
> 
> But its built-in, i.e., it should be defined in the emacs
> executable, and not as a lisp function.
> 
> Have you tried upgrading Gnus?

[...]

Nope, I downloaded the latest 5.10.6 but then noticed it's a beta.
I'm not in a beta testing mood.  I figure I should be able to fake up
something using start-process or shell-execute and explorer.exe.  I
just haven't programed any lisp in 15 years.

><{{{*>


  reply	other threads:[~2004-06-18 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <843c4usvl7.fsf@redpeanut.com>
     [not found] ` <ubrjirze8.fsf@isisSEND.vanderbiltME.eduSPAM>
     [not found]   ` <84k6y5px2z.fsf@redpeanut.com>
2004-06-18 15:15     ` David Hanak
2004-06-18 18:39       ` David Fisher [this message]
     [not found]         ` <87wu24hcpu.fsf@koldfront.dk>
     [not found]           ` <84smcss1jx.fsf@redpeanut.com>
2004-06-21 17:49             ` Adam Sjøgren
2004-06-27 10:39             ` Kai Grossjohann

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=84vfhoso5q.fsf@redpeanut.com \
    --to=fishboy@spamredspampeanutspam.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 NNTP newsgroup(s).