From: Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>
Cc: ding@ifi.uio.no,
Thomas Roelleke <roelleke@charly.informatik.uni-dortmund.de>,
Christian Altenschmidt
<altensch@charly.informatik.uni-dortmund.de>,
Ulrich Pfeifer <pfeifer@charly.informatik.uni-dortmund.de>
Subject: Re: Using a Gnus for collaborative work & todo list mgmt?
Date: 31 May 1996 16:05:39 +0200 [thread overview]
Message-ID: <vafspchx7ik.fsf@ls6.informatik.uni-dortmund.de> (raw)
In-Reply-To: Kai Grossjohann's message of 29 May 1996 11:28:18 +0200
>>>>> On 29 May 1996 11:28:18 +0200, Kai Grossjohann
>>>>> <grossjoh@ls6.informatik.uni-dortmund.de> said:
Kai> Hi there, we're thinking about maintaining todo lists with Gnus
Kai> for a group of people. So far, here's what we've come up with:
Following Lars' suggestion, I tried setting up a few nnmh groups and
quickly ran into the problem of seemingly being unable to `send' an
article without *actually* sending it anywhere by mail or news. I
briefly thought about creating a devnull mail alias or posting the
stuff to the junk newsgroup. I refrained from actually doing that
because it caused me pain, though 8-)
Anyway, here's what I did. It's a kludge, fer sure, but I'll be happy
about any suggestions you might have.
When doing `a' in a group that matches the gnus-cscw-group-regexp (a
hideous euphemism) a Gcc header is automatically included. This seems
to work, kinda.
Maybe the code should delete empty To and Cc headers automatically,
too.
Unbelievable. I spent a day looking for this -- must seriously
reconsider my being a novice with regard to ELisp. :-|
kai
--
Life is hard and then you die.
;;;;;;;;;;;;;;;;;;;;;;;;;;; -*- Mode: Emacs-Lisp -*- ;;;;;;;;;;;;;;;;;;;;;;;;;;
;; gnus-cscw.el --
;; ITIID : $ITI$ $Header $__Header$
;; Author : Kai Grossjohann
;; Created On : Thu May 30 17:57:45 1996
;; Last Modified By: Kai Grossjohann
;; Last Modified On: Thu May 30 21:24:55 1996
;; Update Count : 49
;; Status : Unknown, Use with caution!
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(require 'gnus)
(require 'gnus-msg)
(require 'nnmh)
(require 'message)
;; Variables
(defvar gnus-cscw-group-regexp "^nnmh:cscw"
"Regexp matching cwsc group names.")
;; Functions
(defun message-setup-news-cscw ()
"Hook that inserts correct Gcc header for cscw message."
(cond ((and gnus-newsgroup-name
(string-match gnus-cscw-group-regexp gnus-newsgroup-name))
(save-excursion
(beginning-of-buffer)
(message-position-on-field "gcc")
(beginning-of-line)
(kill-line 1)
(insert "Gcc: " gnus-newsgroup-name "\n"))
(add-hook 'message-send-hook 'message-cscw-generate-headers
nil t))))
(add-hook 'message-setup-hook 'message-setup-news-cscw)
(defun message-cscw-generate-headers ()
(message-generate-headers message-required-mail-headers))
(provide 'gnus-cscw)
prev parent reply other threads:[~1996-05-31 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-29 9:28 Kai Grossjohann
1996-05-29 21:13 ` Lars Magne Ingebrigtsen
1996-05-30 15:05 ` Kai Grossjohann
1996-05-31 1:22 ` Lars Magne Ingebrigtsen
1996-05-31 14:05 ` Kai Grossjohann [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=vafspchx7ik.fsf@ls6.informatik.uni-dortmund.de \
--to=grossjoh@charly.informatik.uni-dortmund.de \
--cc=altensch@charly.informatik.uni-dortmund.de \
--cc=ding@ifi.uio.no \
--cc=pfeifer@charly.informatik.uni-dortmund.de \
--cc=roelleke@charly.informatik.uni-dortmund.de \
/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).