From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, 25154-done@debbugs.gnu.org
Cc: agrambot@gmail.com, tino.calancha@gmail.com
Subject: bug#25154: 25.1; Bindings in cl-letf are in reverse order
Date: Fri, 23 Dec 2016 16:30:47 +0000 [thread overview]
Message-ID: <CAArVCkT81pLsTx-B4ASPFYy+Q8aMOTzrHNeaSOEQOjNdWKq5Rg@mail.gmail.com> (raw)
In-Reply-To: <83pokizr9a.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
Eli Zaretskii <eliz@gnu.org> schrieb am Fr., 23. Dez. 2016 um 14:53 Uhr:
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Fri, 23 Dec 2016 12:17:54 +0000
> > Cc: tino.calancha@gmail.com, 25154@debbugs.gnu.org, agrambot@gmail.com
> >
> > I agree, patches to that effect are welcome. (AFAICT, the manual
> > tries to say that already, but the wording could be more explicit.)
> >
> > OK, I've attached a patch that hopefully clarifies this a bit.
>
> Thanks. My only comment is that I think we prefer talking about
> "binding" instead of "assignment".
>
OK, replaced "assign" with "bind" and pushed to emacs-25 as
c04ac8a3191820d37e7858b7ca4e31cf04808cc3.
[-- Attachment #2: Type: text/html, Size: 1562 bytes --]
next prev parent reply other threads:[~2016-12-23 16:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 23:36 bug#25154: 25.1; Bindings in cl-letf are in reverse order Alex
2016-12-10 4:29 ` Alex
2016-12-10 7:22 ` Eli Zaretskii
2016-12-10 7:43 ` Tino Calancha
2016-12-10 13:41 ` Philipp Stephani
2016-12-10 14:01 ` Tino Calancha
2016-12-10 14:09 ` Eli Zaretskii
2016-12-23 12:17 ` Philipp Stephani
2016-12-23 12:46 ` Tino Calancha
2016-12-23 13:53 ` Eli Zaretskii
2016-12-23 16:30 ` Philipp Stephani [this message]
2016-12-10 18:05 ` Alex
2016-12-10 18:14 ` npostavs
2016-12-10 19:41 ` Alex
2016-12-10 18:27 ` Eli Zaretskii
2016-12-10 19:52 ` Alex
2016-12-11 3:11 ` Tino Calancha
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=CAArVCkT81pLsTx-B4ASPFYy+Q8aMOTzrHNeaSOEQOjNdWKq5Rg@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=25154-done@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=eliz@gnu.org \
--cc=tino.calancha@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).