* .mailcap on Windows / launching file attachments with "meadow" or "cygstart" etc.
@ 2005-04-06 19:14 John Owens
2005-04-13 16:42 ` John Owens
0 siblings, 1 reply; 2+ messages in thread
From: John Owens @ 2005-04-06 19:14 UTC (permalink / raw)
Using GNU Emacs 21.3.50.1 (i386-mingw-nt5.1.2600) of 2005-01-30
I run the "Wanderlust" mailer under emacs on both WinXP and OS X. In that
mailer I would like to launch file attachments in mail messages (so that when
I receive a PDF I can launch Acrobat to view it).
Wanderlust uses the MIME library called "SEMI", which has a method to "mime-
preview-play-current-entity". This looks in .mailcap to find out how to play
the entity in question.
Now, on OS X, this all works fine. My mailcap has entries that look like the
following:
image/*: /sw/bin/launch -w %s
which uses the nice "launch" utility that simply launches the associated
application with the file. All good. This works fine under CVS.
I have never got this to work under emacs on Windows. I was using the 21.3
release for a while, recently updated to the CVS build from 30 January
(above), and have tried a number of .mailcap entries to make this work. Among
them are "cygstart" (from cygwin) and "fiber" (from meadow) that are both
supposed to launch helper apps given a file name. When I call mime-preview-
play-current-entity, emacs records two messages:
Wrote c:/temp/EMI2060j4R/indep_study_proposal.doc
External method is starting...
and then nothing happens. No helper app launches. However, if I call, say,
weetabix 1% fiber -s c:/temp/EMI2060j4R/indep_study_proposal.doc
from the command line, everything works as I would expect.
If I try to quit emacs, I get a message like the following:
Proc Status Buffer
Command
---- ------ ------ ---
----
fiber -s "c:/temp/EMI2060j4R/indep_study_proposal.doc" run *MIME-echo*
C:/Program Files/emacs/bin/cmdproxy.exe -cf fiber -
s "c:/temp/EMI2060j4R/indep_study_proposal.doc"
I first thought this was a problem with my launcher, but now I'm leaning more
toward emacs being the problem since I've tried a couple of launchers now. And
since it works perfectly on OS X emacs, I don't think the fundamental approach
is flawed.
Might I request some help in debugging this, or if others have .mailcap
approaches that work fine, I'll happily hear those too?
JDO
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: .mailcap on Windows / launching file attachments with "meadow" or "cygstart" etc.
2005-04-06 19:14 .mailcap on Windows / launching file attachments with "meadow" or "cygstart" etc John Owens
@ 2005-04-13 16:42 ` John Owens
0 siblings, 0 replies; 2+ messages in thread
From: John Owens @ 2005-04-13 16:42 UTC (permalink / raw)
John Owens <john_owens <at> yahoo.com> writes:
> I have never got this to work under emacs on Windows. I was using the 21.3
> release for a while, recently updated to the CVS build from 30 January
> (above), and have tried a number of .mailcap entries to make this work.
And it turns out that setting the environment variable SHELL to "tcsh"
was the culprit; commenting that out allowed everything to work A-OK.
JDO
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-04-13 16:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-06 19:14 .mailcap on Windows / launching file attachments with "meadow" or "cygstart" etc John Owens
2005-04-13 16:42 ` John Owens
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.