Discussions of development and use of the Sup email client
 help / color / mirror / Atom feed

From: Gaute Hope <eg@gaute.vetsj.com>
To: supmua <supmua@googlegroups.com>,
	Ruthard Baudach <ruthard.baudach@web.de>
Subject: Re: [sup] sig-output hook
Date: Thu, 30 Oct 2014 08:54:03 +0000	[thread overview]
Message-ID: <1414659119-astroid-2-eyq7db51z1-2157@strange> (raw)
In-Reply-To: <1414658312-sup-3756@ruthard-lappi>

Excerpts from Ruthard Baudach's message of October 30, 2014 9:39:
> 
> Playing with the possibilities of sup's hooks, I stumbled over the
> sig-output hook. If I am not mistaken, signature has to meanings:
> 
> a) the signature block := text attached to the body of an message,
>    containing information on whatever the sender wants to inform
>    everybody (s)he is mailing to.
> b) the cryptographic PGP/smime signature of the message ensuring the
>    identity of the sender.
> 
> If I am not mistaken, the sig-output hook seems to apply to the
> signature type b)?
> 
> If so, it might be clarifying to change the description to:
> 
> ---------------------->%----------------------
> sig-output
> ----------
> File: /home/ruthard/.sup/hooks/sig-output.rb
> Runs when the PGP signature output is being generated, allowing you to
> add extra information to your signatures if you want.
> 
> Variables:
> signature: the signature object (class is GPGME::Signature)
> from_key: the key that generated the signature (class is GPGME::Key)
> 
> Return value: an array of lines of output
> ---------------------->%----------------------

Thanks,

I'd be happy to accept a patch for this! There are some great tutorials
on how to use git out there (see email from somewhen earlier). That
would contain all the necessary information (e.g. which file to change).

- gaute

     prev parent reply	other threads:[~2014-10-30  8:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30  8:39 Ruthard Baudach
2014-10-30  8:54 ` Gaute Hope [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=1414659119-astroid-2-eyq7db51z1-2157@strange \
    --to=eg@gaute.vetsj.com \
    --cc=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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox