From: Ruthard Baudach <ruthard.baudach@web.de>
To: supmua <supmua@googlegroups.com>
Subject: Re: [sup] calling sup with email address as argument
Date: Thu, 30 Oct 2014 09:57:12 +0100 [thread overview]
Message-ID: <1414658899-sup-2941@ruthard-lappi> (raw)
In-Reply-To: <1414658379-astroid-1-lcvfs1mnt9-2157@strange>
[-- Attachment #1: Type: text/plain, Size: 2453 bytes --]
>== Auszüge aus der Nachricht von Gaute Hope vom 2014-10-30 09:43:
> Excerpts from Ruthard Baudach's message of October 30, 2014 9:36:
> > Dear developers,
> >
> > To use sup for composing emails following "mailto://" links in HTML
> > documents, sup should enter compose mode when called with an email
> > adress as command line argument like this:
> >
> > sup supmua@googlegroups.com
> >
> > This could be achieved adding the following line of code after
> > the option definitions in bin/sup:
> >
> > ---------------->%----------------------------
> > $opts = Trollop::options do
> > version "sup v#{Redwood::VERSION}"
> > banner <<EOS
> > Sup is a curses-based email client.
> >
> > Usage:
> > sup [options]
> >
> > Options are:
> > EOS
> > opt :list_hooks, "List all hooks and descriptions, and quit."
> > opt :no_threads, "Turn off threading. Helps with debugging. (Necessarily disables background polling for new messages.)"
> > opt :no_initial_poll, "Don't poll for new messages when starting."
> > opt :search, "Search for this query upon startup", :type => String
> > opt :compose, "Compose message to this recipient upon startup", :type => String
> > opt :subject, "When composing, use this subject", :type => String, :short => "j"
> > end
> >
> >>>> ## compose message if we have an email address as first command line argument
> >>>> $opts[:compose] = ARGV[0] if ARGV[0] =~ /.+@.+\..+/ && !$opts[:compose]
> > ---------------->%----------------------------
>
> That is fine by me, but perhaps you can use trollop? Otherwise I don't
> think this possibility will be contained in --help. Also, this requires
> updating the man pages.
>
> I think it would be better with a stricter check, perhaps RMail can help
> out.
>
> - gaute
>
Well, I digged through all documentation of trollop short of reading the source
code, and did not find any possibility to access the command line
arguments other than with ARGV. Trollop removes the parsed options from
ARGV, so that after parsing ARGV contains only the non-option arguments to the command
invocation. If there is a more trollopish way to get at the
commandline, I'm glad to learn.
As to a stricter check, I dig into Rmail when I've got the time. In the
meantime I'll use a wrapper, as documented in the wiki.
Regards, Ruthard
--
Emails bitte verschlüsseln und signieren.
Meine PGP-Id: AC5AC6C2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-10-30 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 8:36 Ruthard Baudach
2014-10-30 8:43 ` [sup] " Gaute Hope
2014-10-30 8:57 ` Ruthard Baudach [this message]
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=1414658899-sup-2941@ruthard-lappi \
--to=ruthard.baudach@web.de \
--cc=supmua@googlegroups.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