From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: How to navigate to next git conflict?
Date: Wed, 6 Feb 2019 22:34:35 +0100 [thread overview]
Message-ID: <20190206213435.GB31555@tuxteam.de> (raw)
In-Reply-To: <CAHGDjgCphLt4ojfSMuzLqRydQqeQL-uhW2O0VfEnHonEgt6=FA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
On Thu, Feb 07, 2019 at 12:22:39AM +0300, Hi-Angel wrote:
[...]
> I guess the problem is that catching an error by writing "error" on
> one of condition branches looks like magic, because it the word
> "error" supposed to evaluate to something.
Ah, but condition case is a special form, so it /is/ magic :)
Special forms don't evaluate their arguments.
Cheers
-- tomás
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2019-02-06 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 7:51 How to navigate to next git conflict? Hi-Angel
2019-01-29 9:42 ` Stefan Monnier
2019-02-06 11:37 ` Hi-Angel
2019-02-06 14:11 ` Stefan Monnier
2019-02-06 14:47 ` Hi-Angel
2019-02-06 15:30 ` Stefan Monnier
2019-02-06 21:22 ` Hi-Angel
2019-02-06 21:34 ` tomas [this message]
2019-02-10 22:00 ` Hi-Angel
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=20190206213435.GB31555@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@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.
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).