From: Kai Grossjohann <grossjohann@charly.informatik.uni-dortmund.de>
Cc: ding@ifi.uio.no
Subject: Re: DWIM fix to message.el (TAB handling)
Date: 26 Feb 1997 11:33:42 +0100 [thread overview]
Message-ID: <vafzpwrdfg9.fsf@ls6.informatik.uni-dortmund.de> (raw)
In-Reply-To: Christopher Davis's message of 25 Feb 1997 15:32:56 -0500
>>>>> Christopher Davis writes:
ckd> The following will allow "tab" in a message-mode header to
ckd> expand mail aliases as well as completing newsgroup names.
ckd> This makes message-mode more integrated between mail and news.
Several people mentioned message-x.el, by yours truly. As it is
rather short, I thought I'd just repost it. I just *love* group name
completion in the Gcc header :-)
I'm always interested in additional stuff to add to
message-x-completion-alist.
kai
--
~/.signature
;; message-x.el -- customizable completion in message headers
;; Kai Grossjohann <grossjohann@ls6.informatik.uni-dortmund.de>
;; 9 Aug 96
(require 'message)
(defvar message-x-body-function 'indent-relative
"message-x-tab executes this if point is in the body of a message.")
(defvar message-x-completion-alist
'(("to" . bbdb-complete-name)
("cc" . bbdb-complete-name)
("gcc" . message-expand-group)
("newsgroups" . message-expand-group))
"Table telling which completion function message-x-tab should invoke.
Lookup in the table is done with `equal' comparison of the header.")
(defun message-x-in-header-p ()
"Returns t iff point is in the header section."
(save-excursion
(let ((p (point)))
(beginning-of-buffer)
(and (re-search-forward (concat "^"
(regexp-quote mail-header-separator)
"$"))
(progn (beginning-of-line) t)
(< p (point))))))
(defun message-x-which-header ()
"Returns the header we're currently in. Returns nil if not in a header.
Example: returns \"to\" if we're in the \"to\" header right now."
(and (message-x-in-header-p)
(save-excursion
(beginning-of-line)
(while (looking-at "^[ \t]+") (forward-line -1))
(looking-at "\\([^:]+\\):")
(downcase (buffer-substring-no-properties (match-beginning 1)
(match-end 1))))))
(defun message-x-tab ()
"Does completion based on header currently in or executes a default
function in the body."
(interactive)
(let ((header (assoc (message-x-which-header)
message-x-completion-alist)))
(funcall
(if header (cdr header) message-x-body-function))))
(define-key message-mode-map "\t" 'message-x-tab)
(provide 'message-x)
;; message-x ends here
next prev parent reply other threads:[~1997-02-26 10:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-25 20:32 Christopher Davis
1997-02-25 21:26 ` Justin Sheehy
1997-02-25 21:47 ` Edward J. Sabol
1997-02-26 10:33 ` Kai Grossjohann [this message]
1997-02-26 15:00 ` Christopher Davis
1997-02-26 16:48 ` Edward J. Sabol
1997-02-28 23:47 ` Lars Magne Ingebrigtsen
1997-03-03 9:20 ` Robert Bihlmeyer
1997-03-06 15:44 ` Christopher Davis
1997-03-06 15:56 ` Kai Grossjohann
1997-02-28 23:46 ` Lars Magne Ingebrigtsen
1997-03-01 3:53 ` Christopher Davis
1997-03-05 8:05 ` Lars Magne Ingebrigtsen
1997-03-05 11:40 ` Per Abrahamsen
1997-03-05 15:22 ` Edward J. Sabol
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=vafzpwrdfg9.fsf@ls6.informatik.uni-dortmund.de \
--to=grossjohann@charly.informatik.uni-dortmund.de \
--cc=ding@ifi.uio.no \
/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).