From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Vaucher <philippe.vaucher@gmail.com>
Cc: acm@muc.de, casouri@gmail.com, emacs-devel@gnu.org
Subject: Re: Add some aliases for re-related functions
Date: Sun, 03 May 2020 17:16:06 +0300 [thread overview]
Message-ID: <837dxtqf2x.fsf@gnu.org> (raw)
In-Reply-To: <CAGK7Mr4W-mJUegaj5+UDzV1gHYQ19kUOFCWxjB=V1VvWWdtuYA@mail.gmail.com> (message from Philippe Vaucher on Sat, 2 May 2020 22:10:29 +0200)
> From: Philippe Vaucher <philippe.vaucher@gmail.com>
> Date: Sat, 2 May 2020 22:10:29 +0200
> Cc: Yuan Fu <casouri@gmail.com>, Emacs developers <emacs-devel@gnu.org>
>
> Just wanted to explicit that this assume we know both function already. If I don't know `posix-search-forward
> ` but know one exists, but cannot remember if it's regexp-search-posix-forward or posix-regexp-forward or
> forward-search-posix, in Yuan's proposal I could "C-h f re- TAB posix TAB and select
> "re-posix-search-forward" quickly.
>
> Without that I have to C-h d "regexp posix" and curse because it returns no result (Eli <--- please fix this),
> then search for C-h d posix and only then find it.
I did fix this, but please note that you are using the wrong tool for
the job. If you expect the _name_ of the function to include "posix",
then the right tool is "C-u C-h a posix RET", which gives you exactly
what you want. "C-h d" is for when you are NOT sure the keyword will
appear in the name, and therefore widen your search to the doc string
and the list of the arguments.
next prev parent reply other threads:[~2020-05-03 14:16 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 18:28 Add some aliases for re-related functions Yuan Fu
2020-05-02 18:39 ` Eli Zaretskii
2020-05-02 18:43 ` Yuan Fu
2020-05-02 21:21 ` Stefan Monnier
2020-05-02 22:27 ` Drew Adams
2020-05-03 8:33 ` Michael Albinus
2020-05-03 19:07 ` Drew Adams
2020-05-02 19:29 ` Alan Mackenzie
2020-05-02 19:48 ` Yuan Fu
2020-05-02 20:10 ` Philippe Vaucher
2020-05-02 20:13 ` Philippe Vaucher
2020-05-03 14:16 ` Eli Zaretskii
2020-05-04 3:09 ` Richard Stallman
2020-05-04 14:28 ` Eli Zaretskii
2020-05-04 17:12 ` Dmitry Gutov
2020-05-04 17:35 ` Eli Zaretskii
2020-05-04 17:42 ` Dmitry Gutov
2020-05-04 17:46 ` Eli Zaretskii
2020-05-04 17:53 ` Dmitry Gutov
2020-05-02 21:09 ` Alan Mackenzie
2020-05-02 21:51 ` Philippe Vaucher
2020-05-03 9:43 ` Alan Mackenzie
2020-05-03 15:00 ` 조성빈
2020-05-02 22:41 ` Stefan Monnier
2020-05-03 17:14 ` Alan Mackenzie
2020-05-04 10:07 ` João Távora
2020-05-03 14:16 ` Eli Zaretskii [this message]
2020-05-03 16:20 ` Yuri Khan
2020-05-03 16:42 ` Eli Zaretskii
2020-05-03 16:50 ` Dmitry Gutov
2020-05-02 21:33 ` Stefan Monnier
2020-05-02 22:10 ` Dmitry Gutov
2020-05-02 22:18 ` Eric Abrahamsen
2020-05-02 22:49 ` Stefan Monnier
2020-05-02 23:13 ` Dmitry Gutov
2020-05-03 3:55 ` Stefan Monnier
2020-05-04 0:29 ` Dmitry Gutov
2020-05-04 3:11 ` Stefan Monnier
2020-05-02 22:44 ` Drew Adams
2020-05-03 3:26 ` Stefan Monnier
2020-05-03 4:37 ` Drew Adams
2020-05-03 8:05 ` Philippe Vaucher
2020-05-03 9:55 ` Alan Mackenzie
2020-05-03 10:26 ` tomas
2020-05-03 15:15 ` Eli Zaretskii
2020-05-03 19:47 ` Drew Adams
2020-05-04 7:32 ` Philippe Vaucher
2020-05-04 8:20 ` Sending plaintext with Gmail (was: Add some aliases for re-related functions) Kévin Le Gouguec
2020-05-04 8:45 ` Philippe Vaucher
2020-05-04 15:09 ` Sending plaintext with Gmail Stefan Monnier
2020-05-04 15:25 ` Kévin Le Gouguec
2020-05-04 15:29 ` Lars Ingebrigtsen
2020-05-05 8:13 ` HTML display in Gnus (was: Sending plaintext with Gmail) Kévin Le Gouguec
2020-05-05 8:24 ` HTML display in Gnus Lars Ingebrigtsen
2020-05-05 9:26 ` Kévin Le Gouguec
2020-07-17 17:14 ` Kévin Le Gouguec
2020-05-04 15:39 ` Sending plaintext with Gmail Andreas Schwab
2020-05-04 16:51 ` Add some aliases for re-related functions Drew Adams
2020-05-04 17:10 ` Drew Adams
2020-05-04 18:17 ` Philippe Vaucher
2020-05-04 18:33 ` Drew Adams
2020-05-05 2:48 ` Richard Stallman
2020-05-04 3:08 ` Richard Stallman
2020-05-04 10:16 ` João Távora
2020-05-04 3:04 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837dxtqf2x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=philippe.vaucher@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.