From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: sieve-manage suggestions
Date: Sun, 12 Jan 2003 18:34:53 +0100 [thread overview]
Message-ID: <ilu1y3il1aa.fsf@latte.josefsson.org> (raw)
In-Reply-To: <84fzryxxe1.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Sun, 12 Jan 2003 15:20:38 +0100")
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> Also, almost everything can be submitted with C-c C-c, but not in a
>> sieve buffer. How about having C-c C-c do like C-c C-l and then kill
>> (or bury?) the buffer? (I think that comment-region is not all that
>> important; now that we have comment-dwim.)
>
> Of course, making C-x C-s do the right thing would be super-nifty.
> But it's work.
I thought about using C-x C-s but I was afraid that users might expect
too much if that is used -- e.g., autosave, crash backups,
save-places.
> I now have one Sieve script shown my sieve-manage, and it's called
> template.siv. Hm. It's kinda strange to have this as something that
> does real work :-) I don't quite remember how I got this, but I
> think I did only obvious things. So how about arranging it so that
> the Sieve script gets a better name when dumb users like me do the
> obvious things?
What would a good solution be? Simply asking the user for a proper
name on upload iff the name equals "template.siv"?
next prev parent reply other threads:[~2003-01-12 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 13:34 Kai Großjohann
2003-01-12 14:20 ` Kai Großjohann
2003-01-12 17:34 ` Simon Josefsson [this message]
2003-01-12 20:06 ` Kai Großjohann
2003-01-12 17:31 ` Simon Josefsson
2003-01-12 20:04 ` Kai Großjohann
2003-01-13 9:22 ` Simon Josefsson
2003-01-13 9:58 ` Kai Großjohann
2003-01-13 16:08 ` Simon Josefsson
2003-01-13 17:37 ` Kai Großjohann
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=ilu1y3il1aa.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--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).