public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "U-BLASTER-6000\\mtdew" <thirdshiftcoder@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Fwd: updated: msg2pdf with emacs-w32
Date: Sun, 05 Nov 2017 18:00:00 -0000	[thread overview]
Message-ID: <vriu375s1u8l.fsf@BLASTER-6000.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <vriumv40aaw5.fsf@BLASTER-6000.i-did-not-set--mail-host-address--so-tickle-me>


Sorry:

I meant to include this message and it went to another recipient.

Yeah... I meant the correct spelling of minty. The little terminal.

Thx. very much for replying.

Jim McNamara

U-BLASTER-6000\mtdew writes:

> Hi-
>
> I noticed that possibly I use msg2pdf in virtualbox with linux
> instead. So I looked further into the path for msg2pdf. The exe is in a
> different location so i changed the path for mu4e-msg2pdf to correct.
>
> setq mu4e-msg2pdf "/home/mtdew/mu-0.9.18/toys/msg2pdf/.libs/msg2pdf.exe
>
> The curious thing now is when I try to launch with Alt+X
> mu4e-view-action I get the message "no message point"
>
> Not sure wny with the correct path now it won't launch. If I take off
> the .exe extension I think it gave me failed to create pdf message in
> the command buffer.
>
> The cool thing is comodo will launch adbobe pdf in a containter by file
> association rule.
>
> All I need to do is figure out how to get msg2pdf to launch a pdf in
> emacs-w32 with mu4e!
>
> Please assist if you have any cool tips.
>
> thx. -
> Jim McNamara


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

           reply	other threads:[~2017-11-05 18:00 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <vriumv40aaw5.fsf@BLASTER-6000.i-did-not-set--mail-host-address--so-tickle-me>]

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=vriu375s1u8l.fsf@BLASTER-6000.i-did-not-set--mail-host-address--so-tickle-me \
    --to=thirdshiftcoder@gmail.com \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).