From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: calendar interface for gnus-delay.el
Date: Fri, 12 Apr 2002 14:14:57 +0200 [thread overview]
Message-ID: <vafit6xglku.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <wc3zo0d8q2z.fsf@gamma.cis.ohio-state.edu> (Benjamin Rutt's message of "Tue, 09 Apr 2002 00:15:48 -0400")
Benjamin Rutt <rutt+news@cis.ohio-state.edu> writes:
> Feedback appreciated. Here begins the patch:
I'm a little worried that you are changing the calendar-mode-map. I
wonder if it is possible to do it another way.
Maybe by entering recursive edit?
Another possibility is to create a _new_ calendar buffer (is this
possible?), and then do (use-local-map (copy-keymap
calendar-mode-map)) in the new buffer and then (local-set-key ...).
Then "q" would kill the new buffer.
Thoughts?
kai
--
Silence is foo!
next prev parent reply other threads:[~2002-04-12 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 4:15 Benjamin Rutt
2002-04-12 12:14 ` Kai Großjohann [this message]
2002-04-12 15:55 ` Benjamin Rutt
2002-04-12 16:56 ` 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=vafit6xglku.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).