Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
To: Daniel Pittman <daniel@rimspace.net>
Cc: ding@gnus.org
Subject: Re: [PATCH] Improve Gnus sieve integration
Date: Wed, 03 Oct 2007 12:57:24 +0200	[thread overview]
Message-ID: <87lkaklb3f.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <87ir5s46mj.fsf@enki.rimspace.net> (Daniel Pittman's message of "Sun, 30 Sep 2007 23:36:52 +1000")

Daniel Pittman <daniel@rimspace.net> writes:

> The attached patch changes this: it extends the support to be able to
> use managesieve to upload the generated Sieve script to a managesieve
> server as well as to upload through running a shell command.

Cool!

The documentation needs to be modified, though, or possibly your code
could be aligned to match the current documentation to avoid backwards
compatibility problems.  The current manual says:

`D g'
     Regenerate a Sieve script from the `sieve' group parameters and
     put you into the `gnus-sieve-file' without saving it.

`D u'
     Regenerates the Gnus managed part of `gnus-sieve-file' using the
     `sieve' group parameters, save the file and upload it to the
     server using the `sieveshell' program.

Maybe your after-save-hook stuff could be replaced by having a new
command that can be invoked in the sieve buffer, to upload the file?
Then people can use D g as before, and have a new option of easily
uploading it via managesieve, or use D u as before too.

Alternatively, the after-save-hook could ask whether the user wants to
upload the file too?  Then both D g and D u would work as documented,
and users would have no surprises and a better experience.  The prompt
could be yes/no/always where always saved a customization of a variable
to remove the prompt.

Just some ideas.

/Simon



  reply	other threads:[~2007-10-03 10:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 13:36 Daniel Pittman
2007-10-03 10:57 ` Simon Josefsson [this message]
2007-10-03 10:59 ` Simon Josefsson
2007-10-03 14:17   ` Daniel Pittman
2007-10-04  7:40     ` Simon Josefsson

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=87lkaklb3f.fsf@mocca.josefsson.org \
    --to=simon@josefsson.org \
    --cc=daniel@rimspace.net \
    --cc=ding@gnus.org \
    /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).