unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
	Juri Linkov <juri@linkov.net>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: isearch region or thing at point.
Date: Tue, 30 Apr 2019 22:05:36 +0200	[thread overview]
Message-ID: <20190430200536.vjs3nfi7hmzb457x@Ergus> (raw)
In-Reply-To: <CAM-tV--y=3_LhaW45opyCoCFM9PWKw_5tOxxwu3nnoOE7c3zTw@mail.gmail.com>

On Tue, Apr 30, 2019 at 03:24:11PM -0400, Noam Postavsky wrote:
>On Tue, 30 Apr 2019 at 15:03, Ergus <spacibba@aol.com> wrote:
>> where is the if-let part in the documentation?
>
>I don't quite understand what you're asking, what is "the documentation"?
>
>If you meant the elisp manual, I seem to remember there was a decision
>to leave subr-x functions out of the manual (can't find the message in
>the archives right now though).
>
Ohh sorry. I didn't know that. I haven't read the header of the subr-x.el
file. (there is also the eval-when-compile indication) Sorry again.

So I may ask then if it is fine to use these if-let in a function I want
to add to isearch.el or if these functions are expected to become
obsolete or are problematic in any sense; so I must use alternative
implementations??

Best Regards,
Ergus.



  reply	other threads:[~2019-04-30 20:05 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-27  0:14 isearch region or thing at point Ergus
2019-04-27  2:15 ` Basil L. Contovounesios
2019-04-29  0:41   ` Ergus
2019-04-29  1:30     ` Ergus
2019-04-29  1:31     ` Ergus
2019-04-29 19:41     ` Juri Linkov
2019-04-29 20:50       ` Ergus
2019-04-30 15:39       ` Drew Adams
2019-04-30 16:57         ` Ergus
2019-04-30 19:58           ` Juri Linkov
2019-04-30 16:25       ` Ergus
2019-04-30 18:49         ` Noam Postavsky
2019-04-30 19:03           ` Ergus
2019-04-30 19:24             ` Noam Postavsky
2019-04-30 20:05               ` Ergus [this message]
2019-04-30 20:38                 ` Noam Postavsky
2019-04-30 22:39         ` Basil L. Contovounesios
2019-04-30 23:16           ` Ergus
2019-04-30 23:33             ` Basil L. Contovounesios
2019-05-01  0:13               ` Ergus
2019-05-01 20:57                 ` Juri Linkov
2019-05-03 16:27                 ` Basil L. Contovounesios
2019-05-01 11:20               ` Ergus
2019-05-01 14:33                 ` Drew Adams
2019-05-01 16:03                   ` Ergus
2019-05-01 16:25                     ` Drew Adams
2019-05-03 16:28                     ` Basil L. Contovounesios
2019-05-04  9:29                     ` Eli Zaretskii
2019-05-03 16:28                 ` Basil L. Contovounesios
2019-05-04  9:26                 ` Eli Zaretskii
2019-05-04 12:15                   ` Ergus
2019-05-04 14:17                     ` Drew Adams
2019-05-04 14:56                       ` Ergus
2019-05-04 15:24                         ` Drew Adams
2019-05-04 21:06                           ` Juri Linkov
2019-05-04 22:40                             ` Drew Adams
2019-05-06 19:41                               ` Juri Linkov
2019-05-07  2:56                                 ` Drew Adams
2019-05-07 19:56                                   ` Ergus

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=20190430200536.vjs3nfi7hmzb457x@Ergus \
    --to=spacibba@aol.com \
    --cc=contovob@tcd.ie \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=npostavs@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).