From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [elpa] master 550ae83 1/2: [gnugo int] Decruft: Don't declare hook and keymap vars.
Date: Thu, 16 Feb 2017 10:41:39 +0100 [thread overview]
Message-ID: <87r32yfp64.fsf@zigzag.favinet> (raw)
In-Reply-To: <jwv8tp8ootc.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Tue, 14 Feb 2017 09:04:56 -0500")
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
() Stefan Monnier <monnier@iro.umontreal.ca>
() Tue, 14 Feb 2017 09:04:56 -0500
`C-h o` and `C-h v` work by making you jump to "the
definition" but in your case, "the definition" is in
define-derived-mode and is just not very interesting.
I see.
["definition" search obstacles]. So there's very little
hope for `C-h o` to improve in this respect.
It's good enough for ‘C-h o’ to find ‘define-derived-mode’. I
expect someone will make it so sooner or later, in the name of
Emacs cohesion.
For gnugo.el, i've installed a small comment intended to help
anyone who gets to the ‘define-derived-mode’ to make the last
step in the search, and will do likewise for other (personal)
code. Perhaps if enough people adopt this convention, it will
become "alternative idiomatic"... :-D
--
Thien-Thi Nguyen -----------------------------------------------
(defun responsep (query)
(pcase (context query)
(`(technical ,ml) (correctp ml))
...)) 748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2017-02-16 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170208091858.6699.16542@vcs.savannah.gnu.org>
[not found] ` <20170208091858.F26CA220010@vcs.savannah.gnu.org>
2017-02-08 22:28 ` [elpa] master 550ae83 1/2: [gnugo int] Decruft: Don't declare hook and keymap vars Stefan Monnier
2017-02-09 17:39 ` Thien-Thi Nguyen
2017-02-09 18:02 ` Stefan Monnier
2017-02-10 5:15 ` Thien-Thi Nguyen
2017-02-14 14:04 ` Stefan Monnier
2017-02-16 9:41 ` Thien-Thi Nguyen [this message]
2017-02-12 11:12 ` Philipp Stephani
2017-02-13 7:29 ` Stefan Monnier
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=87r32yfp64.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--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 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).