From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Kelly Dean <kelly@prtime.org>, Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Proposal for a closed-buffer tracker
Date: Mon, 23 Feb 2015 13:53:39 +0000 [thread overview]
Message-ID: <CAAdUY-K_OCAGrCO_JTkAiZA6PkP6V6HVfhyKgviUUAx1-TkBgQ@mail.gmail.com> (raw)
In-Reply-To: <54EA56E2.3020205@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
On Feb 22, 2015 7:23 PM, "Dmitry Gutov" <dgutov@yandex.ru> wrote:
>
> On 02/23/2015 12:03 AM, Stefan Monnier wrote:
>
>> I consider it good practice to use #'<name> rather than '<name> when
>> referring to a function rather than to a symbol (tho it's not used very
>> widely right now).
>
>
> It's been gaining in popularity recently.
>
>
https://github.com/bbatsov/emacs-lisp-style-guide/commit/26a37b77af54614a41437906f8062fb1744e5889
Not to mention Emacs source should try to set an example. So IMO, yes,
please do that.
[-- Attachment #2: Type: text/html, Size: 844 bytes --]
next prev parent reply other threads:[~2015-02-23 13:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 21:32 Why is Elisp's defvar weird? And is eval_sub broken? Kelly Dean
2015-02-13 19:03 ` Stefan Monnier
2015-02-14 7:35 ` Kelly Dean
2015-02-14 14:36 ` Stefan Monnier
2015-02-15 14:17 ` Daniel Colascione
2015-02-16 5:42 ` Kelly Dean
2015-02-16 7:40 ` Stefan Monnier
2015-02-17 23:39 ` Kelly Dean
2015-02-18 22:29 ` Stefan Monnier
2015-02-19 10:32 ` Kelly Dean
2015-02-19 13:23 ` Stefan Monnier
2015-02-20 0:11 ` Kelly Dean
2015-02-20 2:02 ` Stefan Monnier
2015-02-22 4:11 ` Proposal for a closed-buffer tracker Kelly Dean
2015-02-22 15:53 ` Eli Zaretskii
2015-02-22 22:03 ` Stefan Monnier
2015-02-22 22:23 ` Dmitry Gutov
2015-02-23 13:53 ` Artur Malabarba [this message]
2015-02-23 16:44 ` Eli Zaretskii
2015-02-22 21:59 ` Stefan Monnier
2015-02-28 10:15 ` Artur Malabarba
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=CAAdUY-K_OCAGrCO_JTkAiZA6PkP6V6HVfhyKgviUUAx1-TkBgQ@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kelly@prtime.org \
--cc=monnier@iro.umontreal.ca \
/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).