From: Tim Chambers <tbc@alum.mit.edu>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: empty digests and option for once-a-day digest
Date: Sat, 9 Aug 2014 08:13:41 -0600 [thread overview]
Message-ID: <CABoxX=y0Ep4UCPx3-6vbSYBCnLqqJ9mvGvA9aDJRY+t+kbUvaw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
Dear list owner,
I've been a subscriber for a couple weeks now. This is the second time the
digest has been empty (cf. Vol 126, Issue 24). I'd like to take this
opportunity to ask a couple questions. I'm trying to get into the swing of
things and contribute to emacs long-term. It's been years since I've been
active on a mailing list, so maybe things have changed in the meantime,
but I've never seen these two behaviors:
1. Why are empty digests sent out?
2. Why isn't there an option for a once-a-day digest?
Thanks in advance.
– tbc aka emacs-devel subscriber tbchambers@gmail.com
---------- Forwarded message ----------
From: <emacs-devel-request@gnu.org
<javascript:_e(%7B%7D,'cvml','emacs-devel-request@gnu.org');>>
Date: Saturday, August 9, 2014
Subject: Emacs-devel Digest, Vol 126, Issue 25
To: emacs-devel@gnu.org
<javascript:_e(%7B%7D,'cvml','emacs-devel@gnu.org');>
Send Emacs-devel mailing list submissions to
emacs-devel@gnu.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.gnu.org/mailman/listinfo/emacs-devel
or, via email, send a message with subject or body 'help' to
emacs-devel-request@gnu.org
You can reach the person managing the list at
emacs-devel-owner@gnu.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Emacs-devel digest..."
[-- Attachment #2: Type: text/html, Size: 2891 bytes --]
next reply other threads:[~2014-08-09 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 14:13 Tim Chambers [this message]
2014-08-09 19:03 ` empty digests and option for once-a-day digest Stefan Monnier
2014-08-10 0:25 ` Stephen J. Turnbull
2014-08-11 1:56 ` Tim Chambers
2014-08-11 1:57 ` Tim Chambers
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='CABoxX=y0Ep4UCPx3-6vbSYBCnLqqJ9mvGvA9aDJRY+t+kbUvaw@mail.gmail.com' \
--to=tbc@alum.mit.edu \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.