From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: Oleh Krehel <ohwoeowho@gmail.com>
Subject: Re: [Emacs-diffs] fix-info-dups 6316172: Fix duplicates when completing Info files
Date: Mon, 20 Apr 2015 10:58:36 -0400 [thread overview]
Message-ID: <jwv383ug8k3.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <E1YkAoN-0003Om-Rx@vcs.savannah.gnu.org> (Oleh Krehel's message of "Mon, 20 Apr 2015 12:28:27 +0000")
> * lisp/info.el (Info-read-node-name-2): Use the STRING argument a lot
> less, it's actually always "".
What makes you think it's always ""?
I haven't actually tested your patch, but the way I read it, I get the
impression that it will break things like
C-h i g (emacs-23/e TAB
and
C-h i g (/usr/sh TAB
> Update the regex to remove the split files, the old one wasn't
> working properly.
But the new one only handles those cases where the ".info" extension is
present, which is sadly not always the case (yup, the conventions about how
to name info files suck).
Stefan
> + (not (string-match "\.info-[0-9]+" file))
^^
You forgot to double the backslash.
> + (complete-with-action action (cl-delete-duplicates
> + (nreverse names) :test 'equal) string pred)))
There's `delete-dups' for that.
But I also wonder whether we couldn't try to reduce the amount of
duplication (at least in some of the common cases) even before passing
the result through delete-dups.
IOW, I'm wondering where the duplication actually comes from.
Stefan
next parent reply other threads:[~2015-04-20 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150420122827.13008.83006@vcs.savannah.gnu.org>
[not found] ` <E1YkAoN-0003Om-Rx@vcs.savannah.gnu.org>
2015-04-20 14:58 ` Stefan Monnier [this message]
2015-04-20 15:16 ` [Emacs-diffs] fix-info-dups 6316172: Fix duplicates when completing Info files Oleh Krehel
2015-04-20 19:43 ` Stefan Monnier
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=jwv383ug8k3.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=ohwoeowho@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 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.