From: Chunyang Xu <mail@xuchunyang.me>
To: Emanuel Berg <moasen@zoho.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: [el-search] How to search string excluding docstring?
Date: Mon, 25 Dec 2017 21:57:19 +0800 [thread overview]
Message-ID: <m28tdqykow.fsf@xuchunyang.me> (raw)
In-Reply-To: <86373znhk6.fsf@zoho.com>
Emanuel Berg writes:
> Chunyang Xu wrote:
>
>> but I have no idea how to define
>> 'docstring-p'.
>
> Docstrings are in `font-lock-doc-face' so Emacs
> already knows how to determine that. Find out
> how that is done, and then invoke or reuse that
> code from your function.
It almost solves my problem via:
(and (pred stringp)
(guard (not (eq 'font-lock-doc-face (get-char-property (point) 'face))))
(string "foo"))
but it doesn't work for files which is not already opened, I guess it is
because font-lock-mode is only active when I open the file. For example,
M-x el-search-directory RET
(and (pred stringp)
(guard (not (eq 'font-lock-doc-face (get-char-property (point) 'face))))
(string "^GNU Emacs")) RET
M-x el-search-occur RET
also matches process-event-p's docstring (from levents.el.gz):
(defun process-event-p (obj)
"True if the argument is a process-output event object.
GNU Emacs 19 does not currently generate process-output events."
(eq (car-safe obj) 'process))
and after I open levents.el.gz and try the 'M-x el-search-directory'
with the exact same argument again, the match disappears.
Besides I am still interested in using "pattern match" to solve the
issue. I think it is possible though I don't know how yet.
next prev parent reply other threads:[~2017-12-25 13:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6328.1514197667.27995.help-gnu-emacs@gnu.org>
2017-12-25 12:00 ` [el-search] How to search string excluding docstring? Emanuel Berg
2017-12-25 13:57 ` Chunyang Xu [this message]
2017-12-25 14:34 ` Michael Heerdegen
[not found] ` <mailman.6334.1514210258.27995.help-gnu-emacs@gnu.org>
2017-12-25 14:08 ` Emanuel Berg
2017-12-25 17:55 ` tomas
[not found] ` <mailman.6358.1514224565.27995.help-gnu-emacs@gnu.org>
2017-12-25 18:11 ` Emanuel Berg
2017-12-25 19:14 ` tomas
[not found] ` <mailman.6366.1514229270.27995.help-gnu-emacs@gnu.org>
2017-12-25 19:36 ` Emanuel Berg
2017-12-25 21:20 ` tomas
[not found] ` <mailman.6371.1514236843.27995.help-gnu-emacs@gnu.org>
2017-12-25 21:56 ` Emanuel Berg
2017-12-26 2:44 ` Emanuel Berg
2017-12-26 13:34 ` Emanuel Berg
2017-12-26 13:48 ` Jean-Christophe Helary
[not found] ` <mailman.6381.1514296097.27995.help-gnu-emacs@gnu.org>
2017-12-26 15:19 ` Emanuel Berg
2017-12-27 5:38 ` Chunyang Xu
2017-12-27 13:58 ` Michael Heerdegen
[not found] ` <mailman.6406.1514353148.27995.help-gnu-emacs@gnu.org>
2017-12-27 6:58 ` Emanuel Berg
2017-12-25 19:39 ` Emanuel Berg
2017-12-25 10:27 Chunyang Xu
2017-12-25 10:40 ` Jean-Christophe Helary
2017-12-25 12:00 ` Skip Montanaro
2017-12-25 18:04 ` Michael Heerdegen
2017-12-25 14:56 ` Michael Heerdegen
2017-12-25 16:58 ` Chunyang Xu
2017-12-25 17:51 ` Michael Heerdegen
[not found] ` <mailman.6340.1514213787.27995.help-gnu-emacs@gnu.org>
2017-12-25 15:50 ` Emanuel Berg
2017-12-25 16:59 ` Michael Heerdegen
[not found] ` <mailman.6351.1514221174.27995.help-gnu-emacs@gnu.org>
2017-12-25 18:04 ` Emanuel Berg
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=m28tdqykow.fsf@xuchunyang.me \
--to=mail@xuchunyang.me \
--cc=help-gnu-emacs@gnu.org \
--cc=moasen@zoho.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.
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).