From: npostavs@users.sourceforge.net
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: 27272@debbugs.gnu.org, "Johan Bockgård" <bojohan@gnu.org>
Subject: bug#27272: 25.2; [patch] Fix positional args among keyword args in eldoc.
Date: Fri, 04 Aug 2017 21:35:18 -0400 [thread overview]
Message-ID: <874ltm7q5l.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87shhralv7.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net's message of "Wed, 19 Jul 2017 22:22:04 -0400")
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
npostavs@users.sourceforge.net writes:
> Noam Postavsky <npostavs@users.sourceforge.net> writes:
>> Thanks, we will have to test the patch to make sure it works since it
>> hasn't been tested in isolation then.
>
> I've added a commit message and tests, I will push in a few days if there
> are no objections.
Actually, I found another little problem: it uses `cl-position' without
requiring `cl-lib', so it triggers void-function errors in the *scratch*
buffer from 'emacs -Q'. Here's a new version that uses `member' instead
of `cl-position'.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch --]
[-- Type: text/x-diff, Size: 3804 bytes --]
From b6861be04246d29ea46cf4130700df4d923fac58 Mon Sep 17 00:00:00 2001
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Date: Thu, 15 Jun 2017 05:26:05 +0200
Subject: [PATCH v4] Fix eldoc highlighting for &key args (Bug#27272)
* lisp/progmodes/elisp-mode.el (elisp--highlight-function-argument):
Only switch to keyword-based searching if INDEX point beyond `&key' in
the argument list. All arguments prior to the `&key' are position
based. Additionally, be more strict about what is a keyword when
searching for the current keyword.
---
lisp/progmodes/elisp-mode.el | 25 +++++++++++++------------
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/lisp/progmodes/elisp-mode.el b/lisp/progmodes/elisp-mode.el
index b3f452ca5b..47739f5957 100644
--- a/lisp/progmodes/elisp-mode.el
+++ b/lisp/progmodes/elisp-mode.el
@@ -1394,13 +1394,14 @@ (defun elisp--highlight-function-argument (sym args index prefix)
;; FIXME: This should probably work on the list representation of `args'
;; rather than its string representation.
;; FIXME: This function is much too long, we need to split it up!
- (let ((start nil)
- (end 0)
- (argument-face 'eldoc-highlight-function-argument)
- (args-lst (mapcar (lambda (x)
- (replace-regexp-in-string
- "\\`[(]\\|[)]\\'" "" x))
- (split-string args))))
+ (let* ((start nil)
+ (end 0)
+ (argument-face 'eldoc-highlight-function-argument)
+ (args-lst (mapcar (lambda (x)
+ (replace-regexp-in-string
+ "\\`[(]\\|[)]\\'" "" x))
+ (split-string args)))
+ (args-lst-ak (cdr (member "&key" args-lst))))
;; Find the current argument in the argument string. We need to
;; handle `&rest' and informal `...' properly.
;;
@@ -1412,12 +1413,12 @@ (defun elisp--highlight-function-argument (sym args index prefix)
;; When `&key' is used finding position based on `index'
;; would be wrong, so find the arg at point and determine
;; position in ARGS based on this current arg.
- (when (string-match "&key" args)
+ (when (and args-lst-ak
+ (>= index (- (length args-lst) (length args-lst-ak))))
(let* (case-fold-search
key-have-value
(sym-name (symbol-name sym))
- (cur-w (current-word))
- (args-lst-ak (cdr (member "&key" args-lst)))
+ (cur-w (current-word t))
(limit (save-excursion
(when (re-search-backward sym-name nil t)
(match-end 0))))
@@ -1425,7 +1426,7 @@ (defun elisp--highlight-function-argument (sym args index prefix)
(substring cur-w 1)
(save-excursion
(let (split)
- (when (re-search-backward ":\\([^()\n]*\\)" limit t)
+ (when (re-search-backward ":\\([^ ()\n]*\\)" limit t)
(setq split (split-string (match-string 1) " " t))
(prog1 (car split)
(when (cdr split)
@@ -1437,7 +1438,7 @@ (defun elisp--highlight-function-argument (sym args index prefix)
args-lst-ak
(not (member (upcase cur-a) args-lst-ak))
(upcase (car (last args-lst-ak))))))
- (unless (string= cur-w sym-name)
+ (unless (or (null cur-w) (string= cur-w sym-name))
;; The last keyword have already a value
;; i.e :foo a b and cursor is at b.
;; If signature have also `&rest'
--
2.11.1
next prev parent reply other threads:[~2017-08-05 1:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 9:31 bug#27272: 25.2; [patch] Fix positional args among keyword args in eldoc Thierry Volpiatto
2017-06-07 15:33 ` Eli Zaretskii
2017-06-07 16:02 ` Thierry Volpiatto
2017-06-07 17:00 ` Eli Zaretskii
[not found] ` <87shjbegwy.fsf@gmail.com>
[not found] ` <83fufb8avt.fsf@gnu.org>
2017-06-08 8:17 ` Thierry Volpiatto
2017-06-08 15:04 ` Eli Zaretskii
2017-06-07 16:15 ` Dmitry Gutov
2017-06-10 16:15 ` Johan Bockgård
2017-06-11 8:08 ` Thierry Volpiatto
2017-06-15 0:05 ` npostavs
2017-06-15 3:26 ` Thierry Volpiatto
2017-06-30 4:01 ` npostavs
2017-06-30 6:36 ` Thierry Volpiatto
2017-07-01 21:00 ` Noam Postavsky
2017-07-20 2:22 ` npostavs
2017-08-05 1:35 ` npostavs [this message]
2017-08-16 1:30 ` npostavs
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=874ltm7q5l.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=27272@debbugs.gnu.org \
--cc=bojohan@gnu.org \
--cc=thierry.volpiatto@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).