From: Alex <agrambot@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 8432@debbugs.gnu.org
Subject: bug#8432: 24.0.50; Eldoc highlighting is confused by dolist and dotimes
Date: Thu, 08 Sep 2016 18:15:50 -0600 [thread overview]
Message-ID: <87vay653nt.fsf@gmail.com> (raw)
In-Reply-To: <87zko3vk3i.fsf@escher.fritz.box> (Stephen Berman's message of "Wed, 06 Apr 2011 10:51:13 +0200")
found 8432 25.1
quit
Stephen Berman <stephen.berman@gmx.net> writes:
> 1. emacs -Q
> 2. In *scratch* insert the following sexp:
> (dolist (e '(a b c))
> (message "Done")
> (message "Done")
> (message "Done"))
> 3. M-x turn-on-eldoc-mode
> 4. Putting point on (really, right after) the space after "dolist" makes
> the echo area display this:
> dolist: ((VAR LIST [RESULT]) BODY...)
> 5. Move point one character to the right, onto (really, right after) the
> left parenthesis before "e".
> => Now "VAR" is highlighted in the echo area. Move point one more
> character to the right and "VAR" is no longer highlighted (though
> point is now really on/after the argument VAR of dolist). There is
> no highlighting as point moves further rightwards, until it is at the
> end of the line, right after the closing parenthesis of the argument
> list: now "VAR" is highlighted again.
> 6. Move point to column 0 of the first "message" sexp.
> => Now "LIST" is highlighted in the echo area.
> 7. Move point to column 0 of the second "message" sexp.
> => Now "[RESULT]" is highlighted in the echo area.
> 8. Move point to column 0 of the third "message" sexp.
> => Now "BODY" is highlighted in the echo area.
>
> The same (mis)highlighting pattern arises with dotimes.
I can reproduce this in Emacs 25.1.
next prev parent reply other threads:[~2016-09-09 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 8:51 bug#8432: 24.0.50; Eldoc highlighting is confused by dolist and dotimes Stephen Berman
2016-09-09 0:15 ` Alex [this message]
2020-08-16 10:26 ` Stefan Kangas
2020-10-03 23:52 ` Michael Heerdegen
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=87vay653nt.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=8432@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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.