From: Noam Postavsky <npostavs@gmail.com>
To: Ergus <spacibba@aol.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
Emacs developers <emacs-devel@gnu.org>,
Juri Linkov <juri@linkov.net>
Subject: Re: isearch region or thing at point.
Date: Tue, 30 Apr 2019 14:49:52 -0400 [thread overview]
Message-ID: <CAM-tV-98AZF3BdXJX10GkekN5e2XEY5Fy+reG4+3mwGOws491Q@mail.gmail.com> (raw)
In-Reply-To: <20190430162501.xmqh5r5h57sjjlq5@Ergus>
On Tue, 30 Apr 2019 at 12:31, Ergus <spacibba@aol.com> wrote:
> I am pretty new using lisp, but I don't understand this behavior, Any
> help, please.
>
> The backtrace only says:
>
> ==================================================
> Debugger entered--Lisp error: (void-variable bounds)
> isearch-forward-region(nil)
> funcall-interactively(isearch-forward-region nil)
> call-interactively(isearch-forward-region nil nil)
> command-execute(isearch-forward-region)
> ==================================================
>
> Do I am using wrong the if-let* statement?
You need to put at the top
(eval-when-compile (require 'subr-x))
Otherwise the if-let* macro isn't loaded so it gets interpreted as a
normal function call. It works when you use C-x C-e just because you
happened to load subr-x already. If you carefully start from 'emacs
-Q' you should be able to get the same error that way too.
next prev parent reply other threads:[~2019-04-30 18:49 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 [this message]
2019-04-30 19:03 ` Ergus
2019-04-30 19:24 ` Noam Postavsky
2019-04-30 20:05 ` Ergus
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=CAM-tV-98AZF3BdXJX10GkekN5e2XEY5Fy+reG4+3mwGOws491Q@mail.gmail.com \
--to=npostavs@gmail.com \
--cc=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=spacibba@aol.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).