From: Nicolas Petton <nicolas@petton.fr>
To: Michael Heerdegen <michael_heerdegen@web.de>,
John Mastro <john.b.mastro@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
Plamen Tanovski <pgt@arcor.de>
Subject: Re: seq-mapn and circular lists
Date: Thu, 15 Dec 2016 10:26:50 +0100 [thread overview]
Message-ID: <87pokt1r1h.fsf@petton.fr> (raw)
In-Reply-To: <874m26gj21.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
Michael Heerdegen <michael_heerdegen@web.de> writes:
Hi Michael,
>> Since seq.el is developed as part of Emacs, you can use `M-x
>> report-emacs-bug' to submit a feature request.
>
> Yes, please do that, Plamen.
I pushed a fix in master already :-)
Cheers,
Nico
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2016-12-15 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 22:19 seq-mapn and circular lists Plamen Tanovski
2016-12-14 23:32 ` John Mastro
2016-12-14 23:57 ` Michael Heerdegen
2016-12-15 9:26 ` Nicolas Petton [this message]
2016-12-15 9:33 ` Nicolas Petton
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pokt1r1h.fsf@petton.fr \
--to=nicolas@petton.fr \
--cc=help-gnu-emacs@gnu.org \
--cc=john.b.mastro@gmail.com \
--cc=michael_heerdegen@web.de \
--cc=pgt@arcor.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 read-only IMAP folder(s) and NNTP newsgroup(s).