Gnus development mailing list
 help / color / mirror / Atom feed
From: Andrew J Cosgriff <ajc@bing.wattle.id.au>
Subject: Re: Mailto:  links
Date: 07 Mar 2000 15:31:44 +1100	[thread overview]
Message-ID: <1yvh2zs8nj.fsf@earthling.aia.aig.com.au> (raw)
In-Reply-To: Andrew J Cosgriff's message of "Tue, 07 Mar 2000 04:14:35 GMT"

[-- Attachment #1: Type: text/plain, Size: 768 bytes --]

Andrew J Cosgriff wrote :

> Harry Putnam wrote :
> 
> > Is it possible to set netscape in such a way as to call gnus when
> > clicking a "mailto" link?
> 
> Yeah.  Grab muttzilla[1] and give it a whirl - there's a VM interface
> in there.  I keep meaning to get around to making it work with Gnus,
> but it consistently manages to fall off my stack.
> 
> If anybody's already done so, post it here ! :)
> 
> 
> Footnotes: 
> [1]  http://www3.telus.net/brian_winters/mutt/

Blah.  Here you go.  I call it "gnus-mail" and if you chuck the script
in /usr/local/lib/muttzilla and put

mailargs=gnus-mail

in your .muttzillarc it oughta work.  I couldn't be bothered worrying
about handling CC or BCC, 'cause it's not like I see them every day in
a mailto: header, so...


[-- Attachment #2: muttzilla script for using Gnus message mode --]
[-- Type: text/plain, Size: 1517 bytes --]

#! /bin/sh
#
# Script for spawning gnus' message composition under xemacs through
# muttzilla.
#
# by Andrew J Cosgriff <ajc@polydistortion.net>
# based on the VM one
# by Claus Brunzema <chb@ossi.fho-emden.de>
# most code stolen from muttzilla's mzmail.sh

# If you already have an xemacs with gnuserv running, this script
# first tries to start message mode using that xemacs.  Otherwise a
# new xemacs is started. So, if you don't want a new xemacs for every
# mail, put something like (gnuserv-start) in your .emacs.

# Arguments to the script:
#   1  to
#   2  cc
#   3  bcc
#   4  subject
#   5  body file
#   6  org

MZTO=$1
MZCC=$2
MZBCC=$3
MZSUB=$4
MZBOD=$5
MZORG=$6

ARGS="-eval '(progn (message-mail "

if [ -n "$MZTO" ] ; then
    ARGS="$ARGS \"$MZTO\""
fi

if [ -n "$MZSUB" ] ; then
    ARGS="\"$MZSUB\" "
fi

#
# I'm too lazy to deal with CC and BCC now (ajc)
#

#if [ -n "$MZCC" ] ; then
#    ARGS="$ARGS (mail-cc) (insert \"$MZCC\") "
#fi

#if [ -n "$MZBCC" ] ; then
#    ARGS="$ARGS (mail-bcc) (insert \"$MZBCC\") "
#fi

### body and org still missing ...


ARGS="$ARGS ))'"

if (gnuclient -batch -eval '(progn)' 2>&1 >/dev/null) ; then
    eval gnuclient $ARGS
else
    eval xemacs $ARGS
fi

# This is an ugly hack, and to be honest I'm not even sure it does
# what I think it does, but I hadn't really forseen that you might
# want to spawn one of two programs depending on the results of some
# test.  I'm sure I'll hear from some enterprising VM users who will
# let me know a better way.
exit 0

[-- Attachment #3: Type: text/plain, Size: 82 bytes --]


Enjoy,
 Andrew
-- 
Andrew J Cosgriff <ajc@polydistortion.net> shaken and stirred

  reply	other threads:[~2000-03-07  4:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-04 19:35 Harry Putnam
2000-03-07  4:09 ` Andrew J Cosgriff
2000-03-07  4:31   ` Andrew J Cosgriff [this message]
2000-03-07  4:55     ` Brian May
2000-03-07 10:31       ` Andrew J Cosgriff

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=1yvh2zs8nj.fsf@earthling.aia.aig.com.au \
    --to=ajc@bing.wattle.id.au \
    /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).