From: Noam Postavsky <npostavs@gmail.com>
To: 34292@debbugs.gnu.org
Cc: Dave Abrahams <dave@boostpro.com>
Subject: bug#34292: 26.1; ido-everywhere interferes with find-file
Date: Tue, 02 Apr 2019 19:58:16 -0400 [thread overview]
Message-ID: <87tvfgez8n.fsf@gmail.com> (raw)
In-Reply-To: <4E3F935E-5A44-4E3E-BC47-1BEA9D60223E@boostpro.com>
[-- Attachment #1: Type: text/plain, Size: 82 bytes --]
[forwarding to list, please use "Reply All" to keep 34292@debbugs.gnu.org on Cc]
[-- Attachment #2: Type: message/rfc822, Size: 1360 bytes --]
From: Dave Abrahams <dave@boostpro.com>
To: Noam Postavsky <npostavs@gmail.com>
Subject: Re: bug#34292: 26.1; ido-everywhere interferes with find-file
Date: Tue, 2 Apr 2019 14:00:33 -0700
Message-ID: <2BA75D23-B713-42E5-8C44-A98629F05F06@boostpro.com>
Sorry, I don't know enough about ido's implementation to tell whether that's what I'm looking for. It seems strange that this code should affect my use-case, since I must *have* ido-mode; even with emacs -Q, (require 'ido) succeeds.
> On Apr 1, 2019, at 4:37 PM, Noam Postavsky <npostavs@gmail.com> wrote:
> So are you looking for something like this?
>
> diff --git i/lisp/ido.el w/lisp/ido.el
> index f9a9607a3a..6dcd5bcd99 100644
> --- i/lisp/ido.el
> +++ w/lisp/ido.el
> @@ -1588,6 +1588,8 @@ (define-minor-mode ido-everywhere
> (remove-function read-file-name-function #'ido-read-file-name)
> (remove-function read-buffer-function #'ido-read-buffer)
> (when ido-everywhere
> + (unless ido-mode
> + (error "Can't turn on `ido-everywhere' without `ido-mode'"))
> (add-function :override read-file-name-function #'ido-read-file-name)
> (add-function :override read-buffer-function #'ido-read-buffer)))
>
next prev parent reply other threads:[~2019-04-02 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 20:26 bug#34292: 26.1; ido-everywhere interferes with find-file Dave Abrahams
2019-04-01 23:37 ` Noam Postavsky
2019-04-02 23:58 ` Noam Postavsky [this message]
2019-04-03 0:01 ` Noam Postavsky
2019-04-03 23:37 ` Dave Abrahams
2019-04-04 0:49 ` Noam Postavsky
2020-08-19 10:49 ` Lars Ingebrigtsen
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=87tvfgez8n.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=34292@debbugs.gnu.org \
--cc=dave@boostpro.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).